trigger to act was i just added another multisensor 6 to the mesh and the whole mesh just went...flaky. The new one had a different firmware version to the others, so to eliminate any potential issues i have upgraded all my MS6 and DualNanos to the same/latest versions. so far so good - reliability back and anecdotally seems a little more responsive. touch wood
yeah wish i had bought a z-stick when i bought my first batch of aeotec stuff, would have been a wiser investment than spending more time than i care to admit finding out how to do this without it, successfully extracting the hex from the Aeotec OTA and updating the fleet. hopefully this post saves everyone else the time.
Using the z-Stick to update is quite painful - you either need to get it to join your z-wave network as a secondary controller (not as easy as you'd think), or exclude devices from your network, include them to the z-stick, update them, and include them back into your network.
Personally, I think updating via Habitat is by far the easiest and best option. It's a shame Aeotec et al, and Hubitat, cant reach an agreement to allow Hubitat to host the raw HEX files for their products.
is that so? in ignorance i assumed it would be a piece of cake with the z-stick. grass is always greener huh?
Couldn't agree with you more wrt Aeotec releasing open standard firmware files.
I mean, they started releasing .hec files for homeseer. wtf? We hubitons are far cooler than homeseers.
yep. well....it did for me each time.
wait a bit for the device to reboot, then click Get Version Report button and the version at the top should update.
