-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BHT-002-GCLZB issue with edge version #19412
Labels
problem
Something isn't working
Comments
can you provide the data/database.db entry of your device? |
Here it is:
|
Koenkk
added a commit
to Koenkk/zigbee-herdsman-converters
that referenced
this issue
Oct 27, 2023
Fixed! Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
I will check that tomorrow, Thanks ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I am not able to define a setpoint below 10°C.
I was using 5°C in 1.33.1-1 , but it does not work anymore with the last edge version 1.33.1-dev commit: 4d8c6b2
If my thermostat is set to 5°C on HA, it is set to 50°C in Z2M.
What did you expect to happen?
Be able to use a setpoint of 5°C (below 10°c)
How to reproduce it (minimal and precise)
Try to define a "Current heating setpoint" of 5°C.
As you can see in log, setpoint try to be set @50° instead of 5°C
Zigbee2MQTT version
1.33.1-dev commit: 4d8c6b2
Adapter firmware version
20230507
Adapter
SONOFF ZigBee 3.0 USB Dongle Plus
Debug log
Info 2023-10-24 21:38:13MQTT publish: topic 'zigbee2mqtt/Thermostat', payload '{"child_lock":"LOCK","current_heating_setpoint":50,"deadzone_temperature":1,"heat":"OFF","last_seen":"2023-10-24T21:38:13+02:00","linkquality":149,"local_temperature":21,"local_temperature_calibration":-2,"max_temperature":35,"max_temperature_limit":35,"min_temperature_limit":1,"preset":"hold","preset_mode":"hold","running_state":"idle","sensor":"IN","system_mode":"off"}'
The text was updated successfully, but these errors were encountered: