I heard one person say it’s slow but I’ve never experienced anything unacceptable. Usually less then a 1 second delay if I press a button. I think that’s fine for a thermostat. It’s possible the problem is related to some battery saving feature. I’d give that a check just in case with a fresh set of Alkaline. You can’t really trust battery percentage reporting on most devices. The last time I had issues it was another devices wreaking havoc on my entire system.
Thinking about it though my thermostat only directly controls my heating. My thermostat can’t control my cooling directly so thermostat variables are saved in Home Assistant including the deadband. I removed the cooling jumper from the thermostat so it would not activate the fan… Anytime a setting on the thermostat is changed it updates the variables in HA. Then HA controls my cooling directly. It’s seamless and you wouldn’t actually notice the two are decoupled without looking at the code. My thermostat is just an input device for my cooling. It directly controls heating in the normal manner.
Furnace filter replacement alerts is something I wanted to do. I see no reason why we wouldn’t be able to make some reasonable assumptions about filter replacements based on run times. The question is coming up with appropriate numbers.
EDIT:
Seems like it’s as easy as adding a 250 hour timer toggled on and off with your HVAC. Perhaps adjust that based on things like pets and allergies.
Quote from
Most manufacturers recommend that the filters be changed out after two or three hundred hours of
use which roughly averages out to once a month. During the really hot or cold months, this could
actually mean one should change it out more often while during the “shoulder” months it might be
two or months before it hits the “recommended” mark. This has actually led many programmable
thermostat makers to include a 250 hour countdown so your display will show when it is needed.
Hi guys… I’m new into this board and new to Home Assistant… my setup is as follows… most of my devices connect to SmartThings as i been using it for years… they replicate to Home Assistant… devices i can connect to HA directly i disable from the smartthings flow… but my issues is with the Centralite Thermostat… i do see the device, but dont have all the controls available… on the dev/states i see the below…
hvac_modes:
min_temp: 45
max_temp: 95
fan_modes: null
current_temperature: 73
temperature: 72
target_temp_high: null
target_temp_low: null
fan_mode: auto
friendly_name: Centralite Thermostat
supported_features: 11
So I have this thermostat but am not using Z2M. The only ‘control’ listed is the fan under the device information. I set it up with my ZigBee hub but have no control over my thermostat from HA. It does run on the C wire for power. Should I try it through Z2M instead of ZigBee?
When i go to dev tools, the entity itself is labeled as climate.thermostat_fan_thermostat.
the state is slated as ‘cool’
the attributes include: hvac_modes: off, heat_cool, cool, heat
min_temp: 44.6
max_temp: 86
fan_modes: auto, on
current_temperature: 71.6
temperature: 73.9
target_temp_high: null
target_temp_low: null
fan_mode: auto
hvac_action: idle
system_mode: [3]/cool
occupied_cooling_setpoint: 2333
occupied_heating_setpoint: 2000
friendly_name: Thermostat fan, thermostat
supported_features: 11
I’m glad those attributes show up, but when I have it on a lovelace card and try hitting the heat button, nothing happens, or any button for that matter
I’ve had that issue. As far as I can tell in my setup that was the result of a bad signal. HA was receiving a signal but the thermostat did not. I was able to move my ZigBee stick and it started working just fine. If you are using a ZB dongle try using a USB extension. Even a short one helps. Particularly if it’s plugged into a USB 3 port. Try to keep the antenna vertical.
So I ended up resetting the thermostat from ZigBee and that worked. It’s working now. No idea what caused the problem but if it happens again, I’ll try to check the logs for future reference
nick, for some reason i got an update for HA a few days ago and all of the controls are now available… when i posted the note i didn’t have any of the options under “Operations” I only had the temperature and was able to change it… now i have all of the options to setup “Off” Heat" “Cool” “Heat/Cool”
Does anyone have an issue with just running the fan operation on this thermostat? When I set an automation to turn on just the house fan, it works fine. But when I set the state to off or auto, the fan does not physically turn off and the thermostat still shows the fan running.
Thanks for your very helpful notes on this thread. I followed your advice and unfortunately I’m still receiving errors (logs below in case that helps).
My setup is a Sonoff Zigbee USB dongle (ZBdongle-P) on a Raspberry Pi 4 running Dockerised Zigbee2MQTT. The thermostat is a Centralite Pearl 3157100-eu (not sure if the -eu distinction is causing problems…?).
Can you help?
Logs
zigbee2mqtt | Zigbee2MQTT:warn 2022-11-06 14:54:48: Received message from unsupported device with Zigbee model '3157100-eu' and manufacturer name 'Centralite'
zigbee2mqtt | Zigbee2MQTT:warn 2022-11-06 14:54:48: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
zigbee2mqtt | Zigbee2MQTT:debug 2022-11-06 14:54:51: Received Zigbee message from 'Centralite thermostat', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":67653648,"imageType":5,"manufacturerCode":49887}' from endpoint 1 with groupID 0
I would say the -eu in the model is causing problems, and based on your logs, it appears zigbee2mqtt does not have a default converter for your model.
You can try a custom converter, see my post above. I don’t know if the -eu version is different, but you can try and setup the custom converter to use the default config for the non -eu model and apply it to your -eu model.
