Trouble getting expected results with Shelly Plus 1 with Addon for contact sensor #611
Unanswered
BadgerBadgerAndFox
asked this question in
Q&A
Replies: 2 comments 6 replies
-
Would the retain feature of the json codec assist with setting the initial value of the sensors by allowing the last state to be reported rather than waiting for an updated state change?
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I am also new with zigbee2mqttt, but as far as I found out, the message payload is in JSON, so you need to parse this. You need to edit the sensor config by hand, e.g.: I needet to negate the JSON.parse by the
|
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have just started using this plugin in Homebridge and am not getting the expected result for contact sensor configuration.
I have deployed a couple of Addon modules to existing Shelly Plus 1 modules with DHT22 sensors and a reed switch.
The temperature/humidity sensors are working, although i have noted a small issue particularly with humidity in that the plugin reports no value until a message is sent to the MQTT broker which i think only occurs on a state change. Not 100% sure on this as i am new to MQTT.
This results in the humidity sensor reporting no value for one of the sensors that is in a very stable location. Is it possible to present a historical value on the startup?
My primary query however is with the contact sensor. The logs indicate that the topic is correctly returning states of true/false when the contact senso transitions between states, however the sensor state in homebridge does not change state and with history enabled the eve app also indicates no state changes have occurred. Am i missing something in the config?
Below is the message for the topic as observed for the sensor being closed in MQTT Explorer
{ "id": 100, "state": true }
Below is the message for the topic as observed for the sensor being opened in MQTT Explorer
{ "id": 100, "state": false }
Homebridge logs correctly report the state changes as below
jsonpath $.state decoded message to [true]
jsonpath $.state decoded message to [false]
Any ideas where i am going wrong?
Beta Was this translation helpful? Give feedback.
All reactions