Thank you for all the work on this app for Hubitat - I'm on the migration path from ST to Hubitat. I was able to the nodejs-poolController and the hubitat_poolcontroller without much trouble but ran into an interesting issue. The Device type used for each circuit on the pool panel is a "Generic Switch Component" which seems to not work correctly. When the "on" or "off buttons are used the circuits do toggle on the pool panel however it does not update the switch state and I also receive errors at the nodejs interface (below):
request: {"id":3,"state":1}... id: 3 state: 1 isOn: undefined
error: circuit.get is not a function
192.168.1.178 PUT /state/circuit/setState {"id":3,"state":0}
request: {"id":3,"state":0}... id: 3 state: 0 isOn: undefined
error: circuit.get is not a function
Image of switch with "empty" status
I think the quick fix would be to use a "poolController" Driver for the switch instead of the Generic Switch Component. BTW, I just updated to the latest Habitat Code (maybe that's the issue).
Thanks again for all the hard work....
I figured it out.. I set up the service in the config.json file but didn't enable it (doh)... thanks again
Thank you for all the work on this app for Hubitat - I'm on the migration path from ST to Hubitat. I was able to the nodejs-poolController and the hubitat_poolcontroller without much trouble but ran into an interesting issue. The Device type used for each circuit on the pool panel is a "Generic Switch Component" which seems to not work correctly. When the "on" or "off buttons are used the circuits do toggle on the pool panel however it does not update the switch state and I also receive errors at the nodejs interface (below):
request: {"id":3,"state":1}... id: 3 state: 1 isOn: undefined error: circuit.get is not a function 192.168.1.178 PUT /state/circuit/setState {"id":3,"state":0} request: {"id":3,"state":0}... id: 3 state: 0 isOn: undefined error: circuit.get is not a function
Image of switch with "empty" status![image](https://user-images.githubusercontent.com/34407743/91502542-2ce54380-e87d-11ea-9008-763261aae1dd.png)
I think the quick fix would be to use a "poolController" Driver for the switch instead of the Generic Switch Component. BTW, I just updated to the latest Habitat Code (maybe that's the issue).
Thanks again for all the hard work....
I figured it out.. I set up the service in the config.json file but didn't enable it (doh)... thanks again