I absolutely love Zooz. Their customer service is fantastic and products just work, if you can provide proper Z-Wave coverage. If you prefer WiFi, I have several Shelly products behind traditional switches that have been rock solid.
Before areas was a thing in HASS I would name things with an area name. ESP32-5-Bedroom. Now I just leave it what ever it defaults to, then use HASS to name them, and then put them in an area.
How do you et HASS to name them ? i,e. what names does it chose ? So basically you leave the location out of the name as that is shown in the area anyway ? Thing is, that sometimes you need to choose a device from a dropdown, and in these dropdowns they don’t show the area, so having the location sometime gives more information that is missing
I have the same problem with a zwave energy meter that randomly send a single reading of multiple gigawatts. This makes the history unusable until I manually delete those data points. I haven’t noticed this problem with any of my zigbee sensors.
This is sad to see. I have a hOn device which I recently connected to WiFi to see what features it would have. Sadly it had to connect to the internet to work so I didn’t play with it too much. I checked this plug-in out then and was hoping I could use it.
You need an actuator that takes a proportional input signal. 0-10vdc is common. You’ll just need a 24vac to 10vdc power supply for the manual potentiometer.
Nice. I don’t know about the torque requirements or mounting dimensions of your existing (or new?) damper so double check those. Kinda sucks that they don’t make one that takes the pot signal directly. I know a lot of lighting dimmers are 0-10v but how they are powered and interact with that damper is uncharted territory.
Cannot really answer your questions but if you ever swap to z2m and you keep the exact same friendly name you are using in zha, automations won’t need to be updated. I know it would be still a pain to re-pair but z2m is better than zha, so you will gain in the long term.
I’ve swapped out at few of my Zigbee devices in the past, and even though I’ve deleted the original device, HA will add an “_2” to the entity ID, which breaks any automation that uses it, even if the friendly name remains the same. The only time I’ve seen this not happen is when a device drops off the network and I re-pair it. Is there a trick to making this work? Even if I don’t switch to Z2MQTT, this would be really useful to know. I have a few unreliable cheap door sensors that I’d like to replace, but they’re tied to so many automations that I’ve been dragging my feet on it.
No particular tricks, maybe it’s a one of the limitation of zha. As an exemple, I recently replace a bulb by a new one and old one was repurpose somewhere else in the house, the only thing I did was to rename old bulb and added the new one with old bulb name.
Couldn’t agree more. ZHA is supposed to be more simple to use, but if one is already using HA it’s not going to be long before they reach its limits. Zigbee2MQTT has better device support and more features. While the basic setup may be a little bit more complicated than ZHA you get the benefits mentioned earlier, and you don’t really need to understand all of its functionality from the start - you can learn as you go.
When you talk about the limits of ZHA, what are you referring to exactly? It would probably take an entire weekend for me to re-pair all the devices on my Zigbee network, but I’m not completely opposed to the idea of I gain some functionality that I didn’t have before.
Based on what I read when I first set up HA, it seems like ZHA was somewhat lacking for quite some time but is now essentially equivalent to Z2MQTT. I went with ZHA because it seemed like the “default” for Zigbee.
I like this thermostat except for one issue. When i manually change the target temperature with the HA thermostat card, it has a maximum temperature of 40 degrees. With Fahrenheit, this is obviously no good. it has something to do with the MQTT configuration but i cant figure it out. Luckily service calls in automations work fine.
Hey I got one too! I took it apart and repainted it black to match.
For temp schedules I made a local calendar in HA with repeating events with a description of “high” “mid” and “low”. The automation trigger is a calender event that reads the description and sets the temp accordingly
I have an amcrest one and it works great with frigate over RTSP. I also blocked it’s internet access and firewalled it on my local network so it can’t phone home.
No I just mean Wi-Fi. I do have existing doorbell wires that I can hook up to it for power. I’d probably prefer not having a battery just so I don’t have to worry about charging it ever.
homeassistant
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.