Integration with PC1616 - need help with making arming work #49
Replies: 1 comment
-
Slowly progressing - thanks to hint from @otto76 from comment #51 I focused on powering and changed power supplier to external USB phone charger (some cheap item though) then at the same time went through pins again to make sure there is proper contact and sending the alarm arm command works. Not sure if it was supplier or some unnoticaeable cable issue (as I tested before and seemed to have connection). But what happens is that immediately 1D command is generated on its own which I captured on snoop trace. This obviously causes alarm arm and immediate disarm, regardless if this is triggered from NodeMCU or keyboard. Update: solved - the broker kept some retained messages and deleting them helped. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I eventually connected all together and I'm almost there but need help with one function which is arming/disarming alarm. Arming status seem working, zone statuses, trouble field are getting updates too.
I intended to use it with OpenHAB2(OH2) so I used HomeAssistant-MQTT example but at the moment instead of configuring OH2 I used MQTT Dash app on Android and configured topics there for simplicity. It works to me for other devices so I assume that problem is not with testing client.
I see 2 options here:
or maybe something else related to the PC1616...
When it comes to publishing I'm sending payload either 1A or 1D (I have only 1 partition) and I can observe this in snoop trace on my broker device. It is like either NodeMCU doesn't sent it further to PC1616 or so. Any hints very much appreciated, thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions