@alan564923
v2.6.23 adds zwaveStatus (enabled/disabled/unkown)
Generally the values will be either enabled or disabled, the unknown (should never see) is a fall through in case it is unable to determine the situation.
3 Likes
After updating, getting these errors in the logs:
dev:13942022-03-18 03:28:06.409 pm errororg.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.50:8080 [/192.168.1.50] failed: Connection refused (Connection refused) on line 925 (method configure)
dev:13942022-03-18 03:28:04.259 pm errororg.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.50:8080 [/192.168.1.50] failed: Connection refused (Connection refused) on line 925 (method configure)
dev:13942022-03-18 03:28:02.880 pm traceHub Information Driver 2.6.23 initialized
Looks like that 192.168.1.50 address has been hard coded into the driver.
After I manually updated with my correct Hub IP and reinit and hit the configure button, I get the following:
Left a hard coded IP in there, if you do a repair you should be good.
2 Likes
Just want to give @thebearmay props for being so responsive to the community requests. Hub Info Driver has been an essential tool to keep an eye on my hub and has enabled timely RM based automatic reboots to keep it running and healthy. The latest updates have been working great. Thanks!
7 Likes
GREAT! Thank you!
I believe this is a "Feature Request":
I'm using the Hub Info Driver as a source to provide an attribute for CurrentMode to Simple Multi Tile. I do this to condense the content of 5 tiles, to a single tile.
The Simple Multi Tile app cannot pull the Mode since mode is a system variable - so I 'hooked' into Hub Information to get the CurrentMode. Today, the GF did an iPhone update - and her phone showed away when it was Present which caused Mode to show we had left the house. Fairly innocuous. When I restarted her Owntracks, and got her presence working again - the tile still kept showing Away. Even after I went into the Hub and updated Mode manually to "Day", the tile showed Away.
Looking at the device Current States for my hub, it showed currentMode as Away (and also currentHSMMode as Armed). I believe the driver might need to add the option to Poll for both of these attributes.
Pressing 'Configure' did force the driver to 'catch-up' so to speak.
Driver currently checks both on its regular polling cycle (about line 513), the Configure just forced an early poll.
Seems like after one of the recent updates to the Hub, your driver can no longer check if there is an update. I set the update check to 15 seconds and turned on debug logging but not seeing anything useful. It is stuck like this:
What do you get if you enter
http://yourHubIP/hub/cloud/checkForUpdate
The only way you should get the Status Not Available message is if the endpoint errors out. (15 seconds may be a little too quick)
That endpoint works. So, I went into the code and added a debug entry. Not useful at first but then I added the resp.status and resp.data. I have Hub Security enabled, and the driver is getting a login screen. All the other metrics I think are refreshing (no errors).
Here is what I added (commented out now since I saw the problem)
And I am literally getting a login screen printing to my logs!
UPDATE: I am sure you will figure this out, but it seems one of the updates made this endpoint require a login and it must not have needed it before based on your code. I copy and pasted some login code from another function in your driver into the update check function and it fixed it for me. So that's the fix.
1 Like
Yep, the minute you said hub security I knew what the issue was. I’ll get an update out to incorporate the fix. Thanks!
2 Likes
v2.6.27 is out with the security login for the update check
5 Likes
Maybe this has been addressed.....
That was generated by the information device for my second hub through mesh on my primary hub.
During a reboot or??
It was not during a reboot. We weren't home. I got a notification of this just once. Checked when I got home and everything seems fine.
Not hurting anything just saying that it’s geeting two requests to update the HTML attribute at the same time. I’ll add some logic to handle though.
1 Like
Oh! So it's like I hit the lottery!? Two requests at the exact same time! 
I guess that wouldn't happen if I had polling times offset a bit?
2 Likes
On a somewhat related note.... since adding a second hub for LAN/Cloud stuff I discovered that I'm basically running this driver...
I need to get more stuff! Tons of overhead now!
1 Like
I noticed recently that my Hubitat information device is not updating every 300 seconds like I have it set to. As of this morning, it hasn't updated since about 0300 yesterday morning. The CPU load and temperature today were still the same exact numbers as they were all day yesterday. I hit the Initialize button and it's now updating every 300 seconds as it should. I've done this before, though, but it seems to stop updating at some point.
I haven't rebooted recently, and I also have the most recent Hub Information Driver installed.
Is there a setting I missed?
