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
ZHA: Setting offsets for temperature and humidity, turn off the display, measurement interval #30
Comments
@pvvx sw_build_id = ZHA Write Attribute throws an error, logs say |
@pvvx indeed I pushed the update via OTA. Thank you, will try. |
hi in Zigbee2MQTT I get cluster 516 has no command 256, when trying to set offset "softwareBuildID": "3001-0118", Am i doing something wrong ? |
@gacopl Can you try this PR that add temp/humidifty calibration and others attributes to UI? |
Don't know how to test tbh using official releases only |
@gacopl You need to paste code from PR description to new file and add refernece to this file in |
Would be very nice to set these values in the UI. I also think that a lot of users dont know that this is possible with zha. |
Using pvvx firmware because i switched from zha to z2m. |
For firmware version 0.1.2.1
ClusterID: 0x0204 (Thermostat User Interface Configuration)
Attr: 0x0100, INT16 (id:0x29), Temperature offset, in 0.01° steps, range: -32767 (-327.67°)..32767(+327.67°). Default 0.
Attr: 0x0101, INT16 (id:0x29), Humidity offset, in 0.01% steps, range: -32767 (-327.67%)..32767(+327.67%). Default 0.
Attr: 0x0106, ENUM8 (id:0x30), Turn off the display. 1 - Display Off. Default 0 - Display On.
Attr: 0x0107, UINT8 (id:0x20), Measurement interval, step 1 second, range: 3..255 seconds. Default 10 seconds.
For firmware version 0.1.1.7 - 0.1.2.0
ClusterID: 0x0204 (Thermostat User Interface Configuration)
Attr: 0x0100, INT8 (id:0x28), Temperature offset, in 0.01° steps, range: -127 (-12.7°)..127 (+12.7°). Default 0.
Attr: 0x0101, INT8 (id:0x28), Humidity offset, in 0.01% steps, range: -127 (-12.7 %)..(+12.7 %). Default 0.
Offset for temperature.
Offset for humidity.
The text was updated successfully, but these errors were encountered: