Hi, thanks! I have read through a bunch of threads on the sensor but not found any obvious solutions that I haven't tried (or at least I haven't found threads that have given me a solution - I may have missed some!).
Some specs:
I have a Rev C-5 Hubitat (EU version) with software version 2.2.3.119. When this started I had 2.2.2.129, but upgraded along the way.
I usually access the hub on Safari (currently 13.1.2) from a Macbook pro currently running 10.15.6. I have also accessed it from my iPhone 8 on Safari there.
As for logs, the last report from the sensor was the following: dev:22020-08-09 23:28:25.297 infoIlluminance is 0 Lux
then you can see in the logs about 8 hours later that I pressed the activity button to wake it: dev:22020-08-10 09:18:57.310 infoUtomhus is configuring its settings
dev:22020-08-10 08:10:17.734 infoUtomhus is configuring its settings
then I tried an exclude and a z-wave network repair,
sys:12020-08-10 09:32:21.946 infoZ-Wave Exclude Started for 30 Seconds
sys:12020-08-10 09:33:22.257 infoZ-Wave Exclude Started for 30 Seconds
Also new to HE I'm only fiddling about with my EU-C7, using only a few devices before migrating all my stuff.
I ran into exactly the same issue using these drivers after about one day, motion sensor using Binary Report CC still worked, though.
After all I've read here, the recommended way of including seems to be non-secure, so I tried this just now, after using S0 before.
Also new to HE I'm only fiddling about with my EU-C7, using only a few devices before migrating all my stuff.
I ran into exactly the same issue using these drivers after about one day, motion sensor using Binary Report CC still worked, though.
I think the sensors stopped reporting due to the batteries running out. I've read a couple of threads about the battery life being short especially if the sensor reports every 5 minutes, and I noticed that in the logs they were doing so, so I don't think it was a driver issue.
After all I've read here, the recommended way of including seems to be non-secure, so I tried this just now, after using S0 before.
I've also only being trying a non-secure connect, though at some point when that wasn't working I did try secure with no success.
May I ask where you got the EU firmware-image?
I got the firmware update for the sensors on the aeotec website.
No worries. I'm out of ideas then unfortunately. Like I suggested, you could try contacting support directly... It also sounds like some people are having some success with more recent HE firmware, but it does sound like it has been a mixed experience across users... Given the rollback process is relatively straight forward it may be worth a try as well...
Hopefully someone else with more knowledge than me will be able to help out.
When you're trying to pair it again with Hubitat, have you tried different positions/locations to make sure it's not a Z-Wave signal range issue? (You probably have tried, but just to be sure...) Does it not work even when close to the hub itself?
Have you tried rebooting the hub? I sometimes find that after doing some includes/excludes with my hub, it ends up in some sort of a state where inclusion and exclusion no longer work. A reboot fixed the problem.
Aside from that, nothing else really comes to mind right now. I can tell you that I have several MS6 around my house, and I just excluded/included a couple yesterday (decided to use them in different rooms). I have a C-4 Australian hub, fully updated. (I think the latest update was yesterday?)
Did you first pair them under USB power, and then change to battery power? I thought that the default reporting interval under battery power is 1 or 2 hours. Alternatively, did you accidentally set the reporting interval to 5 minutes? FWIW, I find that mine last pretty long on batteries if configured correctly. Most of mine are USB powered, but a few are in locations where that's not practical. For those on battery power, I have selective reporting set up so that there's no regular reporting interval, only reporting when thresholds are reached. If you set large enough thresholds (especially for the values that you're not interested in), then reporting is reduced significantly. These days, I use the Basic Z-Wave Tool to configure the parameters that I want, and then switch the driver back to the in-built driver.
I was told that 'my driver' didn't report Motion when it was Joined using S0. For years we've avoided S0 and so it probably didn't get great testing over the past year. I suggested it be Joined insecurely (one click of the button for C-3 thru C-5) and the person reported back, all was good.
I've since created a v2.0 version of the driver that uses the new zwaveSecureEncap() BUT that only exists in the latest 2.2.3 Platform. I'm using it on a C-4 with v2.2.3.127 with success. However, I have not re-joined any of my MultiSensor 6's on THAT particular hub. I did test it with S0 on my C-7 and it worked fine of course.
All that said, however, and I still think the correct advice is... when in doubt, use the built in Driver(s). It's so easy to flip back and forth. Remember, each time you Join, the Hub will pick the Built-in driver first.
Yes, I did initiate a firmware update over the air in the beginning but my sensor didn't even wake up, and the file that I did have, I realized later, was not the right file type (I was not paying attention ).
I later decided to get me a z-stick and do it the official Aeotec way.
When you're trying to pair it again with Hubitat, have you tried different positions/locations to make sure it's not a Z-Wave signal range issue? (You probably have tried, but just to be sure...) Does it not work even when close to the hub itself?
Yes I've moved it around and currently have it within 1 m of the hub. No dice!
Have you tried rebooting the hub? I sometimes find that after doing some includes/excludes with my hub, it ends up in some sort of a state where inclusion and exclusion no longer work. A reboot fixed the problem.
I have rebooted several times, but I'll give it another go.
Did you first pair them under USB power, and then change to battery power?
I only paired them on battery power, but I've got the problematic hub on USB now because the batteries seem to drain pretty quick.
I thought that the default reporting interval under battery power is 1 or 2 hours. Alternatively, did you accidentally set the reporting interval to 5 minutes?
I thought so too. I don't remember even configuring the reporting interval initially so I was surprised to see in the logs it was reporting so often. If I get it going again I'll be sure to double check that setting. Thanks for the tip re the Z-wave tool!
Not sure if the same issue. I tried to add my second Multisensor 6 and cant get HE to detect it.
I had one working no issue but in my innocence I rest zwave to reinstall both and now neither is detected.
Both are flashing blue/purple/red and flash green when I press power button.
I'm just not having any trouble with these devices.
I have one Joined to my C-7 and I just Excluded it. I had previously Included it as S0 (double click) and so I had to double click to Exclude. I single clicked a couple of times, and the screen shifted to Force Remove.. then I double clicked and the device did the 'rainbow glow' to show it had Excluded and a heartbeat or two later, the 'force remove' screen went away and the device was gone.
I then Included it, again without trouble. This time as insecure.
Having trouble pairing a Aeotec M 6 . Tried S0 and none but Hubitat will not se the device . its also not seeing it when trying to exclude. Have factoryresetted and tried everthing and I am stuck... Im I doing anything wrong? I have 2 of them before working good. The strange thing is I have a vera plus and ezlo plus that also will not recognize the device.... Heeeeeeelp!
Edit: I got a new one from the store and it worked asap!
A very delayed update.
I basically ignored my sensors as I didn't have time to fiddle with them. Then last month I pulled them out of the drawer and updated my hubitat to the latest version. I connected the sensors to USB power. Using a z-stick I removed all the sensors from hubitat. Then I re-discovered them one by one as per the normal routine without a problem. And now I have them in various places in the shed and around the house and they work without a problem.
).
