Fibaro motion sensor includes properly with Engine 2.0 and as a generic device on Engine 3.0

[JeroenL 8]

Hi all, 

More an observation, request for confirmation than a “question”. 

I have two  Homecenter 3’s. One running on Engine 2.0 and the other one, I started from scratch in the holiday home, running Engine 3.0.

Funny enough the Fibaro Motion sensor includes differently on both homecentres. It being a native Fibaro device, I was not expecting this. (See the images attached). 

 

Is this normal? They work, however, block-scenes need to made differently. On engine 2.0 it is “ Motion triggered”. And on engine 3.0 it has to be state = detected. In LUA both see the same. 

Functionality like “drop detection” seems to be absent in Engine 3.0. 

 

Thanks for any thoughts anyone might have. 

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

[Fabir 65]

@JeroenLI've seen several strange things on zwave engine ZW3.

 

Things you can try:

-restart hc3

-Soft reconfiguration of the motion sensor

-exclude / include the motion sensor again with or without secrurity

 

[JeroenL 8]

Thanks Fabir ! 

 

I have been trying all of the above over the weekend, but without success unfortunately. 

Every time the same result. 

 

Well, they work, so that is not an issue, it is just "strange", perhaps this will be solved in a future update. 

 

[Neo Andersson 184]

Don't forget, engine 3 is only in Beta version, so some unexpected things might happen yet.