sue_her_birds

There’s a couple zigbee thermostats on Amazon if you search that. None that i have used personally so I don’t have any recommendations. There is a super cheap Tuya one, but i haven’t had a ton of luck with Tuya zigbee devices being very good. YMMV

I’m pretty sure Honeywell has a WiFi version as well. The Lyric T6 i think. It also uses the same bracket and if you bring it in to HA with the HomeKit integration you can block it’s access to the internet and it is fully local and considered offline to Honeywell

There is a z-wave version of that thermostat with the same form factor and clicks right into the same bracket: https://a.co/d/03PLsNtX I have it and it works as you’d expect.

You can use these devices with HomeKit and firewall then off from the internet so they can no longer phone home. I have mine brought into home assistant with the HomeKit controller integration and it’s on a WiFi network with no connection to the outside world. The downside is that it can’t receive a firmware update.

Hue Bulbs are zigbee. They weren’t bricked. You can use them with any zigbee adapter plugged into home assistant, hubitat, etc. I believe you are thinking of the hue hub that began requiring a hue account for “security reasons”

Have you looked at your logs to see if anything looks fishy? Check your main logs but also the logs in your zigbee integration

Also it may be time to submit it as a bug.

Very strange. Are you yaml based or automatic builder based? Can you post your code/screen shots?

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.

Edit: for clarity

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.