I have problems in PaperUI (openhab 2.1) with the integration of the motion detector Steinel IS 140-2.
This thing seems not to be in the z-wave database.
The manufacturer has provided a complete z-wave description: [Steinel-Manual](http://www.steinel.de/out/steinel_relaunch/pictures/media/bdal2_110043503.pdf)
There is information here on how to add devices to the database.
After adding the device in the z-wave database:
I copied the XML-data from the database in my node.xml-file.
But: I can’t see the (new) defined channels in PaperUI or Habmin.
I have no idea what’s wrong.
If the device has been approved and linked in to the binding, then you need to update to the latest snapshot.
The node XML files are totally different files than the XML files in the database so copying the database file over the node file will not work (as you’ve found ).
@ubuntu_Joe Where did you buy this sensor IS 140-2 Z-Wave? (country?/dealer?/eu-version?)
The STEINEL-hotline told me, that in germany I can’t buy it yet. Thanks.
I am currently trying to set up such a sensor with openHAB2 (2.2-SNAPSHOT). My device claims to be of Type:Id 0002:1A72 which is apparently not yet approved (and thus not in the snapshot binding):
If I can help to perform some testing, please let me know.
This was only added to the database yesterday. I’ll do an update tonight.
In case anyone else tries to include the Steinel L 810 IHF sensor switched up- and downlighting with z-wave SNAPSHOT 2.3.0:
After a number of trials with no success I managed to get it included.
I am using a Raspy Zero W with Razberry and Openhabian 2.2.
1.) Exclude the 810 IHF via Habmin by briefly pressing the key on the L 810 IHF ( I did this because of my retries before).
2.) Set the Z-Wave Controller to High power inclusion
3.) Locate the z-Wave controller directly near the 810 IHF
4.) start inclusion on L810 by briefly pressing the button
5.) Begin searching via z-wave binding
6.) L 810 IHF appears in inbox of Paper UI
7.) Change parameters of the L 810 IHF via Habmin only
What did not work with my configuration:
- inclusion via network wide search
- inclusion via nearby switch (a Fibaro is located 2 m to the IHF 810)
Hope this helps someone else…
@Ren001: Did you manage to get motion and luminance reports from the device? I had no problems with inclusion, but the device is reporting absolutely nothing to OH. The only usable channel is switch_dimmer, it allows me to switch the light ON/OFF via UI, but all the other 8 channels semm to be useless at the moment. I set accociations for lifeline, motion and luminescence to the controller (tried in Habmin and PaperUI) but nothing changes. Any ideas?
Same issue here:
Inclusion is working and I can set the value of lux when the lamp will be switched on – but no response from the device at all. Looks like a one way street…
Well, I am meanwhile one step further and the device now reports motion detection reliably. I set it to Slave_Mode = 2 (bit 1 set) and set ALL association groups to the controller (I just wanted to see in the logs if anything will be ever sent).
The important association was the one for the association group “Control: Key01”.
After that the device reports motion on the channel “alarm_burglar2”. It is set to ON if motion is detected and then switches back to OFF after 8-9 seconds.
I think that the naming of the channels and associations groups is very unfortunate. Probably the device database needs to be updated for this device.
However I could not get any luminance value so far. What is your configuration? And which version do you have? I have 1.0
is this case solved? I am in considderation of buying this sensor, but would like to be certain that it actually works
BTW. What is the experience with this particular sensor?
I was told from a local suplier that this was taken of production (I could only guess due to small selling numbers) so I jumpted and bought 3 of them.
It has all the functionallity I wanted and the guys who added this to the z-wave library did a great job with explaining text and so on!
So get it while you can
I got it working with light control (not slave mode) and still reporting motion.
I’ve integrated a Steinel 140-2 Motion Detector successfully in Openhab. I’m getting values in channels
So i’m getting everything i need to interact with other devices. To get luminance infos set parameter Global_Light to 0.Otherwise the device awaits luminance information from another z-wave device. The parameters “time” and “light” set’s duration for the switch relay and the lumanince threshold for switching the relay. I left parameter “Slave Mode” to 0.
I don’t have to set any associations group parameters to get the device work.
What is the difference between switch_binary and switch_binary3?
I also cant figure out the difference between sensor_luminance and sensor_luminance2. I would wish that it is a interval difference, because in my opinion the luminance value max out at 2000 very easily. Otherwise a great product.
I just mounted a Steinel L 810 incl. motion sensor and included it in my system.
It seems it is currently flooding my z-wave network according to the openhab debug log always with the same event:
2019-10-01 16:42:48.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-10-01 16:42:48.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-10-01 16:42:48.727 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 16 07 60 0D 02 01 20 01 00 A8
2019-10-01 16:42:48.731 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler, type=Request, dest=22, callback=0, payload=00 16 07 60 0D 02 01 20 01 00
2019-10-01 16:42:48.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler, type=Request, dest=22, callback=0, payload=00 16 07 60 0D 02 01 20 01 00
2019-10-01 16:42:48.735 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-10-01 16:42:48.736 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:DONE)
2019-10-01 16:42:48.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: resetResendCount initComplete=true isDead=false
2019-10-01 16:42:48.740 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-10-01 16:42:48.742 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_BASIC, endpoint 2
2019-10-01 16:42:48.743 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY not supported
2019-10-01 16:42:48.745 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2019-10-01 16:42:48.746 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 22: Basic report, value = 0
2019-10-01 16:42:48.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-10-01 16:42:48.750 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint=2, command class=COMMAND_CLASS_BASIC, value=0
2019-10-01 16:42:48.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:5a95239b:node22:alarm_burglar2 to OFF [OnOffType]
2019-10-01 16:42:48.755 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
2019-10-01 16:42:48.756 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@dcb6f5.
2019-10-01 16:42:48.758 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-10-01 16:42:48.759 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-10-01 16:42:48.761 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-10-01 16:42:48.762 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
Any idea if that is normal or what might be wrong?
It meanwhile stopped. Not sure what caused this. Now it seems to behave as expected with turning ON when motion detected and OFF (only one time) if not.