Does the Hubitat integration still work? #458
-
I see these messages in the Hubitat log:
192.168.0.31 is the rpi running nodejs-poolController 192.168.0.213 is the Hubitat. When I start a new PoolController app, I try discovering, but nothing is found. I get these messages:
When I enter the IP address for poolController manually, I get these messages:
/sys/var/syslog on the poolController rpi has records like this:
I can do gets using postman using the "Swagger" api for api's like get http://192168.0.31:4200/state/all. But, when I try a GET for /device I get:
So, I'm wondering if something in the api has changed that has messed up the Hubitat integration? Or am I missing something? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 23 replies
-
I don't run Hubitat but the above has an invalid upnp request. And yes this was previously in the njsPC code but it was not properly responding to upnp requests.
I think the original code was produced by @bsileo and is no longer supported but I submit a request to have him change that single line of code to recognize the correct schema. |
Beta Was this translation helpful? Give feedback.
-
Thanks @bsileo! |
Beta Was this translation helpful? Give feedback.
I don't run Hubitat but the above has an invalid upnp request. And yes this was previously in the njsPC code but it was not properly responding to upnp requests.
urn:schemas-upnp-org:device:PoolController:1
is not the correct upnp schema. The proper schema isurn:schemas-tagyoureit-org:device:PoolController:1
I think the original code was produced by @bsileo and is no longer supported but I submit a request to have him change that single line of code to recognize the correct schema.