Hi,
What I'd like to accomplish is to configure 'virtual motion switch' , which will be related on few other "more or less real PIR sensors".
All devices are actually dumb devices, updated by json or mqtt, by Satel PIR, camera etc.
I tough I can configure it by adding "motion virtual (dumb)" switch, then add all other 'pir' switches as Sub/Slave device.
But it is not working like I expected, this "motion virtual" switch is not getting updated when other PIR switches are activated.
Am I missing something ? Or is there a bug ?
motion switch and sub/slave devices
Moderators: leecollings, remb0
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: motion switch and sub/slave devices
Please correct me if I am wrong but the Sub/Slave device mechanism is designed for switch -> switch communication. I don't think it will work for PIR -> switch.
A small dzVents script could be a solution. Happy to help with that if that would be an acceptable method.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
- Posts: 24
- Joined: Monday 17 February 2020 19:16
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Poland
- Contact:
Re: motion switch and sub/slave devices
Thank you for fast reply Waaren.
So I expected it to have working sub/slave mechanism, especially that this option is exposed in UI.
I know it is possible to do this via scripting, but if possible I prefer simpler solutions.
Do you think it *should* work that way ? I couldn't find much information online about sub/slave...
Worth to report as a bug , or feature request rather ?
And this is a switch device, virtual/dumb - but still. Right ?
So I expected it to have working sub/slave mechanism, especially that this option is exposed in UI.
I know it is possible to do this via scripting, but if possible I prefer simpler solutions.
Do you think it *should* work that way ? I couldn't find much information online about sub/slave...
Worth to report as a bug , or feature request rather ?
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: motion switch and sub/slave devices
The sub / slave stuf is not the most intuitive part of domoticz. Did you follow the description from the (old) manual ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
- Posts: 14
- Joined: Friday 21 February 2020 8:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.11774
- Location: Italy
- Contact:
Re: motion switch and sub/slave devices
i have the same problems,it seems that sub/lsave mechanism its not working. i get the motion sensor event but i cannot use it to light a bulb. but its not only related to pirs also standard rf switch are not working as slave device. maybe a release bug? i triad both stable and beta but nothing to do.
Pizigate Plugin version: 5.1.017
Firmware version: 0321
Firmware version: 0321
-
- Posts: 24
- Joined: Monday 17 February 2020 19:16
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Poland
- Contact:
Re: motion switch and sub/slave devices
Yes Waaren, I followed this manual, its just not working like expected.waaren wrote: ↑Friday 13 March 2020 15:00The sub / slave stuf is not the most intuitive part of domoticz. Did you follow the description from the (old) manual ?
IMHO this is a bug, or I completely dont understand this mechanism...
Who is online
Users browsing this forum: No registered users and 1 guest