I found Tuya to be such a massive pain in the ass that I just ended up ripping out all devices.
The main integration would just randomly stop working when my developer account expired and required an evening of frustrating clicking through poorly translated slow as molasses Chinese websites to re-enable.
Localtuya was spectacularly half baked for my devices.
Has anything changed? Is there a special secret to getting Tuya stuff to work reliably?
I've flashes LibreTiny (fork of Esphome) on my Tuya devices, on a IR blaster and a relay. Took some time to understand how it worked, but then it worked like a charm. Now they are just esphome devices, no more Tuya stuff.
LocalTuya on HACS, it's a bit of a pain to setup and requires you to make a tuya dev account (free) but as far as I can tell you can delete it after, it's just to get the security keys to actually control the devices, and then issue them locally. My devices were much more responsive after doing so
I use zigbee mqtt
Which of course integrates with mosquito broker.
But I tied in my ecowitt weather station data via mqtt into the broker so I have it in HA. I did this with weewx . There's an mqtt add-on
I also integrated my blue-iris NVR in to mqtt for motion detection, notifications for cameras.
Life360 integration to help automate things based on who's home
I use esphome and have a bunch of sensors/devices. I track whole house power utilization, I have temp sensors on my HVAC to I can watch all its performance stats.
Here's my ugly drawing that tracks inside/outside/basement temps, geothermal water loop temps, in/out furnace air temps, water heater state along with both it and the furnace realtime watts usage.
I used to have a Ring and became concerned about privacy once Amazon took over. Worse, all it used to capture was delivery people's backs - by the time it would see motion the action was almost over. That's when it captured anything at all - it used to miss a lot.
Reolink doesn't require any Internet access - even for initial setup. People detection works great with Frigate and you can tell it to start recording before motion is detected so you don't miss anything.
Full disclosure, it does take some fiddling to get it working reliably. I still don't have 2 way audio working.
Create your own automation instead of using the blueprint. The blueprint doesn’t expose the location so it won’t work.
You might be able to look at the full yaml from the trace and copy it into a new automation (replace everything, then update the name). Once you’ve done that you should be able to use the visual editor and make whatever changes you need.
They definitely are repeaters. I had issues with a Moe's ZigBee dimmer. It turned out it was relaying off of an IKEA bulb. When that lamp got turned off at the switch, it killed the link. I ended up using a smart plug as a repeater.
I second this statement. Most of my bulbs are IKEA. I have 4 floors and my ZigBee dongle is on the ground. If they weren't repeaters, my Aqara motion sensors wouldn't be working, but they do!
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.
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.
It does just one thing, and it should do it well. No duplication of efforts by writting support for same devices in multiple softwares.
In future if I wanted to redo HA from scratch or swap it with some else software, I can continue using Zigbee2MQTT without repairing all devices.
Even, I can test different software in parallel, by connecting it to already running MQTT, to access sensor readings of my existing running Zigbee network.
My guess is that at some point you had a lux sensor (illuminance) as a condition and that entity has either had its name changed or has been deleted.
Check out the automation (either in the builder or in the yaml) to see if you have this condition. Then see if that entity still exists or if it’s name has changed.
Once I had devices that replaced entities with new ones with a different ID after a firmware update. It happened to some ESPHome devices I had after upgrading the firmware. Have you checked the device the entity belongs to?
So I've been going through whatever the search engines would throw at me and it seems some people have become so accustomed that they have automations to send alerts. I'm gonna try and track down more info so I can file a decent bug. Hopefully they squash it for once and for all.
homeassistant
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.