Easy to use, 100% Lua-based event scripting framework.
Moderator: leecollings
mvermand
Posts: 1 Joined: Friday 18 January 2019 14:36Target OS: Raspberry Pi / ODroidDomoticz version:
Contact:
Post
by mvermand Friday 18 January 2019 14:54
Hi,
I have a Fibaro Dimmer 2 switch and I want to create a script that does different things in case someone presses the switch and in case the switch was controlled by Domoticz when a Sensor detects motion.
Code: Select all
return {
on = {
devices = {
'Dimmer Hall', 'Sensor Hall'
},
},
execute = function(domoticz, device)
domoticz.log('Trigger: ' .. device.name .. ' s:' .. device.state, domoticz.LOG_INFO)
local DimmerHallName = 'Dimmer Hall'
local DimmerHalDevice = domoticz.devices(DimmerHallName)
if (device.name == DimmerHallName and device.state == 'On') then
-- Someone pressed the Dimmer Switch => do some stuff (**B)
end
local SensorHallName = 'Sensor Hall'
if (device.name == SensorHallName and device.state == 'Open') then
-- The sensor detected motion => turn on Dimmer at 20%
DimmerHalDevice .switchSelector(20); -- (**A)
DimmerHalDevice .switchOff().afterSec(60);
end
end
}
This script does not work correctly because when the Dimmer is activated by command **A, the Dimmer is switched on but that triggers a new iteration of the script with trigger device == DimmerHall, ending up at **B.
So is it possible to detect in script if the Dimmer was controlled by human or by Script?
In that case, I could check on that condition in the if statement of block **B.
Thanks
JuanUil
Posts: 497 Joined: Friday 22 May 2015 12:21Target OS: Raspberry Pi / ODroidDomoticz version: 4.11083Location: Asten NB Nederland
Contact:
Post
by JuanUil Friday 18 January 2019 16:11
I Don't know DzEvents but in Lua I would say:
Your mind is like a parachute,
waaren
Posts: 6028 Joined: Tuesday 03 January 2017 14:18Target OS: LinuxDomoticz version: BetaLocation: Netherlands
Contact:
Post
by waaren Friday 18 January 2019 22:27
mvermand wrote: ↑ Friday 18 January 2019 14:54
I have a Fibaro Dimmer 2 switch and I want to create a script that does different things in case someone presses the switch and in case the switch was controlled by Domoticz when a Sensor detects motion.
This script does not work correctly because when the Dimmer is activated by command **A, the Dimmer is switched on but that triggers a new iteration of the script with trigger device == DimmerHall, ending up at **B.
Use option silent() to switch without triggering the script again.
in the
wiki
silent(): Function. No follow-up events will be triggered: mySwitch.switchOff().silent()
or
mySwitch.dimTo(xx).silent()
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>>
dzVents wiki
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Wednesday 17 April 2019 8:23
waaren wrote: ↑ Friday 18 January 2019 22:27
Use option silent() to switch without triggering the script again.
in the
wiki
silent(): Function. No follow-up events will be triggered: mySwitch.switchOff().silent()
or
mySwitch.dimTo(xx).silent()
Hi waaren
On my side .silent() seems to no longer work
viewtopic.php?f=6&t=27607&p=211804#p211804
I don't know if it's due to zwaves devices (because it is ok with dummy devices) or due to DzVents
Do you use .silent() with zwaves devices?
I've updated with the previous beta with no improvement
waaren
Posts: 6028 Joined: Tuesday 03 January 2017 14:18Target OS: LinuxDomoticz version: BetaLocation: Netherlands
Contact:
Post
by waaren Wednesday 17 April 2019 10:34
dzVents does not do anything special for zwave type devices. It sends the same commands to the domoticz main program as for other switchtypes.
I tested with latest Beta on my zwave switch. (I do not own a zwave dimmer so cannot test this)
Methods
switchon.silent()
switchon.checkFirst().silent()
toggleSwitch.silent()
all behave as expected. (They do not trigger an event)
testscript:
Code: Select all
local test = {1192; 676, 1252} -- 676 is zwave switch
return {
on = { timer = { "every minute" },
devices = test },
logging = { level = domoticz.LOG_DEBUG,
marker = "Zwave test" },
execute = function(dz, item)
if item.isTimer then
zwaveDevice = dz.devices(676)
zwaveDevice.toggleSwitch().silent()
dz.log('State of Device '.. zwaveDevice.name .. " (" .. zwaveDevice.id .. ") will be changed. Now: " .. zwaveDevice.state, dz.LOG_DEBUG)
zwaveDevice.dump()
else
dz.log(".............. This should not happen !!",dz.LOG_ERROR)
end
end
}
If you can also use the dump() method on the zwave device with the unexpected behavior and report back with the relevant loglines of this dump() ?
Relevant is:
Code: Select all
2019-04-17 10:02:00.512 Status: dzVents: > lastUpdate:
2019-04-17 10:02:00.522 Status: dzVents: > msAgo: 60250
2019-04-17 10:02:00.524 Status: dzVents: > deviceId: 00000E01
2019-04-17 10:02:00.524 Status: dzVents: > deviceSubType: Switch
2019-04-17 10:02:00.524 Status: dzVents: > _state: Off
2019-04-17 10:02:00.525 Status: dzVents: > hardwareName: Aeotec Zwave stick
2019-04-17 10:02:00.525 Status: dzVents: > _adapters:
2019-04-17 10:02:00.526 Status: dzVents: > 1: Switch device adapter
2019-04-17 10:02:00.527 Status: dzVents: > _data:
2019-04-17 10:02:00.527 Status: dzVents: > switchTypeValue: 0
2019-04-17 10:02:00.529 Status: dzVents: > hardwareTypeValue: 21
2019-04-17 10:02:00.529 Status: dzVents: > switchType: On/Off
2019-04-17 10:02:00.530 Status: dzVents: > deviceType: Light/Switch
2019-04-17 10:02:00.532 Status: dzVents: > rawData:
2019-04-17 10:02:00.532 Status: dzVents: > 1: 0
2019-04-17 10:02:00.532 Status: dzVents: > nValue: 0
2019-04-17 10:02:00.532 Status: dzVents: > hardwareType: OpenZWave USB
2019-04-17 10:02:00.534 Status: dzVents: > baseType: device
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>>
dzVents wiki
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Wednesday 17 April 2019 22:57
Thank waaren
the script
Code: Select all
local test = {205; 142, 206} -- 142 is zwave switch
return {
on = { timer = { "every minute" },
devices = test },
logging = { level = domoticz.LOG_DEBUG,
marker = "Zwave test" },
execute = function(dz, item)
if item.isTimer then
zwaveDevice = dz.devices(142)
zwaveDevice.toggleSwitch().silent()
dz.log('State of Device '.. zwaveDevice.name .. " (" .. zwaveDevice.id .. ") will be changed. Now: " .. zwaveDevice.state, dz.LOG_DEBUG)
zwaveDevice.dump()
else
dz.log(".............. This should not happen !!",dz.LOG_ERROR)
dz.devices(142).dump()
end
end
}
the main result is:
2019-04-17 22:55:27.033 (Dummy1) Light/Switch (test inter 205)
2019-04-17 22:55:27.017 Status: User: admin initiated a switch command (205/test inter 205/Off)
2019-04-17 22:55:27.198 Status: dzVents: Info: Zwave test: ------ Start internal script: TestSilent: Device: "test inter 205 (Dummy1)", Index: 205
2019-04-17 22:55:27.199 Status: dzVents: Error (2.4.17): Zwave test: .............. This should not happen !!
2019-04-17 22:55:27.199 Status: dzVents: Info: Zwave test: ------ Finished TestSilent
The log with dump
Spoiler: show
19-04-17 22:50:01.394 OpenZWave: Domoticz has send a Switch command!, Level: 255, NodeID: 23 (0x17)
Tested with 5 zwaves switches with the same result
waaren
Posts: 6028 Joined: Tuesday 03 January 2017 14:18Target OS: LinuxDomoticz version: BetaLocation: Netherlands
Contact:
Post
by waaren Wednesday 17 April 2019 23:29
hestia wrote: ↑ Wednesday 17 April 2019 22:57
the main result is:
2019-04-17 22:55:27.033 (Dummy1) Light/Switch (test inter 205)
2019-04-17 22:55:27.017 Status: User: admin initiated a switch command (205/test inter 205/Off)
2019-04-17 22:55:27.198 Status: dzVents: Info: Zwave test: ------ Start internal script: TestSilent: Device: "test inter 205 (Dummy1)", Index: 205
2019-04-17 22:55:27.199 Status: dzVents: Error (2.4.17): Zwave test: .............. This should not happen !!
2019-04-17 22:55:27.199 Status: dzVents: Info: Zwave test: ------ Finished TestSilent
Tested with 5 zwaves switches with the same result
OK. Looks like your dimmer type of switches reacts different than my On / Off type switch.
Can you please test if silent() method works for an On/Off type of Zwave device like I see on my system ?
Can you please test what happens if you use dimTo(0).silent() on the dimmer devices ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>>
dzVents wiki
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Wednesday 17 April 2019 23:50
with an On/Off device => It was already tested => This should not happen !!
It is an On/Off device (Switch Type in Edit) but it is a "Qubino (Goap) ZMNHDD1 Flush Dimmer+" as hardware
Spoiler: show
019-04-17 23:44:06.361 Status: User: admin initiated a switch command (205/test inter 205/On)
the dump log
Spoiler: show
2019-04-17 23:41:15.126 (Dummy1) Light/Switch (test inter 205)
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Thursday 18 April 2019 0:15
a new test with the same device
w/o the dump
Spoiler: show
2019-04-18 00:06:00.413 Status: dzVents: Info: Zwave test: ------ Start internal script: TestSilent:, trigger: every minute
w the dump
ok -> Off
Spoiler: show
2019-04-18 00:12:00.530 Status: dzVents: > ruleMatchesTime()
ko -> On
Spoiler: show
2019-04-18 00:13:00.561 Status: dzVents: > updateCounter()
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Thursday 18 April 2019 0:34
with dimTo(50)
Curiously, 1 of 2 times the switch turns off
and 1 of 2 times it is ok
log
Spoiler: show
2019-04-18 00:23:00.648 Status: dzVents: Info: Zwave test: ------ Start internal script: TestSilent:, trigger: every minute
with dump
Spoiler: show
2019-04-18 00:28:01.843 (Z-Wave Plus Z-Stick Gen5) Usage (Parking Watt)
waaren
Posts: 6028 Joined: Tuesday 03 January 2017 14:18Target OS: LinuxDomoticz version: BetaLocation: Netherlands
Contact:
Post
by waaren Thursday 18 April 2019 0:38
hestia wrote: ↑ Wednesday 17 April 2019 23:50
with an On/Off device => It was already tested => This should not happen !!
It is an On/Off device (Switch Type in Edit) but it is a "Qubino (Goap) ZMNHDD1 Flush Dimmer+" as hardware
If I look at the dump I see a value between 0-100 for level and for lastlevel. For the On/Off type Zwave device on my system these values can only be 0 or 255. So somewhere in the domoticz and/or zwave code your device 205 is seen as a device that can be set to a certain dimLevel.
I don''t know if that is causing the difference in handling the NOTRIGGER option (= the domoticz equivalent of silent() in dzVents)
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>>
dzVents wiki
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Thursday 18 April 2019 0:40
with dimto[0)
Spoiler: show
2019-04-18 00:37:56.202 Status: dzVents: Write file: /home/pi/domoticz/scripts/dzVents/generated_scripts/TestSilent.lua
KO when from On to dimto(0)
OK when from dimto(0) to dimto(0)
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Thursday 18 April 2019 0:49
waaren wrote: ↑ Thursday 18 April 2019 0:38 hestia wrote: ↑ Wednesday 17 April 2019 23:50
with an On/Off device => It was already tested => This should not happen !!
It is an On/Off device (Switch Type in Edit) but it is a "Qubino (Goap) ZMNHDD1 Flush Dimmer+" as hardware
If I look at the dump I see a value between 0-100 for level and for lastlevel. For the On/Off type Zwave device on my system these values can only be 0 or 255. So somewhere in the domoticz and/or zwave code your device 205 is seen as a device that can be set to a certain dimLevel.
I don''t know if that is causing the difference in handling the NOTRIGGER option (= the domoticz equivalent of silent() in dzVents)
waaren, perhaps I made a mistake on this test, because 205 is a dummy device that I've clicked
With the following tests, I more confident of the result
the zwawes are 76, 142, 198, 178, 443 (443 is On/Off, the others with level)
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Thursday 18 April 2019 0:55
I've found a real On/Off device and it was ok on 2 cycles On to Off to On
so it's look like it is about dimmers
Spoiler: show
2019-04-18 00:50:04.345 Status: OpenZWave: Received timeout notification from HomeID: 3795207774, NodeID: 47 (0x2f)
hestia
Posts: 361 Joined: Monday 25 December 2017 23:06Target OS: Raspberry Pi / ODroidDomoticz version: 2022.1Location: Paris
Contact:
Post
by hestia Wednesday 01 May 2019 20:34
I redo some testing:
before I put out of the electrical network the 3 devices I've worked on when the issue appeared
and I used a device that was ok before and that I didn't touch
I've got the issue even though when using dimTo(0) or dimTo(100), but all the devices with the same behaviour (some some, dimTo(0) is ok, for another one, KO)
Spoiler: show
2019-05-01 19:25:00.715 (Z-Wave Plus Z-Stick Gen5) Usage (Entrée Watt)
At that time (just before the issue arrived), as I had issue with new devices, I had upgraded to the last beta, and that when the issue appeared. I couldn't find in the log (too far) the previous version when I was ok.
In the log I founded the versions after.
Spoiler: show
Date,Time,Level,Host Name,Category,Program,Messages,
I've just upgraded to the last beta
Version: 4.10641
Build Hash: 9bcca3f7
Compile Date: 2019-05-01 16:47:33
same
blueberryPie
Posts: 18 Joined: Sunday 19 November 2017 20:30Target OS: Raspberry Pi / ODroidDomoticz version:
Contact:
Post
by blueberryPie Tuesday 28 September 2021 16:44
I see this thread seems to have diverged from the initial question. "Determine if switch was physically pressed or controlled by Domoticz".
If you look at the log of a device the last column is titled User and you can see what "User" is associated with each device event.
If dzVents then the User is indicated as : EventSystem//home/pi/domoticz/dzVents/runtime/dzVents.lua
If JSON or Web interface then the User is indicated as : Admin (IP: xxx.xxx.xxx.xxx)
If Z-Wave device the User is indicated as : Z-StickGen5
Looking at the device.dump() I don't see anything that relates to these different "Users".
It would be great to be able to get this information inside a dzVents script. Can this be done currently? If not this would be a nice feature to add.
The .silent is just a workaround in some situations but is not a solution for all cases. Using a number of virtual switches is another workaround but not a good solution.
Also as it turns out fading Dimmer devices generate "Set Level: x %" events from the device as they are dimming after a dzVents .silent() command so .silent() is not an option at all with dimmers.
Related topic -
How to switch silent with api?
Users browsing this forum: Google [Bot] and 1 guest
