I added the v3 information driver as a device. It’s working and I was able to within the device reboot the machine.
I’m unclear, though, what the proper way is to use a rule to trigger an action from the virtual hub info driver device from a simple rule or from the rule machine?
I apologize if I missed this within the documentation, but for the life of me I can’t seem to figure it out.
I saw the earlier posts to trigger run actions but I can’t figure out the correct way to trigger that on my system.
The logic makes perfect sense to me, but I’m having trouble referencing the hub information device from within a rule.
Can you tell me what the right way is to reference snd to command this as a virtual device?
I apologize for asking such a basic question, but I haven’t worked with virtual devices yet and after trying all of the actions have so far been unable to reference it.
Thanks for your help and for making this great tool.
Is there a way that I would be able to pull off having two different HTML attributes? For instance I have a very basic simplified one on our home dashboard but it'd be nice to have a more detailed one on a mobile dashboard that I have for quick temps and stats on things.
I have them set up through aggregation. Would I just need to run a second instance of that?
I just used HPM to install the v3 driver on my 3 hubs (2 C-7, 1 C-5) and had no issues at all. I have seen others report having to do a repair to get the code downloaded and I was expecting the same issue,
You can thank @csteele. He read through a few thousand lines of code and found a very subtle error in the way my manifest was coded ("required":"true" vs "required":true) that was causing an improper determination being made in one leg of HPM's code. Once that was pointed out it was a simple fix.
A thought, have you restarted the hub since you set the new format? The attribute only gets set during initialization which normally occurs when you reboot the hub. If you haven't restarted since then, you can force an update by clicking the Initialize button on the driver page.
Why would the Hub Firmware Version still be showing the prior version after upgrade? It does a reboot so would it not pull the current version at that time? I even did a refresh and it still shows the prior version but if I go to the actual check for updates it shows I'm on the current version.
Line 314 is the timeZone formatting, but if it runs into an error there any base attribute updated after that won't finish. What does your Settings|Hub Details|Time Zone look like?
Hi. I installed the Hub Information Server v3, repaired it using HPM, added a virtual device for it called Hubinfo, clicked configure, clicked initialize, and see the information populating within the Hubinfo device screen.
I do not, however, see the device showing up in any of the action lists such that I can command it, such as to reboot, or so that I can poll it (to check memory usage which I’m continually running low for.).
I apologize if I’m missing something, but I’ve checked all the available action menus and submenus and can’t figure out how to leverage the Hub Information Driver.
Sounds like you're well along the way, but let me verify a couple of things.
Have you gone through the preferences and assigned all of those you want to track a poll queue?
Does each poll queue in use have a value greater than zero for a value?
If you've answered yes to both of those then you should be getting regular updates based on your selections automatically - no need for polling outside of the driver itself. As to actions, most people will utilize webCoRE, or Custom Triggers and Actions in Rule Machine to react to minimum level issues (i.e. low memory) - one of those Custom Actions can be a directive to reboot the hub.
