Already did both. Yiu sure you posted us.firmware? Acts.like its listening on. Diff frequency
I took the US download so provided that's is correct then yeah. But you said it worked until you factory reset it. If that was the case it would have stopped working straight away. If you have a spare C7 hub you could try the different frequencies to confirm. I will compare the hex tomorrow night.
No it didn't work.immediatly. they all seem to reset after firmware update . At .least all aeon devices i have seem to be reset and be unpaired after update so i have had. to.fail them and remove from hub and rejoin. .this was also seemed to be reset.
When.it wouldnt.exclude .or..include. i tried reset.
I have a dozen of those MS6 and I've upgraded them all enough times to have specific expectations. First, I've never yet unpaired/excluded them. Second, the MS6's all need a power cycle after an upgrade. Pull the USB or pull the batteries. I have 3 hubs with MS6's and I have to (of course) get the Zwave usb stick joined to the correct Hub via PC Controller -- so I have to Exclude/Include the stick, not the MS6's.
The v1.15 was a yawn for me, v1.12 was the majority of my MS6 prior. Probably half still are since I didn't get joy from the upgrade.
I do recall a stubborn MS6 or two that insisted on being on USB power to do the upgrade.
Really .. you think .i.didnt power cycle it. I said i did above. Good for.you.. not.very helpful for.me.
All.of.my extenders were reset after my firmware updates. And i have upgraded 4 of them now.
definately toast.. even though the light is color changing to indicate ready to pair. it cant be excluded either in the hub, or with the minimote.. when i try exclude the light flashes green fast a bunch of times (normally) but nothing picks it up to exclude it.. oh well. in the trash it goes.
thanks for everyones help
Hi @BorrisTheCat Same thing happened to my MS6 today as happened to @kahn-hubitat. I downloaded the US 1.15 above. It updated ok via the Device Firmware Updater but then stopped communicating with the hub. The LED
still blinked green on motion. It is USB powered and was at V1.13. I powered it off and on, tried to exclude and include. I also tried with my Aeotec stick but it also can't communicate with the sensor.
Does anyone know of a way to force a new firmware onto these?
I'll check it now. If it is indeed the wrong frequency you would have to join it with that frequency and then redo the update. Going to pull the hex for now.
Yeah this was the download so I am assuming your issues are all related to this, sorry. Down load the hex editor and take a pop yourself. Not going to make any more unless I am doing it for myself and I can test it.
@stevebott123 I'm assuming yours was good?
What's that saying? "No good deed goes unpunished." Something like that.
I'm not upset, you were just trying to help.
Does anyone know what happens if I change my hub's frequency?
Will my zwave devices connect ok when I change back to US or will they have to be re-paired? I am ok with them not communicating with the hub for a while.
let me know if you revive it or figure it out.. ill pull it out of the trash for now lol.
I don't think this is the issue, unless they have mislabeled the download but think that is unlikely.
I suspect it's related to the warning of not updating v1.8 and below devices. That wasn't there when I originally did mine so I suspect your not the only ones, however mine MUST be older than 1.8 and it worked fine .
But I'm EU
Honestly no idea, personally unless you have a spare hub or one you don't mind redoing I wouldn't attempt it.
Not @stevebott123 but I can tell you it worked perfectly for me here on my Aussie version.
Thank you very much!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.