Trouble with Aeon Multisensor after adding Fibaro Dimmer

[trash 1]

So here's an interesting dilemma that I can't solve and need help with. In my bathroom I had for a while fully functional and working Aeon Multisensor 4 running on batteries. It's been there for two months with no issues at all. 

Last week I added Fibaro Dimmer 2 into the same room to control one of the lights. It work's perfectly fine.

However since I added it, the Aeon Multisensor stopped working. While I can see it still detects movement as the light comes upon upon detecting, it does not seem to be capable to send anything to HC2 anymore. I tried re-adding Aeon by first removing it and adding it back again, but that did not help the situation at all. It took me lot of time to get it added again as waking it up remained undetected by HC2. Finally when I got it done, I ended up in the same situation I started with, i.e. the Aeon runs, detects movement but none of that gets across to HC2. 

I suspect this must have something to do with the mesh-network, but am no expert there. Any suggestions what to try?

[chaicka 195]

See if this helps.

 

Go to "Configuration | Z-Wave Network" and under "Mesh network reconfiguration" section, select the Fibaro Dimmer 2 and click 'reconfigure', once completed (check dashboard on top for log display) repeat the same for Fibaro Dimmer 2 (need to wake battery-operated device up). May need to do the same for surrounding devices.

 

Based on my limited understanding, I have learnt to reconstruct the mesh network properly whenever introduce a new device or changing/swapping device. The mesh network does not always auto-learn or auto-learn correctly, especially when a new device is introduced near to HC2 (just so that it is included properly) but shift to the intended spot after inclusion.

[TRicky 84]

See if this helps.

 

Go to "Configuration | Z-Wave Network" and under "Mesh network reconfiguration" section, select the Fibaro Dimmer 2 and click 'reconfigure', once completed (check dashboard on top for log display) repeat the same for Fibaro Dimmer 2 (need to wake battery-operated device up). May need to do the same for surrounding devices.

 

Based on my limited understanding, I have learnt to reconstruct the mesh network properly whenever introduce a new device or changing/swapping device. The mesh network does not always auto-learn or auto-learn correctly, especially when a new device is introduced near to HC2 (just so that it is included properly) but shift to the intended spot after inclusion.

Thnx Chaicka,

 

This is a good tip. Helped me too with some other problems 

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

 

Cheers

[petergebruers 1,268]

Does the sensor work when it is closer to the HC?

[trash 1]

Does the sensor work when it is closer to the HC?

 

Yes, Peter it works fine then. When I move it further away the issue starts to manifest itself again.

 

I noticed that Aeon was missing even Group-1 association. So I added it by taking the device close to HC2. It started working, but stopped the moment I moved it back to the bathroom.

I tried to do the mesh reconfiguration as suggested by TRicky. The only problem with that is that while waking the Aeon it does not seem to be able to get the instruction from HC2 so it does not work... I will give it another try now when I got the association group fixed.

[petergebruers 1,268]

Yes, Peter it works fine then. When I move it further away the issue starts to manifest itself again.

(...) I tried to do the mesh reconfiguration as suggested by TRicky. The only problem with that is that while waking the Aeon it does not seem to be able to get the instruction from HC2 so it does not work... I will give it another try now when I got the association group fixed.

The HC should be in the association group, but it doesn't explain why it doesn't respond to "update neighbors".

A device holds a list of it's neighbors. "mesh configuration" means: ask a device (or devices) to detect the neighbors (and sending that list to the HC). Indeed, if you move the sensor outside the reach of the HC then the command to update it can't get there. To end this chicken-and-egg problem you can bring the sensor about halfway to where you want it. Then give the mesh reconfigure command on the HC and wake up the device. If that works, move closer to where the sensor has to function and repeat. Some time ago I did tests with a really simple setup. Only one powered device (a relay) and one battery operated device. That worked exactly the way I predicted.

I'd say... usually devices in an "average home" have either a direct connection, or need one hop. When you need 2 hops, things become more difficult because both your device and the first hop will have a list of (its) neighbors. So now not only your sensor should be up-to-date, but also the next hop. And you don't know which device is acting as second hop, if you have many devices... I think it's worth trying a full mesh reconfigure. A few minutes after launching that, your mains powered devices should be OK, but the battery operated devices will update only after wake-up. I'd recommend to just wait a few hours, before attempting anything else.

[TRicky 84]

True Peter,

 

My experience is that once given the 'Mesh reconfiguration' command it might result in a error code but the system try's again in a few minutes. If not You'll start it again yourselves and, in my situation, the second attempt will generate the 'New Neighbors' list and the module works quite well again. (A 3 attempt has occurred too but who cares)

[trash 1]

Thanks guys, the problem is fixed! What I did is a mesh reconfig for the Aeon sensor and some time later a reconfiguration of the entire network. Not sure which of the two did the trick or both perhaps, but the sensor became fully functional again. Thanks again!

[TRicky 84]

Please login or register to see this image.

/emoticons/default_biggrin.png" alt=":D" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />