Cannot toggle output zone status after upgrading to 3.4.9

[AKAPADIA]

After upgrade to 3.4.9 from 3.8.8, DON/DOFF to Output zone don't stick. The zone status remains what it was before.

[AKAPADIA]

I have a browser based repro where in one window I do a GET on 192.168.1.213:8080/rest/nodes/n003_output_14/cmd/DOF and in another window a GET on 192.168.1.213:8080/rest/nodes/n003_output_14/ abd the output remains On:

<nodeInfo>

<node flag="0" nodeDefId="output">

<address>n003_output_14</address>

<name>HVAC-Bed 2</name>

<family instance="3">10</family>

<parent type="1">n003_controller</parent>

<type>4.3.2.1</type>

<enabled>true</enabled>

<deviceClass>0</deviceClass>

<wattage>0</wattage>

<dcPeriod>0</dcPeriod>

<startDelay>0</startDelay>

<endDelay>0</endDelay>

<pnode>n003_controller</pnode>

</node>

<properties>

<property id="ST" value="100" formatted="On" uom="78"/>

<property id="TIME" value="0" formatted="0 seconds" uom="58"/>

</properties>

</nodeInfo>

 

This is working for other Output zones. This only started breaking after I upgraded.

[AKAPADIA]

JFYI, I have restarted the Node server and rebooted the polisy multiple times but it doesn't help. In the previous version (3.8.8), every so often (every few weeks) I would bump into this situation where output cmds would stop being honored (even though they would return HTTP 200). I had to reboot the Polisy device to fix. Now, the reboot doesn't work.

Also, there is nothing in the Node server log even when set to DEBUG.

[AKAPADIA]

I messed around with the ELKRP - just logged in and deleted the problematic zone and readded it and it seems to have unstuck it. So this seems like an ELK issue..