Any update on this?

Any updates on the issue with the Command Class: Locked(Advanced) with Kwikset Door locks? This is the error I continue to receive whenever the door is lock/unlocked through Domoticz or manually: 2020-09-21 21:44:06.431 Error: OpenZWave: Value_Changed: Tried adding value, not succeeded!. Node: 45 ...

After some research I found this: https://github.com/domoticz/domoticz/issues/2642, also there is additional information about the issue several posts down. What I did to make it work was create dummy or virtual switches (one for each iDetect device)and used dzvents to activate the dummy switch when ...

Thanks for your hard work in this, it works fine but there is one issue. First I'm on a RPI3 B, latest Domoticz beta, Asus RT-AC86U Merlin and it's shares it's data with the main Domoticz machine that is also running on a pi. All of the other sensors and devices on the pi with iDetect share their ...

Look under Active: it says active (exited), it should be active (running). Try sudo /etc/init.d/domoticz.sh restart then sudo /etc/init.d/domoticz.sh status to see if this helps. It looks like you are missing libssl.so.1.1. Are you running the beta version, if so sometimes it has issues and needs to ...

Sorry for the late reply, did you get it fixed?

Thanks for the clarification. One question - if checkFirst() never work for uservariables then why has this script been running fine with no errors for several years? That's all I wanted to know from the beginning. Sorry for any problems caused, I just wanted an answer to my question. Thanks for ...

Waaren, Check the dzvents documentation, everything is there. Section 2.3.0 it says: "Added more options to the various commands/methods: e.g. myDevice.switchOff().silent(), .forSec(), .forHour(), .afterHour(), .repeatAfterSec(), .repeatAfterMin(), .repeatAfterHour(), .withinHour() and .checkFirst ...

I've been checkFirst() with a uservariable for a long time. Just noticed a lag and traced it back to error on line 45 and 91 of the script below. (2019-10-28 08:16:00.511 Error: dzVents: Error: (2.4.29) ...icz/scripts/dzVents/generated_scripts/Garage Door V2.lua:91: attempt to call field 'checkFirst ...

Great idea. Isn't it great that there's more that one way to get to the same point.

Wouldn't your script have to run twice on every motion ON? The first time when there is motion the light comes on, then run second time due to the device change of the light? Am I missing something?

This is what I ended up doing. return { on = { devices = {'PIR*','LIT*'} }, execute = function(domoticz,item,triggerInfo) local timeValue = 6 --minutes of time delay if item.name:sub(1,3) == 'PIR' then if item.active then domoticz.devices('LIT' .. item.name:sub(4)).cancelQueuedCommands() domoticz ...

I was planning on doing something similar if I can't access the device que.

I just wanted to access the que to see if there was already an off or on scheduled. Thanks for your help.

This may be off topic but Is there a way to check the QueuedCommands for a device?

I'm working on the code for this this morning and this is what I have so far. This is just for the motion activation side, I haven't done the portion that shuts off the device if it's manually triggered. return { on = { devices = {'PIR*'} --motion sensor }, execute = function(domoticz,device ...

Thanks for the example, with all the new code changes in dzVents it's made coding much shorter and easier. Kudos to dannybloe!

I'll need to re-visit all my old dzVent scripts and make updates.

PIRDevice is the motion sensor, domoticc.devices(PIRDevivice.name:sub(4)) is the device being switched. i.e. - I have a motion sensor named PIRgarage_lights, the switched relay is named garage_lights. I have many motion sensors all starting with PIR ending with the name of associated relay or switch ...

Thanks, it was written for an earlier version of dzVents, I haven't been reading the release notes as well as I should have. I corrected the outdated triggerInfo.type with isDevice or isTimer. I want the device to shut off after given time after the motion device (PIR) shuts off. So if there is ...

I have an issue and I'm probably just missing something. However I'm doing this so several motion detectors can be use in one script: return { on = { devices = {'PIR*'}, timer = {'every minute'} }, execute = function(domoticz,device,triggerInfo) if triggerInfo.type == domoticz.EVENT_TYPE_DEVICE and ...

I know this is late but I haven't checked Domoticz in a while. I had this issue several months ago. After checking all of my scripts and disabling and enabling each individual script to find the culprit, nothing was positive. I even replaced the sd card on the PI, no help. What I ended up doing to ...

I have a bunch of bluetooth devices (cell phones) that get pinged every so often to determine if they are near. If they are near the shell script reports that the bluetoooth device.text is "Home". They are each named differently except I added a " OCC" to the end of each to separate which devices ...