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.
-
|
@rstrouse is spot on. I changed it in my local code and everything syncs just fine. |
Beta Was this translation helpful? Give feedback.
-
|
Still not working for me: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I mistyped line 100. Now I think it's working! Thanks bsileo! |
Beta Was this translation helpful? Give feedback.
-
|
Ok I made this change in the repo. Its a little odd that this helped though as I thought that code would only matter in the case where you are manually adding your controller...when it is discovered with UPNP it should be getting this path dynamically already. Been pretty busy recently so its going to be a bit till I get a chance to update my local environment and work through this. |
Beta Was this translation helpful? Give feedback.
-
|
I manually entered the controller. I couldn't get discovery to work. A 169.x.x.x address was found, but not my controller. Unless it takes more than a couple a minutes--I did the manual add when it didn't seem like it was going to work. How long should I wait? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @bsileo! |
Beta Was this translation helpful? Give feedback.
-
|
You can use Next Heater Mode to toggle ahead in the list. But you are correct there is not a simple toggle to just set a particular mode. Once the mode is set you can just turn it on and off as you noted, which I think works for most people. The one challenge is that the available Heating Modes is different for each installation, so the design was trying to handle that dynamic list. I actually think I found some information on a way to create a dynamic set of options in Hubitat which if I could get to work would allow a "SetHeatingMode" command with correct options. Of course I could do it without options but then the user would have to type in the right value. |
Beta Was this translation helpful? Give feedback.
-
Yes, I'm looking at pool and/or spa body. From the device page as you showed, the setpoint commands and heater off command works but no response with heater on or next heater mode. Within hubitat dashboard, the only templates that seem to work are attributes and temperature but these only show the data or attribute chosen, no command options. I've read with other pool integrations, the thermostat template can be used for the heater.
States are correct in the hubitat website and with hubitat dashboard, just not the hubitat ios app device page. However, it seems many other devices have this issue...not just pool controller. This is unfortunate as i would like to quickly view status or turn on/off a circuit without having to build a dashboard for everything. I use (or used) Actiontiles with smartthings. I was hoping to transition away from actiontiles and use hubitat dashboard to have all local control and not be cloud dependent, but unfortunately many options are missing from hubitat dashboard and design is difficult (in my opinion). |
Beta Was this translation helpful? Give feedback.
-
|
bsileo Next Heater Mode is fine and on/off control is fine for what I need. Whenever "Heat On" is pushed, the currentHeater Mode goes to Heater. So, I'll add a little code to do "HeaterOn" followed by "nextHeaterMode" when "Solar" (aka heatpump) is desired. |
Beta Was this translation helpful? Give feedback.
-
My experience was similar so I ended up integrating Sharptools. Inherently you need something off the lan for control when away from home (at least I do) so this checked that box and works for local control as well. |
Beta Was this translation helpful? Give feedback.
-
The Pool Controller Body device type includes these capabilities: So you are correct that you should be able to use a Thermostat template to interact with it. Here is an example of this on my dashboard (in Sharptools):
I do not use the Hubitat Dashboards so I can't quickly test this side out. Next time I get deeper into development I can try to install those on my Dev hub and see if it works. It certainly should since this is all standard Hubitat settings. |
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:1is not the correct upnp schema. The proper schema isurn:schemas-tagyoureit-org:device:PoolController:1I 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.