PIR status not resetting

[Dave21w]

I have PIR connected via and RFXCom, it is seen as a PT2262 device and only sends an ON signal, I have added it as PIR and set the off delay to 5 secs, each time it is triggered you can see the "last seen" time update and then 5 seconds later it updates again because it has been reset to off I assume because of this setting :-

Off Delay: 5 (Seconds) 0 = Use sensor time

However the PIR shows as permanently on according to the device unless I manually refresh the webpage, if the time can be seen to update without a page refresh why does the device status not change as well, is this normal?

TIA

[Geitje]

You mean it only switches back to off when you manually refresh the webpage? What browser do you use? In Chrome my motions sensors switch back off without refreshing.

[azonneveld]

It probably creates two devices. One device for ON and one device for OFF.
Create another dummy device to hold the actual status, and control it from LUA.

Code: Select all

for deviceName,deviceValue in pairs(devicechanged) do
    
    if (deviceName=='Kerui 01 Open') then
        commandArray[#commandArray + 1] = {['Kerui 01 Contact'] = 'On'}
    end
    if (deviceName=='Kerui 01 Closed') then
        commandArray[#commandArray + 1] = {['Kerui 01 Contact'] = 'Off'}
    end
end

[Dave21w]

Yes it only switches back to off if i refresh the page however this is when i use and RFXCom to recieve the signal, if I do the same thing with an RFLink the status changes as it should. In fact if I use both recievers at the same time and create 2 devices (one for each) and have them next to each other on the switches tab one resets and the other doesn't even though they are both setup exactly the same including the Off delay in the settings :-

Off Delay: 5 (Seconds) 0 = Use sensor time

The sensor does not send an off, it is only detected as one device and just sends an ON so a reset in domoticz back to OFF is essential.

Sorry for the delay in replying, thought I'd put my question in another section.

[Geitje]

That is strange. Seems related to RFXcom then?
Then I would use the RFlink

You could bypass this by creating a separate event (blocky for example) which: If: on -> switch sensor of after 3 seconds. Kind of dirty way....