Outdoor Z-wave PIR

[lost]

In Germany the Company „Steinel“ is New to z-Wave. They are Known for Lights and Sensors.
They sell a IS-140 2 PIR.
I have no experience with it.

Hello,

No experience with this one as well, but ability to control an external light (as non z-wave version) directly (relay included) + reporting movement using z-wave looks interesting for a lighting PIR replacement (i.e having AC power). Don't know if this one have a config file to describe the device for OZW, but if this needs to be done documentation also looks very good and there is range+sensitivity tuning (usually, you only have sensitivity).
https://www.steinel.de/out/steinel_rela ... 043503.pdf

Drawback for standalone use is this is not a battery device (+ for an alarm system, AC off = no detection).

[Jan Jansen]

IS-140 2 PIR is interesting indeed. It seems to be supported see WIKI >> Z-wave >> OZW:Supported devices ( https://github.com/OpenZWave/open-zwave ... ter/config ).

Is there someone who has succeeded to connect this device to Domoticz?

[C4rtm4N]

Is there someone who has succeeded to connect this device to Domoticz?

Bought one from Amazon for £99 last week, it connected to Domoticz (recent Beta) no problem & worked immediately.

I'm very happy and will be getting a 2nd one for the side of the house after Christmas!

[Jan Jansen]

Bought one from Amazon for £99 last week, it connected to Domoticz (recent Beta) no problem & worked immediately.

I'm very happy and will be getting a 2nd one for the side of the house after Christmas!

Thanks

[garrop]

Hi @C4rtm4N,

Could you post how your settings for the IS-140 2?

I recently purchased one, but I keep getting error messages (timeout notificatons) and eventually it went dead. It is close to my RPi and for some time when powered on would work fine for some 20 minutes and then nothing. It does not even work as a simple detection-switch device.

I am not sure if it is a faulty unit or else it is my settings, as the unit seems to be created for the Steinel hub.

After quite power on-off attemps, the unit is dead, my Razberry sees it after rebooting, but it does not communicate with it. I forgot to mention right from the beginning, I never got light and movement sensor readings (they do not show up in my devices list either)

Any help will be greatly appreciated.

[hestia]

Hi

Could you post how your settings for the IS-140 2?

Code: Select all

Configuration

Request current stored values from device

1. Duration of light after motion detection: 
180
 (seconds) (actual: 180)

Available settings: 5-900 seconds.
Last Update: 2020-04-05 21:50:53

2. Light threshold: 
2000
 (lx) (actual: 2000)

2000 - is used as daylight (always night mode). 0 - run Learn ambient light sequence. 2-1999 lux.
Last Update: 2020-04-05 21:50:53

5. Sensitivity: 
25
 (%) (actual: 25)

Potentiometer State. Available settings: 2-100%.
Last Update: 2020-04-05 21:50:53

8. Global Light: 

External ambient light value.
Last Update: 2020-04-05 21:50:53

9. Slave Mode: 

Disable local control.
Last Update: 2020-04-05 21:50:53

10. Off behaviour: 
10
 (actual: 10)

Off behaviour (timeout). 0 - Lamp is switched off and remains so until any new motion event (local or remote) is received. 1 to 100 (Default) timeout: 1 second (1) to 100 seconds (100) in 1-second resolution. 101 to 200 timeout: 1 minute (101) to 100 minutes (200) 1-minute resolution. 201 to 209 timeout: 1 hour (201) to 9 hours (209) in 1-hour resolution. 255 Lamp is switched off for TIME (cfg 1). It does not wait for a motion event and works normally via current motion evaluation.
Last Update: 2020-04-05 21:50:53

11. On behaviour: 
255
 (actual: 255)

On behaviour (timeout). Similar than Off behaviour. Available settings: 0-255. 0 - Lamp is switched on and remains so until any new motion event (local or remote) is received. It then works normally via current motion evaluation. Notice - during the day, this mode cannot be ended remotely due to motion events not being transmitted - only via local motion sensor if enabled.
Last Update: 2020-04-05 21:50:53

12. On behaviour time over: 
204
 (actual: 204)

On behaviour time over (timeout). Available settings: 0-255. 0 No additional waiting for motion. 1 to 100 timeout: 1 second (1) to 100 seconds (100) in 1-second resolution. 101 to 200 timeout: 1 minute (101) to 100 minutes (200) 1-minute resolution. 201 to 209 (Default) timeout: 1 hour (201) to 9 hours (209) in 1-hour resolution. 255 Never stop waiting before motion.
Last Update: 2020-04-05 21:50:53

13. Sequence On-Off behaviour: 
204
 (actual: 204)

Available settings: 0-255. 0 - Lamp is switched off and remains so until any new motion event (local or remote) is received. 1 to 100 timeout: 1 second (1) to 100 seconds (100) in 1-second resolution. 101 to 200 timeout: 1 minute (101) to 100 minutes (200) 1-minute resolution. 201 to 209 (Default) timeout: 1 hour (201) to 9 hours (209) in 1-hour resolution. 255 device ignores ON - OFF sequence and uses OFF behavior.
Last Update: 2020-04-05 21:50:53

14. Sequence Off-On behaviour: 
204
 (actual: 204)

Available settings: 0-255. 0 - Lamp is switched on and remains so until any new motion event (local or remote) is received. It then works normally via current motion evaluation. Notice - during the day, this mode cannot be ended remotely due to motion events not being transmitted - only via local motion sensor if enabled. 1 to 100 timeout: 1 second (1) to 100 seconds (100) in 1-second resolution. 101 to 200 timeout: 1 minute (101) to 100 minutes (200) 1-minute resolution. 201 to 209 (Default) timeout: 1 hour (201) to 9 hours (209) in 1-hour resolution. 255 device ignores OFF - ON sequence and uses ON behaviour.
Last Update: 2020-04-05 21:50:53

15. Sequence timing: 
10
 (actual: 10)

Available settings: 10-50.
Last Update: 2020-04-05 21:50:53

16. Motion Off behaviour: 
0
 (actual: 0)

Available settings: 0-255. 0 (Default) BASIC SET to Motion sensor endpoint ignored, BASIC to root is mapped to relay endpoint, motion sensor still enabled. 1 to 100 timeout: 1 second (1) to 100 seconds (100) in 1-second resolution. 101 to 200 timeout: 1 minute (101) to 100 minutes (200) 1-minute resolution. 201 to 209 timeout: 1 hour (201) to 9 hours (209) in 1-hour resolution. 255 BASIC SET to Motion sensor endpoint ignored, BASIC to root is mapped to relay endpoint, motion sensor still disabled
Last Update: 2020-04-05 21:50:53

I don't have any switch, nor light connected directly to the PIR

Version: 2020.1 (build 11875)
Build Hash: 8c5c9826f-modified
Compile Date: 2020-04-03 08:25:18

And previous betas
Hope this help!

[garrop]

Thanks for your quick reply!!

Values for 8 Global light and 9 Slave mode do not show up in your post (did not get copied and those seem to be the key ones from what I am guessing from various info found in the net). Could you please confirm on those two?

I will update my domoticz version asap, reset the STEINEL unit, relink and see if I can make it function properly. I will post back.

Take care

[hestia]

Values for 8 Global light and 9 Slave mode do not show up

sorry too quick copy/paste !!!

8 Global light: disable
9 Slave mode: normal mode with lifeline error signalisation

Good luck and take care too

[garrop]

Merci infiniment!

It is quite curious, I did have those same values when first paired and was getting quite a weird behaviour from the unit. It would work fine at the very beginning and then bunch of timeouts and dead unit during the same day...

Anyway, I did reset the unit and now functions as a non-connected one just fine. Over he weekend I will backup my domoticz Raspbian installation, will update to the latest domoticz version and will pair once again the unit and see what happens.

I will post back with victory or total failure.

Kiind regards

[garrop]

For the record and help of others, this is what I did and how I went:

- I upgraded to 2020.1 on my RB3 w/o updating to buster

- Realized I needed to go to buster for the dependencies, so with my updated DZ already in place, I updated raspbian.

- Reboot and domoticz was able to launch and besides one sensor (Philio PTS02) which is giving me daily troubles, the rest stayed sound and safe.

- Activated the add node state on DZ

- Activated the IS 140 to pair and join the DZ server which went smooth as well. The light and movement sensors were detected and included fine.

- All the way until the twilight, the unit was fine.

- Tried the light after that and bump, it operated fine, BUT...

Despite the fact the unit was set to turn off the light after 3 minutes (default) the light stayed on and on and on. I tried switching it off from DZ to no avail.

I had to cut the power from the unit and after that the unit died and does not respond any more. Luckly enough it has gone back to standalone mode, so at least I can have some light if I was to arrive late at home (which will not happen in a while

I have no clue how to solve this issue. I will try and contact the manufacturer because it might be just a faulty unit.

Best regards.

[hestia]

I had to cut the power from the unit and after that the unit died and does not respond any more [...] it might be just a faulty unit.

Probably, I think I did this several times w/o issue

Despite the fact the unit was set to turn off the light after 3 minutes (default) the light stayed on and on and on

I don't use this. I just use the PIR to trigger a dzVents script that switch on the light and after switch it off

[garrop]

Thanks again

Could you share your script, as I might take that road as well?

I will post back with any progress.

Take care.

[hestia]

there is this topic
https://www.domoticz.com/forum/viewtopi ... t=29834[*] where I've suggested my script (I did several more versions since), you could find less simple by waaren and probably better...
I've also written 2 scripts, more for my Christmas tree than for outside
They are simple.

one to switch on

Code: Select all

-- Pilotage Smart Plug

local SBDY_RESULT = 451 -- dummy which knows if anyone at home
local PIR = 756
local PLUGS = {965}
local TRIGGER = {SBDY_RESULT, PIR} -- {SBDY_RESULT, Détecteur Salon}
local DOMAIN = 'SmartPlug On' -- For logging, as you like!

return {
    active = true,
    logging = {
	level = domoticz.LOG_ERROR, -- Select one of LOG_DEBUG, LOG_INFO, LOG_ERROR, LOG_FORCE to override system log level
	marker = DOMAIN
	},
	on = {
        devices = TRIGGER,
        },

	execute = function(dz, the_device, triggerInfo)
	local LOG_LEVEL = dz.LOG_INFO -- LOG_INFO, LOG_DEBUG, LOG_ERROR, LOG_FORCE
	local ToON = false 
	 local plugDevice
    dz.log('*** start ' .. triggerInfo.type , dz.LOG_LEVEL)
    
    if the_device == dz.devices(SBDY_RESULT) then
        if dz.devices(SBDY_RESULT).level == 30 then -- somebody at home
            dz.log('Somebody arrive' , dz.LOG_LEVEL)
            ToON = true
    	end
    end
    if the_device == dz.devices(PIR) then
        if dz.devices(PIR).active then -- somebody at home
            dz.log('Somebody sans le salon' , dz.LOG_LEVEL)
            ToON = true
    	end
    end
    if ToON then
        for i1, l1 in ipairs(PLUGS) do
            plugDevice = dz.devices(l1)
            dz.log(i1 .. ' Device '.. plugDevice.name .. " (" .. plugDevice.id .. ") to ON" , dz.LOG_DEBUG)
            plugDevice.switchOn().checkFirst()
        end
    end        

end
}

one to switch off

Code: Select all

-- Pilotage Smart Plug
local PIR = 756
local PLUGS = {965}
local TRIGGER = {PIR} -- {Détecteur Salon}
local DOMAIN = 'SmartPlug Off' -- For logging, as you like!
local TIME_INTERVAL = 'every 5 minutes'
local MAX_TIME = 15

return {
    active = true,
    logging = {
	level = domoticz.LOG_ERROR, -- Select one of LOG_DEBUG, LOG_INFO, LOG_ERROR, LOG_FORCE to override system log level -- normal = LOG_ERROR
	marker = DOMAIN
	},
    on = {
        devices = TRIGGER,
        timer = {TIME_INTERVAL},
  	},

        
    execute = function(dz, device, triggerInfo)
    local LOG_LEVEL = dz.LOG_INFO -- LOG_INFO, LOG_DEBUG, LOG_ERROR, LOG_FORCE
                    
local the_device = dz.devices(PIR)
local plugDevice

    if not the_device.active then        
        dz.log('OFF ' , dz.LOG_FORCE)
        if the_device.lastUpdate.minutesAgo  >= MAX_TIME then
            dz.log('To OFF', dz.LOG_FORCE)
            for i1, l1 in ipairs(PLUGS) do
                plugDevice = dz.devices(l1)
                dz.log(i1 .. ' Device '.. plugDevice.name .. " (" .. plugDevice.id .. ") to OFF" , LOG_LEVEL)
                plugDevice.switchOff().checkFirst()
            end
        end
    end    
    
    dz.log(the_device.name .. ' ' .. the_device.state .. ' ' .. the_device.lastUpdate.minutesAgo .. ' minutes.', LOG_LEVEL)
 
 
end
} 

You could put "every minute" if you want to have 3 minutes
You could make it only with one
I think you could just put your light in PLUGS and just comment "--local SBDY_RESULT ="

[garrop]

Thanks once again.

This is just in the border between my abilities and my incompetency. I will give it a try after I spend some hours getting to know dzVents (which will help me enormously going forward).

I have also contacted Steinel (France) to enquiry if I have a faulty unit.

Best regards

[hestia]

hi
you should look at this
Auto-On, Auto-Off and Auto-OnOff
https://www.domoticz.com/forum/viewtopi ... 72&t=32031
didn't take the time to read it thoroughly

[garrop]

Cool stuff.

I will definitely dig into it.

Take care.