I have the Aeotec 5th Generation Z-Wave controller on my OpenHAB 2.5.9-1 (On Raspi 3B+)
I have connected 3 Steinel IS 140-2 Z-Wave motion sensors which I want to control using OpenHAB. Two of them work without any problem. But one of them not.
I cannot switch it on/off using HABMin. If I click the switch (or relay) button in HABMin nothing happens. Paper UI says it is online.
I compared the configuration settings of one of the working sensors with the one which is not working - but I cannot see any difference.
This is my Z-Wave network:
1: Controller
2: 1st Steinel IS 140-2 Z-Wave (working)
3. 2nd Steinel IS 140-2 Z-Wave (not working)
4: 3rd Steinel IS 140-2 Z-Wave (working)
This is where the controller and sensors are located:
(the red one is the one which is not working)
The biggest distance between sensor and controller is between sensor 4 and the z-wave controller 1 and is around 15m.
Btw: for the other sensors I can see lots of polling messages coming up.
But for the broken sensor not. For the broken one I can only see DEBUG messages if I hit the button inside HABmin.
Don’t know if this ifnormation is useful or not.
I am not a log expert but I know that unfiltered DEBUG logs are needed for troubleshooting. The online log viewer may give some clues until the experts arrive here.
I forgot to mention that this sensor I already changed by a brand new one, because I thought it was defective. But the new one is just the same.
The log above comes from the new one - so the device itself should be fine - there is only something wrong with z-wave.
Maybe I’m wrong, but it looks like you’ve filtered your logs using something like grep. This has removed a lot of the content and makes the logs unusable. We need to have the complete logs - not filtered for node 3 or anything else.
Apologies if that’s not what you’ve done here, but every line starts with Node 3, so this is just how it looks to me.
Here the binding is reading the luminance and switch state - responses are fast and it looks fine to me. Clearly the channels are there and the device is working fine - as far as I can tell anyway.
it gets even more strange. Now the node 4 does not work anymore, but node 3 is now working, means switching on/off in HABmin.
Then I powered off my garage so node 3 and node 4 booted up.
Now node 3 is not working anymore but node 4.
It seems that I can only use one of node 3 or node 4 at same time!?!
I’m not sure what this log shows - as above, there is only any activity with node 3, which if I understand your statement above, is not working . The log shows it’s working fine - the same as the earlier log you provided, but there is no activity with node 4. I’d suggest to create a log showing activity with both devices - or at least clearly state what the log is meant to show.
sorry for the confusion. Here another log.
1st I switched node 3 on then off and again on and off.
The light on the garage did not follow - it keeps off.
Then I switched node 4 on and off and again on and off.
The light on the garage follwos exactly this on and off procedure.
What I also see is, there are two items for each Steinel (see screenshot from one of the prev. messages):
Switch
Relais
For node 3 if I set switch to on then it takes around 5 sec. and then the relais follows.
The light on the garage itself keeps off.
But for node 4 if I set switch to on then immediately the relais turns on as well and the light follows - don’t know if this information is helpful or not.
I created a simple Basic UI and created a screencast. There you can see that node 3 needs more time to set the relais to on whereas node 4 sets the relais immediately to on if I activate the switch. Again, don’t know if this is an useful information.
I really can’t see anything wrong here - from the logs, and the responses from the devices, it looks like it’s working fine to me… The one interesting point is that the commands are sent to the root node (ie unencapsulated), but the responses come back from EP-3. This tells me that the switch on the root endpoint is likely mapped to endpoint 3 and probably you should just use the EP3 command (which is the one called Relay Switch). (I’ll repeat though - I don’t know the device, and I don’t have one, so I’m only going on what I see in the logs, which requires a little bit of guesswork). I think this is reflected in what the video shows as well - you send a command on the switch, the UI is updating this so it updates immediately. The response comes back on the Relay channel and this is a little later due to delays in the ZWave network.
I’m not familiar with this device so can’t really be sure how it works. There shouldn’t be any difference from the binding perspective, but maybe the device uses these differently. From the binding perspective, they are similar functions - just using different endpoints.
As far as I can see, all commands to both devices respond quickly, and reliably, so I don’t see any issue other than possibly with how the device is configured, or the channels are being used.
The short answer is that ZWave devices can have multiple endpoints (so kind of logical devices), and they always have a root endpoint (for backward compatibility with devices from before multi channel endpoints were added.
A device will map endpoint functions into the root endpoint - ZWave doesn’t define how this is done. In this case, it appears that the switch in Endpoint0 (root) is mapped to the Relay in endpoint 3.
I would suggest not to use the switch at all - just use the relay channel. It should be exactly the same functionality (as far as I can see) but it avoids this strange cross mapping of commands and responses.
but if I click on the relais button (instead switch) inside the Basic UI then the light does also not turn on or off. It just keeps off.
This is really strange since this is a brand new device and the prevoius one (which I thought it was broken) has exactly the same behaviour.
The Z-Wave command reach the device but it does not turn on / off the light bulp.
If I move myself to the sensor the light switches on and inside HABmin I can see the switch-channel turning on as well, the relay-channel stays off. This way around it works.
But switching on/off from within HABmin or Basic UI it does not work - but only for this device. This is really strange to me.
Sure - I understand that’s what you’re reporting, but that’s a different question. As far as I can see from the logs (and as I’ve shown above) everything is working at the ZWave level. The device is reporting that it has changed state, and you see this in the video you showed.
I can really only point you at the device manual - maybe there is something there. I had a quick look, and it talks about things like twilight mode as being a reason for it not switching on - maybe it’s not configured correctly?
thanks for your patience.
I several time set the device (and also the previous one, which I thought it was broken) back to factory settings. But the result is always the same.
What I wonder is that today one time this node 3 worked, as you can read in one of my previous posts. But at the same time the node 4 did not work anymore and had the same issues. Then I removed power of both nodes and the behaviour swapped. Means Node 3 was not working anymore and node 4 was working again.
I am not a Z-Wave expert at all, but can it be that the devices block each other somehow?
. The log shows it’s working fine - the same as the earlier log you provided, but there is no activity with node 4. I’d suggest to create a log showing activity with both devices - or at least clearly state what the log is meant to show.
