I recently added four new Aeotec Multisensor 6 devices to my HE. I previously had two older ones, one on USB power and the other on battery. All the newer ones are on USB power. Two of them have stopped communicating. If I unplug them and plug them back in, they start communicating again. I'm using them for lux readings. They in locations that don't get triggered by motion very often. Could they be going to sleep? If so, is there a way to keep them awake? I haven't rebuilt my Z-wave mesh given that all devices work with the exception of the two mentioned.
The firmware is 1.14. The driver is aeotecmultisensor6 version 2.0.1 by @csteele
Update
I moved the two problematic devices to locations where they are now triggered by motion on a regular basis. They've been staying online for several days now. I only moved them a few feet so they point down instead of up or out a window. They've always have been within ten feet of the hub. It seems as though the lack of motion triggering is the issue. Since they are new to my z-wave network, it could just be a matter of settling in.
Solution
The problem appears to be the use of Apple USB phone chargers as the power source. I believe they learn to power off after they think the connected device is charged. At first the multi-sensor would stay on for a couple of days. Eventually, it got down to a couple of hours. I tried a different Apple charger. It did the same thing. All my other powered sensors are plugged into a USB power only hub and wired through my attic. When I mounted the problem sensor in the ceiling and plugged it in to the hub, it ran for a day and quit again. After replugging it, it has run for a week so I think I'm good.
There are two custom drivers for the MS6. I am using the one by @csteele and it is working fine. Search in the Package Manager app under keyword “csteele”.
I had trouble with the other driver by Sebastian as it would not update lux readings - not sure why. It’s the only one that comes up when you search for Aeotec, so could be what you have.
I just checked. I'm using the driver by csteele. It's version 2.0.1 in the driver comments. I look for a newer version. The latest version is 2.0.1 release 31 Dec 2020 so I'm up to date
Maybe it's good you stated the obvious. When I connected the device for the first time, it chose the csteele driver as I had used it for my previous multi-sensors. I went ahead and did the steps and now the drive details show up on the device page. I'll wait to see if the devices go offline again
I updated the driver and I still had the problem. In addition, one that I had on batteries that worked all the time, stopped working when I switched it to USB power. I also mounted it into the ceiling so may not be triggered as much by motion. I'm going to try to see if I can get help from Aeotec.
That is really strange. I wonder if there is some difference because of the firmware versions since mine is working? Tagging @csteele to see if he can provide any insight.
Mine is reporting regularly even when not triggered by motion. I don't have logging turned off for this device in Hubitat, but I can see the Illuminance change in my Homebridge logs.
I opened a ticket with Aeotec. I'll post here anything useful I see from them. This is what I got back:
The MultiSensor 6 should not go to sleep on USB power at all, they should always remain awake for as long as you have paired all sensors My recommendation here is to unpair and re-pair them.
If they go offline, make sure to check its routing table if possible. to determine where it is communicating through and see if it is going through a route that is undesirable.
The problem devices are in two different locations, both within 20 feet of the hub so I can't see it as a routing issue. I'll try the repairing. Does the readied device become a new device or does it take on its former identity. I have it mapped to Home Assistant and from there to Node-red so I'd hate to have to redo the whole setup.
I'll try a network repair first just because it's easier. Well, that was interest. I got more failures than successes:
I have had a couple of Aeotec Multisensor 6s for some time, running on batteries (replaced periodically obvs). They are always going offline. Usually, battery removal and reinsertion gets them going again, for a bit. Seem to be lots of similar problems reported
They are a great idea, but some of them are just not very good IMO
Looking for a more dependable luminance sensor that works out of the box.
I have 12 of them. None go offline except when the battery is dead.
It's not an inherent issue with them, in other words. My mesh is certainly different from yours and any deficiencies in a MS6 might only show with your environment.
I just bought a TriSensor last month and it's now substituting for one of the MS6's. But the MS6 is here on my desk still: active.
