search

UniversalDevicesInc-PG3 / udi-poly-ELK

MIT License
2 stars 1 forks source link

DON/DOF to some output zones don't "stick" #84

Closed arshishk closed 2 years ago

arshishk commented 2 years ago

After upgrade to 3.4.9 from 3.8.8, DON/DOFF to Output zone don't stick. The zone status remains the same. It sounds like something you have fixed, but I still see this behavior.

I use output zones to control HVAC valves, so my zoned airconditioning system is totally busted if I can't figure this one out :-(

arshishk commented 2 years ago

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:

n003_output_14
HVAC-Bed 2 10 n003_controller 4.3.2.1 true 0 0 0 0 0 n003_controller

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

arshishk commented 2 years ago

I have restarted the nodeserver and rebooted the polisy multiple times. 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.

jimboca commented 2 years ago

Have you looked at the node server log for errors? I'll try to take a look today.

arshishk commented 2 years ago

ELK_8-21-2022_80400_AM.zip Added a log. I don't see any errors. Interesting that the last error was when I mistyped DOFF instead of DOF

arshishk commented 2 years ago

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..

jimboca commented 2 years ago

Thanks, I was just going to suggest it was something weird with the ELK.