UserVariables not always set after Device Trigger Off[edit]
Moderator: leecollings
-
- Posts: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
In de case of the Z-wave Off command, no change.
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
-
- Posts: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Did some testing with the Z-Wave device and created an secundary script which triggers on the 2 UserVariable changes.
The original script to set the UserVariables send an email notification and the UserVariable change script also send a notification; The On command generates an email for both the UserVar's changes, the Off command not...
The original script to set the UserVariables send an email notification and the UserVariable change script also send a notification; The On command generates an email for both the UserVar's changes, the Off command not...
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
-
- Posts: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Here's the script I use to test the UserVariables, no rocket science.:
Here another test with the strange behaviour of the Z-Wave device and the expected behaviour of the "Badkamer verlichting2" dummy device;
Code: Select all
return {
on = {
variables = {'BadkVerwarmingOffTime','BadkVerwarmingOnTime'}
},
logging = {
level = domoticz.LOG_DEBUG, -- change to LOG_ERROR after you tested the script
marker = "Return::on::variables::"
},
execute = function(dz, item, info )
local function logWrite(str,level) -- Support function for shorthand debug log statements
dz.log(tostring(str),level or dz.LOG_DEBUG)
dz.notify(tostring(str))
end
logWrite('UserVarTestScript:'..item.name..' :: changed to:'..item.value)
end
}
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Have to admit I am intrigued by this. Can you try and switch names of the Zwave and virtual device and check again ? This to see if the issue is caused by the name or by the different device types ?
TIA
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: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Looks like it has something to do with the lenght of the devicename;
Devicename "Badkamer verlichtin" is working is expected
Devicename "Badkamer verlichting" is not working as expected
Devicename "Badkamer verlichtin" is working is expected
Devicename "Badkamer verlichting" is not working as expected
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
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: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Don't known if its matter, but thats a virtual/dummy device and i'm using a Z-Wave device.
When I use a dummy device with the name "Badkamer verlichting3", then it's also working fine; And the strange thing is... When I add a * the the "on" trigger in the script; "Badkamer verlichting*" both
Z-wave "Badkamer verlichting"
and
Dummy "Badkamer verlichting3"
are working as expected...
So;
Results in;
When I use a dummy device with the name "Badkamer verlichting3", then it's also working fine; And the strange thing is... When I add a * the the "on" trigger in the script; "Badkamer verlichting*" both
Z-wave "Badkamer verlichting"
and
Dummy "Badkamer verlichting3"
are working as expected...
So;
Code: Select all
return {
on = {
--timer = {"every minute"},
devices = {
--237,
"Badkamer verlichting*"
}}, -- 433 is sensor / isDevice Test switch
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
-
- Posts: 94
- Joined: Thursday 24 November 2016 14:55
- Target OS: Linux
- Domoticz version: >=Béta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
Any idea what's causing it?
Domotica/graphs "freak" :)
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
NUC8i3BEH(8gb/250gb),
Lubuntu 19.04,
Aeotec Z-Stick S2(Gen5)
HarmonyElite
HUE(5 bulbs, 2 blooms)
NetAtmo(complete setup)
MiLight iboxV6(2 MiLightBulbs)
IP-Cam
https://www.frijduurzaam.nl
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: UserVariables not always set after Device Trigger Off[edit]
I am sorry but no. I cannot reproduce the issue even with the exact same names. Until now no other forum member reported a similar issue with zwave devices so not much to work on either. Maybe if you switch on debug mode in dzVents and log to an OS file to show all relevant lines we will see more.
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
Who is online
Users browsing this forum: Bing [Bot], habahabahaba and 1 guest