This virtual device is designed to allow a single button push to request that all hubs in a Hub Mesh check for and install an HE firmware update if available.
Install the device driver on every hub you wish to participate
Determine which hub you want to use as the primary aka, publisher
Either:
a. Method 1 (Port 39501)
i. On each subscribing hub:
1. Turn on the acknowledgement of HE Terms of Service
2. Enter the publishing hub’s IP address and click subscribe
ii. On the publisher hub
1. Turn on the acknowledgement of HE Terms of Service
2. Turn on “Push Update Request to All HubMeshed Hubs”
3. Click “Send Test Message” (all subscribing hubs should have their msg attribute set to “Test Message”)
b. Method 2 (Rule Assisted)
i. On each subscribing hub:
1. Turn on the acknowledgement of HE Terms of Service
2. Share the Hub Updater Device via HubMesh to the publishing hub
ii. On the publisher hub:
1. Turn on the acknowledgement of HE Terms of Service
2. Create a rule:
a. Trigger: Push on the publishing hub is clicked
b. Action: Activate Push on all subscribing hubs
Optional – create a momentary button tile on a dashboard of the publisher hub for the updater device.
To initiate request:
Click the Push command on the publishing hub updater device.
The device will check for an update and either:
Set the msg attribute to say that the hub is current.
or
Send a request out to each subscribing hub to initiate their check for update and:
a. Store the URL of the Community Thread for the update in the notesUrl attribute.
Note: This is URL not valid for Beta releases, production releases only
b. Update the msg attribute with the message that it is updating to version xx.xx.xx.xxx
c. Request the update from HE and start processing.
This sounds very cool. Thank you for working on this. I know there was a discussion on this topic recently and I thought the conclusion was that it was not possible.
For those using Method 1, I’m interpreting this to mean that we should create a virtual button, add it to a dashboard, and have a baby rule that actuates the Push command upon button press? If I’m going to do all that, I might as well have done Method 2 lol. Unless there is a button attribute inside this awesome driver that I could add to my dashboard on the publisher hub directly?
No judgment either way, just confirming understanding.
This is great and will certainly makes things easier for people with multiple hubs.
As with all things, when you release something, we all want more. Sorry!!
Personally I always download a backup before updating.
Is it at all possible to incorporate 'download a backup' before updating?
It may not be that easy to do but it's just a thought.
Thanks again for all your efforts in making things easy for us non-coders out there.
Is this the link? Release 2.3.9 Available
Doesn't this change with each update? or at least each new platform version? By chance this could work for Beta too?
For the production releases the availability check returns the link to the community forum thread, for the beta releases it returns the url to the latest production thread (my assumption is that by using a single endpoint to serve both production and beta updates, updating the endpoint with the url for the beta thread would overwrite the information for the production thread.)
I've been playing with options and keep running into the issue that I can't respond from the destination location. What I could do, if you think it would help, is add an option to send a HTTP GET to a URL of your choosing. Thinking that you may be able to script the wget execution as a response to the GET.
I wouldn't worry about it.
I'm only using 2 hubs so it's no big deal.
It was just a nice to have.
Thanks for having a look though.
I'm sure there are more important things you can be focusing on.
Thanks again.
HomeKit Pushable Button wouldn’t implement right (refused to send button press - wanted to start some other action) so I added Switch capability. Turning on the switch will execute the push logic and then turn the switch off.
I have never shared buttons with HomeKit but was curious about your findings and attempted to add a button device to Tonesto's Homebridge and saw this message which confirms your findings:
@thebearmay
Any chance this can work with HubConnect? I use mesh here at home, but have two remote hubs at different locations. They are connected via HubConnect and work well for sharing devices... Since I'm on the beta channel, and we seem to get a lot of updates, I have to VPN into those locations and do it manually... Not a big deal, but it would be nice to control it from one hub.
