You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be because I updated the change value for msTemperatureMeasurement via the frontend.
I verified my other sensors where I modified the reporting for msTemperatureMeasurement and they all have the same string instead of numeric swap.
What did you expect to happen?
The data type to be the same when update via the frontend, mqtt, or via configure().
How to reproduce it (minimal and precise)
Seems to be easy to trigger by changing the reporting values via the frontend, for example for a sensor. (FWIW, these were all battery powered)
What happened?
While filing #16824 I noticed that the reporting data for that device had a some strings where I would expect numeric.
More specific:
vs
This seems to be because I updated the change value for msTemperatureMeasurement via the frontend.
I verified my other sensors where I modified the reporting for msTemperatureMeasurement and they all have the same string instead of numeric swap.
What did you expect to happen?
The data type to be the same when update via the frontend, mqtt, or via
configure()
.How to reproduce it (minimal and precise)
Seems to be easy to trigger by changing the reporting values via the frontend, for example for a sensor. (FWIW, these were all battery powered)
Zigbee2MQTT version
1.30.1-dev commit: 6afcb97
Adapter firmware version
20221226
Adapter
zzhp-lite
Debug log
No response
The text was updated successfully, but these errors were encountered: