I didn't. I suppose since I know I can go backwards now, I'll try to put it back on newest and look at how it behaves tonight and let you know.
I did just get another email after reporting to Aeotec that the downgrade fixed it so far and they said that the have received several of the same reports so he will be taking a deep dive to try and figure it out. Said he would also check back in a week to see how it's doing. I'm actually pretty impressed with the support staff. Quick and attentive so far.
Upgraded back to new firmware, factory reset, off power 10 minutes, included / excluded / factory reset / included. 85 error again and stuck on motion active. Same behavior. Seems pretty obvious that the new firmware isn't playing nice with something, as the 1.3.7 works.
I have 6 MultiSensor 7 and I attempted to drop them back to firmware 1.3.7. One of the 6 was successful. The other 5 have been bricked after the firmware completed. Waiting to hear back from Aeotec support. Frustrated to say the least.
I'm having this issue and don't know where to start, seemingly Aeotec have removed all firmware for the MS7 off their site, so I can't even begin to start doing anything about it. I'm in the UK so I would need a EU version too. Any ideas? Anything I can do via Hubitat?
Contact Aeotec support directly. They will send you the lower firmware. Just make sure you flash it within 10ft of the sensor because otherwise you very well could brick your sensor.
Would I just then take the file they send me and upload it to the 'Device Firmware Updater' app on Hubitat and take it from there. Or will I need to go down the Z-Stick route?
Thanks again @inetjnky, is there a particular reason not to do it via Hubitat? The ZWave updater app seems a much simpler process having just looked at the documentation...
On a side note, I can't believe for a device costing £65 has arrived in such a state. Mine also has a 'cream' colour plastic front which I wasn't expecting (all the images show it as pure white) which is really going to stand-out agains my white walls, not sure if they are making cutbacks by buying cheaper materials, or mine has some sort of fault there too. Unbelievable for such an expensive device.
Yep, I used the zooz zst10 700 to work on mine and it did a fine job. Reasonably priced at $31 on Amazon in the US.
As for an update with my sensor, it's been rock solid on 1.3.7. Aeotec did follow up with me after a couple of weeks just to see how it was doing as well. Although I'm pretty disappointed in the ordeal for such an expensive sensor, I would say my personal experience with support was quite prompt and helpful all around. They didn't talk down to me like I was 3 years old as I've experienced with some other companies in the past.
My recommendation is only based on proximity to the sensors themselves. With a zetick and a laptop you can walk it within feet of the sensor in relation to the location of the hub in your house and sensor placement. I wouldn’t flash the firmware on these devices over 10ft. The closer the better.
I got my Multisensor 7 yesterday and set it up to test and i'm not having any luck what so ever - the point where I think I might have a faulty one.
I can't get motion sensing working on either battery or USB. I've updated the parameters with the Basic Z-Wave Tool - still not luck. Not only does it stick on active, but most of the time it doesn't trigger motion at all, I have to physically pick up the device and shake it around a bit?!
I'm being reported as on FW 1.04 but looking above that is 1.4.1 - i've e-mailed Aeotec to try and get hold of 1.3.7 firmware, as it's not on their site anymore, if anyone has a copy of the EU 1.3.7 firmware and could send it over that would be great as I imagine they've finished for Christmas.
I had a Multisensor 5 that I used with SmartThings back in the day and that was reliable and flawless so i'm pretty disappointed at this as there's no other options for flush mounting a multi sensor in the ceiling which is what I plan to do.
Thanks. I think mine might be faulty. I've flashed with 1.3.7 succesfully, fully reset, added whilst mains powered and still it doesn't detected motion unless you physically move the thing.
Just wanted to update that I received replacement Multisensor 7's under warranty from Aeotech. I flashed them back to 1.3.7 firmware sitting a foot from a plugged in z-stick Gen 5 in my PC and performed a factory reset. Once complete I placed them in their final location and included them in my hub. Updated my rules and everything is working great again. I did have to remove the ghost nodes from the hub to remove the old devices that were replaced.
FYI, I've been working with Aeotec to fix an issue with the MS7 (on FW 1.37) where lux does not update fast enough/freezes for a while, making motion lighting based on Lux levels not work consistently (particularly if you changed the parameter reporting threshold to be less than the default of 100 lux).
My sensor is on battery, not sure if wired versions had the same issue, but I suspect so. Aeotec have just emailed me saying they have fixed the issue and released a new 1.4.2 firmware that you can download here: Update MultiSensor 7 V1.4.2 : Aeotec Help Desk
I've just updated, things and will test/report back my findings. But all seems well thus far...
By means of an update, unfortunately it seems this latest version hasn't fixed the lux sticking issue. However, it looks as though this may only be an issue when you want your lux reporting threshold to be less than 100 lux. The Aeotec rep I'm working with is going to check with their engineering team to see if this is some sort of sensor limitation as he is noticing the same things. Right now, it seems like the MS6 is a much better product than the 7 and potentially has a better sensor in it too (I have almost 20 of these set to 10 lux reporting thresholds and none of them have missed a beat).
