Have just updated to this latest driver and adding items to my grafana dashboard
I noticed that Zigbee shows as online, whilst Zwave shows as enabled
Is there a reason they are different? no big deal, just curious
Cheers
At one point both were derived values (and in some instances still are) and I made the decision to reflect the value displayed in the UI. A small change to the UI at some point exposed some additional zigbee data and in making the change to use that I didn’t notice that the terminology from the hub had changed and just used the value returned. (I’ll fix that inconsistancy in the next few days.)
4 Likes
Seeing some odd behavior after updating my C-8 Pro to 2.3.9.158. When polling for via the API: http://10.10.70.170/apps/api/36/devices/40, the formattedUptime is no longer updating past 47 seconds. I've tried restarting the unit a few times, checked for updates and have the latest version of 3.0.43 of the info driver.
Anyone else seeing this behavior?
Not heard of an issue
are you seeing anything in the logs?
I'm seeing that the c-7 is not updating the firmware version and firmware update status as not available. The c8 is working fine.
the first update takes a while to get new info depending on your queue settings. working fine on my c7s
My C8 Pro hub (firmware version 2.3.9.163) update status is stuck on "Update Available". It initially got stuck on V3.1.2 after updating the hub to V2.3.9.163, but I've just updated the driver to V3.1.3 and tried "Update Check"/"Configure"/"Initialise"/"Refresh"/"Save preferences"/"Save device"/"Reboot with rebuild database", all to no avail. The hub isn't reporting that an update is available after doing an update check, so I assume it's a driver problem?
Does anyone have any idea how to force it to refresh to the correct state?
Same, mine is stuck saying update available. Just updated to 3.1.3 and ran Init and refresh still stuck. No errors in logs.
Hmmm, on line 1126 try changing 127.0.0.1 to ${location.hub.localIP}
Its getting a 408 back, but its not timing out because it comes back immediately. Possibly that endpoint is being blocked due to login security, even on the loopback ip? I am going to add some more logging see if I can figure it out.
Hmmm.. hub without login security enabled is getting a 408 back too.
Endpoint works from a browser.
2 Likes
Maybe up line 1128 to timeout: 100, Notice I had to do that for some of other endpoints.
Getting rid of the blank headers param fixed it on both hubs for me. Put headers back get a 408, remove, get 200 and it works.
void updateCheckReq(){
params = [
uri: "http://127.0.0.1:8080",
path:"/hub/cloud/checkForUpdate",
timeout: 10,
//headers:[]
]
asynchttpGet("getUpdateCheck", params)
}
3 Likes
Interesting... I'll make that change and push it up. (Probably should have deleted that line when I removed the security cookie.)
4 Likes
Updated the driver to V3.1.4, and happy to confirm it's fixed. Thanks very much guys 
3 Likes
That update worked for me as well. Thank you all!
2 Likes
Anyone else having issues with the Reboot command and Shutdown commands no longer working? It started in the version prior to 3.1.4 and also in 3.1.4. Its happening on all 7 of my hubs. (3 C8's, 3C7's, and one C4) Log is below. Same error and same line # on all 7 hubs.
Thanks
I made a change that might fix it, try doing a repair or a re-import of the driver while I update the manifest to make it available through normal channels.
2 Likes
Wow! Thank you for the quick response and thank you so much for this driver. Ive been using it for a while to schedule weekly reboots and a rule to push one dashboard button and all my hubs reboot with one click! Thank you, thank you, thank you sir. May hat is off to you. Sure saves a lot of time from having to browse to seven hubs to reboot. I will try re-importing in a few and let you know.
3 Likes
Did a repair through HPM and issue is resolved! Thank you again sir!
Excellent!
1 Like
