This might be a user error/understanding, but I thought I post it to be sure. The app is reporting my hub version as 2.3.4.130
But in actuality, it is 2.3.4.132
The firmwareVersionString shows correctly...
Are these different data points or are they the same?
Thanks!!
So it's depreciated but still shows in the app or is it something that I did wrong when I installed the version 3 app?
Thank you very much!
Hit Remove Unused and it should delete those.
Both are now showing the information I expect. There is one small issue.
My primary hub is showing its proper name.
My secondary hub (holds my Iris V1 devices) is showing the name as "My New Hub" instead of what I called it in the device list.
Hub name seems to be whatever the hub was named when you first set it up. May want to see if the locationName agrees with what you expected (should agree with the Hub Details page).
Mine was showing "Home Hub" instead of just Home. I fixed it by going to the Settings > Hub Details. Rename the hub to something else, save, go back and rename it again to your desired name. Must have been a bug in one of the firmware versions where it did not update all the data fields correctly.
I tried renaming it, saving it, then checking. I did not see any change on the tile.
I changed the name back and saved again. I checked, and it is still showing up on the tile and in the html list on the driver page as "My New Hub."
html :
Name My New Hub
Version C-5 / 2.3.4.133
IP Addr 192.168.1.125
Free Mem 486200 KB
CPU Load/Load% 0.05 / 1.0 %
DB Size 2 MB
Last Restart 2023-01-17 19:48:35
Uptime 0d, 3h, 11m, 18s
Temperature 111.2 °F
ZB Channel 0x19 (25)
ZW Radio/SDK null / null
Hub Details show my desired name and location.
Edit: I think I got it figured out. I needed to move the slider on "Base Information" to activate it and have it set to check.
Yes, you will want the Base data, set it to poll4 at whatever your longest interval is.
I'm not using the Z-Wave on this hub. How do I supress the ZW Radio/SDK null/null line? I tried editing the template to delete the line,
ZW Radio/SDK<%zwaveVersion%> / <%zwaveSDKVersion%>It did not work. I saaved it and uploaded it through the file manager after deleting the old one. It is still showing the ZW Radio/SDK line.
Edit again: I had to refresh it a couple of times before the changed .res file actually took. It is solved. Thanks for the assistance in getting it running.
It seems a bit weird that the memory for the hub went below 280MB on two occasions at around 3am when there is no activity?
Any idea how I can diagnose this?
Check your backup times...
Ah, yes, it seems to be around the time automated backup occurred.
Not sure why there is two backups on the 18th, will change the reboot time from 5mins to 30mins.
May not have had time to record the fact that it had finished the first backup so it rescheduled. May want to check for 2 concurrent readings below your bottom threshold as the hub should recover most, if not all, of the memory from backup processing.
If I'm reading that right it is still going to reboot even if the memory recovers. Can you add a condition to the reboot that it only reboots if still below your minimum desired?
Can do this several ways. I'm still on the old Hub Info but the logic would be the same. Using the trigger as you have it I'd do it with these actions:
So basically triggering on the low memory and then waiting for it to go back over 240 for 10 minutes. Then it either did go over 240 or the 10 minutes expired. So we test and if it's under 240 we do the reboot otherwise it will simply exit. Also not sure but you may need some logic to be sure the rule doesn't keep triggering if the memory keeps shrinking. Like using the Boolean variable and setting it as you are beginning the wait. So something like:
Even if you keep it as you have it now consider the Boolean addition to keep it from potentially running the logic over and over if the memory keeps ticking down.
Excellent, thanks for this @tivomaniac!
EDIT: working rule after further discussions with @tivomaniac.
Note: manually set PB to true under local variables once the rule has been setup.
Download the Hubitat app
