Hey guys. I saw that we had a lot of traffic on updating the Aeotec Multisensor 6. Can you tell me if the new 7 version runs the same firmware? I’ve been trying to update the firmware in my 7’s to the most recent version, with predictable results.
Have a great holiday weekend (for those in the states, LOL).
The updates for aeotec in the past haven't been compatible with the HE firmware update tool. So you may need to ask someone that knows how to extract the firmware into a compatible hex file.
The other option is to follow their directions using SiLabs software to do the update.
Thank you!
It's not hard to do but you need the tools (often called a HexEditor) to be able to work on the .exe Aeotec makes available. You have to find a certain pattern then starting there, copy to the end of the file and that's the Hex file you need to create. Not hard, but "sensitive" to accuracy. 
Anyone feel like giving this a try? I’d love to learn, but this might be a bit much for me just yet. 
So, I received a MultiSensor 7. It seems lighter than the 6, It does not do 'accelleration' (don't really care), and it seems to perform as promised with the built in driver now included with Hubitat. HOWEVER.... the options are very limited. There is no way to set the threshold for reporting LUX below 50. Really? There has to be a 50 point change for the device to update Hubitat? And there is no way to tell it to poll for changes every X seconds or minutes. Ditto with the poll for motion timing. The driver written by Mr. Steele (do I have that name right?) is MUCH more capable.
I originally tried that driver but then could not update the firmware to 1.03. It kept thinking it was a multisensor 6 and rejected the firmware. I reset it, and updated the firmware with no issues. Is there another driver out there for use with Hubitat which can give me the functionality that my 6s have?
Thanks.
John
i have 5 of the 7's and 5 of the 6's
you can adjust all the parameters using the basic zwave tool available via HPM, download swapped the driver to basic zwave tool adjust parameters then swap back, i needed todo this with the 6's as well as not all parameters are available on any driver----- edit except csteele advance drive as that has a basic zwave tool built in.
the 7's defiantly need firmware 1.03
Sheesh.. that MS6 driver I maintain has what feels to be a zillion parameters PLUS it includes the basic zwave tool too.
v2.0.1 Added in optional Param Set / Get commands.
* Added Fingerprint for this device type.
* Added Limit Check on Temp, Illuminance, Humitity and UV values for wildly out of range cases.
* Integrated portions of basicZWaveTool (2020-08-14 maxwell & Copyright 2016 -> 2020 Hubitat Inc. All Rights Reserved)
What's missing for the 6's?
to be honest i forgot that your advance driver had the basic zwave tool built in, so does cover all options available. i just use the basic driver now as they have been tweaked into my needs now for so long that i have no need to play any more
@csteele.. You tell him!!! : ). I wish there was a way to modify your driver for the 7. It has everything I need. One last question - I typed in the parameter number i.e. 35 (not the 0x35), the size as indicated by the manual and the setting I want to send and clicked set parameter. But when I switched back to the driver in Hubitat there is an issue. The driver has the minimum value for Lux reporting at 250 or disabled or no selection. How is the parameter that I set with the Zwave tool going to override the built in driver if I switch back?
Thanks for the help with this.
John
When you switch back, DON'T press Configure.
Ok, I did not. Thank you again.
And yes, you are correct. I set lux threshold and timing and went and covered the sensor and voila. The setting 'stuck' and works despite what the device settings now show. Yay!
Download the Hubitat app
