Page 2 of 2
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Friday 13 May 2016 16:14
by Egregius
I2 and I3 are virtual sensors, not real relays.
They can be used to trigger actions or zwave groups.
I trigger a bash script with it. The bash script then toggles the real device.
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Friday 13 May 2016 16:18
by mvveelen
Oh really....? So, how can I go further:
I want the I2 to toggle a virtual (kill) switch. When I go to bed at night, I push the button and the killswitch turns off all devices.
Edit: I use a switch called "Wandschakelaar" in an event. And when it's ON, then.....and OFF, then.....etc. So I should have an extra toggle script you say? How would that script look like? Are there any examples?
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Friday 13 May 2016 20:50
by Egregius
I have this in the on action of the I2 sensor:
script:///volume1/web/secure/belknop.sh
And the script itself is
Code: Select all
#!/bin/bash
curl -s --connect-timeout 4 --max-time 5 "http://127.0.0.1:8084/json.htm?type=command¶m=switchlight&idx=77&switchcmd=On&level=0&
switchcmd=On can also be switchcmd=toggle
see
http://www.domoticz.com/wiki/Domoticz_API/JSON_URL's for all options.
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Saturday 14 May 2016 14:01
by mvveelen
I've rewritten it a bit so I can use it on my Synology and put the script in the Domoticz scripts folder. Using the toggle command I can switch a second, virtual switch which turns off everything like the old 'killswitch' did. Thanks for this workaround !
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Sunday 15 May 2016 15:03
by dgonneau
I got my own ZMNHDD1 and also experienced the same i2/i3 problem.
It got better when I assigned group 5 to controler but is it really the right way to fix this problem ?
Doing so, the i2 doesn't behave well with a monostable switch even if you change parameter 2 to the right setting (monostable instead of bi-stable).
Furthermore, I tried to plug the monostable switch on the i3 and my domoticz device that was working with i2 also was activated by i3.
I therefore concluded that this device is kindof linked something else or to the controler, that's strange ...
So far I keep my setting with a bistable switch and I'll make a script later to toggle my target device only when ON is pressed.
I just find it strange that we can change the setting of i2 (stable or bistable) but that it doesn't seem to make any difference...
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Monday 20 March 2017 19:01
by Lusch
Just to follow up on this. I have my ZMNHDD1 configured like in this topic, I notice some weird behaviour though.
For testing I have this Lua script which just prints the status of the I2 puls switch:
Code: Select all
if(devicechanged['I2']) then
print ("<font color='amber'>I2 pressed ("..otherdevices['I2']..")</font>")
end
I would expect it to go on and off all the time, but the thing is, it goes like this:
Code: Select all
2017-03-20 18:55:39.558 LUA: I2 pressed (Off)
2017-03-20 18:55:39.559 EventSystem: Script event triggered: I2 woonkamer
2017-03-20 18:55:39.544 (Razberry) Light/Switch (I2)
2017-03-20 18:55:49.711 LUA: I2 pressed (On)
2017-03-20 18:55:49.697 (Razberry) Light/Switch (I2)
2017-03-20 18:55:51.718 LUA: I2 pressed (Off)
2017-03-20 18:55:51.719 EventSystem: Script event triggered: I2 woonkamer
2017-03-20 18:55:51.704 (Razberry) Light/Switch (I2)
2017-03-20 18:59:15.451 LUA: I2 pressed (Off)
2017-03-20 18:59:15.451 EventSystem: Script event triggered: I2 woonkamer
2017-03-20 18:59:15.444 (Razberry) Light/Switch (I2)
So every other time I press the puls switch it only sends to Off comand. Very annoying, any suggestions?
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Tuesday 21 March 2017 20:03
by Lusch
In addition I noticed that the single OFF command (without the ON command first) is send even before I release the switch! So it must be a config issue....
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Monday 15 May 2017 0:00
by brammh
This thread is extremely helpful for me, thanks! Finally got events from I2 and I3 coming in...
Now running into my next issue: these events, have the exact same message payload / object. I don't see any different attributes, which makes it not possible to see where it was triggered from. Any clue?
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Saturday 24 June 2017 21:41
by mven
Hi all- thanks for this post! I've got I2/3 working! But... like brammh, I can't get I2 and I3 configured as two independent switches.
Could it be that both I2 and I3 have been set to "sensor"? From the Qubino's perspective, there might be only one sensor, which is now triggered by both inputs. And hence produce the same payload.
If I have time, I'll change I3 to another notification type (e.g. motion detection) and see what happens.
Keep you posted.
Re: Can't get I2 or I3 input work - Qubino dimmer ZMNHDD1
Posted: Sunday 17 March 2019 14:54
by kimhav
Looking to make use of L2 as a virtual switch to switch on Philips Hue bulbs and it seems that there are some various configuration to enable and make use of the l2 virtual switch. What is correct way and easiest way of making this happen in Domoticz? Asking since there seems to be at least two different ways of doing this and also is there a need to set parameter 100 to "sensor binary"? Asking since I've set parameters 100 to what is being discussed in this thread and maybe expected that an additional Device would show up in Domoticz (but it isn't guess it's not clear to my which groups the node id should be added to and why...).
What is the recommended way?