Zipato Multisensor Quad unintentionally turns on lights

carntzen shared this question 1 month ago
Need Answer

I have a Zipato Multisensor Quad in a room where I also have two Zipato Wall Plugs (used for lights).

I have not created any rules relating these devices to each other.

Still, the lights (wall plugs) reacts to motion in the room and turns on!

How can this happen? And how can I prevent it from happening? I still want to use the PIR sensor in the Multisensor Quad for other actions, so I don´t want to turn of this sensor (divice configuration setting).


In the Wall Plug manual an example scenario is described: "During night, if illuminance levels are lower then preset value, any person movement in device’s field of vision will trigger radio signal that will turn connected lightning equipment."

It seems like there is a default configuration setting that somehow affects other z-wave connected devices. How?

Best Answer
photo

This "Unknown_Device_2" normally represents Zipato controller. They have strange way of reporting assiciation groups to the box, because instead of NodeID =1 (main controller) they report each assiciation group to NodeID equal to number of that group - so Group 2 is reported to NodeID=3, group 3 to 3 etc.

Unfortunately sometimes Zipato assigns those low NodeIDs to devices you connect to the network. When that device is a switch and gets ID=2 or 3 it gets turned on/off by most devices that on Groups 2-4 send basic on/off or similar notification.

I hope it is more clear now. So basically if you see on Advanced Tab that your device has NodeID=2 you actually should remove it and add to the network, because your problems with turning on/off would return in the future when new devices are added to the network and they get NodeID 2 assigned to their association group 2.

Comments (14)

photo
1

If you do not have a rule triggering this. it sound like you have bind or associated the devices together. You need to check this out, otherwise, delete the Multisensor then re include it.

photo
2

some years ago this happened to me too! with a TKB Plug and a fibaro motion eye.

Devices was already joined to the system. Devices already configured and worked good since the first use.

No configuration changes, no new things, no bindings, no rules, nothing. But the TKB plug turned on every motion the fibaro detected.

But at a certain time, they start to works like binded (but without any bind evidence).

I opend a ticket, they pointed the finger - obviously - to me, to my devices, to my configuration over the devices (that never changed), but absolutely not to the zipabox.

Solution? The same of ever: remove and re-add device like @lite automation already suggested.

photo
1

Thank you Simone for your answer. This was comforting to read!

This is exactly the case I experienced. I haven´t done any thing with the configurations of the devices, nor done any binding of them. I can´t see anything in the Associations Manager for the light sensor that indicate a binding (but I´m not sure how to read this feature). They somehow just seem to know about each other in some magical way... (of course it´s not magic but some technical explanation behind this - which I would appreciate if Zipato could explain). I´ll try to exclude and include the sensor.

photo
1

canrtzen, you had probably an association in group 2 but to see them you need to select a group on the right panel and then click "RETRIEVE" in the middle. That happened to me recently and moreoverI couldn't remove that association, but I could add more devices to it. You can check what devices are associated in groups selecting each group and clicking "RETRIEVE".

photo
1

Thanks, I tried this now. The only thing that shows up after the Retrieve-procedure is "UNKNOWN_DEVICE_2". Do you have any idea what this means?

photo
1

Just to complete this topic: I tried the process of removing the association to this "UNKNOWN_DEVICE_2", and it seeme to work. I haven´t had any more issues with the lights turning on/off when motion. Thanks for all help.

photo
1

This "Unknown_Device_2" normally represents Zipato controller. They have strange way of reporting assiciation groups to the box, because instead of NodeID =1 (main controller) they report each assiciation group to NodeID equal to number of that group - so Group 2 is reported to NodeID=3, group 3 to 3 etc.

Unfortunately sometimes Zipato assigns those low NodeIDs to devices you connect to the network. When that device is a switch and gets ID=2 or 3 it gets turned on/off by most devices that on Groups 2-4 send basic on/off or similar notification.

I hope it is more clear now. So basically if you see on Advanced Tab that your device has NodeID=2 you actually should remove it and add to the network, because your problems with turning on/off would return in the future when new devices are added to the network and they get NodeID 2 assigned to their association group 2.

photo
1

This is the kind of answer I would expect from a technical support .. and instead these answers often come from users, with the support that answers "delete the device and add it back".

Obviously .. because with a similar explanation they would admit their mistake ... and they will never do it.

photo
1

Great knowledge Tomasz! I´m impressed :) Thank you for sharing.


I do agree Simone, this should come from Zipato support!

photo
1

Woww, Even I did not realize this possibility. Great information.

photo
photo
1

Carntzen,

Z-wave devices can control each other (basic functionality) without the need of a controller, as long as they are on the same network and also it depends on the device capabilities. For some reason looks like the Quad sensor got associated somehow with the wall plug, this was making the sensor to trigger the wall plug. By deleting that association you removed the "rule" that triggered the plug. This is meant to exist so if your automation is basic you can make devices react faster and without the need of the controller.

photo
1

Sure.. But the problem is that association was created without user intervention :)

The same happened to me some Years ago.

photo
1

That is the spooky part... I only have got devices deleted automatically but this is the next level.

photo
1

I do agree. I´m not very happy with this auto-association happening. @Fibaro please fix! Luckily none of my other Fibaro Wall plugs was associated. I have one in the next room connected to my freezer (to trigger alarm if power consumption drops). I would have a very warm freezer if the motion sensor turned this on and off all the time!

photo