Aeon multi sensor 6 lux stops

Seems to have a issue both with the community driver and built in one that the lux seems to stop reporting in.

Anyone else noticed it? @csteele

I'm on Z-wave JS

I'm on a C-8Pro, latest, latest Platform and ZWJS, but it's NOT replicated on my devices:

Name Value Unit Description Produced by Triggered apps Date/Time
illuminance 48 lux Multisensor6H (masterBath sink) illuminance is 48 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 8:17:58.475 am
illuminance 35 lux Multisensor6H (masterBath sink) illuminance is 35 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 8:07:56.822 am
illuminance 27 lux Multisensor6H (masterBath sink) illuminance is 27 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 7:47:57.728 am
illuminance 23 lux Multisensor6H (masterBath sink) illuminance is 23 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 7:32:58.862 am
illuminance 21 lux Multisensor6H (masterBath sink) illuminance is 21 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 7:27:57.064 am
illuminance 17 lux Multisensor6H (masterBath sink) illuminance is 17 Lux Multisensor6H (masterBath sink) Node-Red Maker (eventHandler) 6/21/2025 7:12:58.936 am

It's just an hour's worth of logs, but plenty of Lux changes.

What firmware version for the device?

Screenshot 2025-06-21 at 6.14.24 PM

image

yeah i noticed it a few weeks ago, i tried the basics but it never seemed to resolve, so being time poor i used a workaround instead (time sunset > sunrise).

im not on zwave JS...

I made some manual changes to the parameters using the basic tool. Will see if it helps and will come back.

Big chunks of the basic tool were incorporated into the driver (with permission) if you didn’t realize. :slight_smile:

I have a multisensor6. I've had it for several years (using @csteele 's driver). Unfortunately, mine misbehaves and messes up my entire Zwave network.

When I first got the C-8Pro (for Xmas this year), I tried it again. I figured different controller, different Zwave chip... Maybe the MS6 would finally work? Nope.

Tried again after switching to zw-js and it still misbehaves. So, unfortunately, I can't use my MS6. But whenever I try it, mine reports lux consistently with csteeles driver. The device just seems to wig out and each report from the device is duplicated like 20 times

I have 12 of the Aeon MultiSensor 6 devices and all but 1 is in constant use. Although I've dropped a couple over the years from up high on a wall, one of them did not survive the accident. The plastic got damages and the back cover won't stay on. Given that's the place the mount attaches, I can't use it in any practical way in my home.

In every bedroom, the MS6's temp reading controls the fan's speed, Motion controls the light and lux feeds into a "gloomy day" decision to extend when motion actually turns on lights during the day.

I have a nearly equal number of Iris v2 & v3 motion sensors that have begun to die. I've been replacing them with Zooz ZSE18... but the MS6 are still going strong as are the pair of Tri-sensors.

Are you looking at the events page or logs. The events page is limited to the number specified in Device Info > Event History Size (per event type). With that in mind if you turn on logging for the device what do the logs show?

Yeah I'm sure mines just borked. I have a couple older trisensors that work great.

Nothing in the logs yet, turned them on and made some changes to settings but not home to check until weekend.

Don't think I did, I'll have changed back before I left so will check again.

1 Like

I believe those are Basic Tools elements

1 Like

seems to have helped i changed these:


set to 15

also set some more but can't remember right now :person_facepalming:t3:

@csteele odd, was working fine, then last night I clicked configure on the device after I made some changes with you driver and it stopped working.

This morning I changed the lux change valve to 5 and pressed save and it's reporting again. (Have not clicked config)

@csteele are you seeing this in your logs for your sensors?

All of mine are and only since later hub update.