Hi there,
I’m trying to get my sensative AB strips guard 700 Model 1101021 running with the lates OH-Version.
I’ve added the Z-Wave USB-Stick to the raspberry and have installed the z-Wave binding.
I’m also able to scan and assign the device… But it doesen’t matter how long the device runs it shows always as unknown device.
As I can see in the docu from the “open smart house” the Version 1101021 should be added at least by OH version 3.2.
I’ve installed the latest version from OH at V3.3.0… As my meaning is that the version should be included?!?
May I ask you to help me please with this matter #OH beginner #raspberrypi4 beginner
On the UI page for the device, properties drop down, what are the device ID and Type. Both should be “4”. If not what are they?
Also on the UI page for the device at the bottom, are there five lines? If not use the magnet to try to wake the device. These devices can be tough to fully include
Hm… tried a few times the wake up move - still 12 properties available. zstick is in front of me.
No I can’t find the Z-Wave node 1 entry. I just can see it under the thing type info.
Thats all I can see at the UI:
That is not a normal reaction Actually I was hoping for a quick one.
So now more information gathering
What kind of zstick? Does it have a button?
How did you install OH? Are you using openhabian?
What does the controller UI page look like (mark advanced tab before making picture)?
Read the Zwave documentation, especially at the bottom where it says “when things do not go as planned” Set the binding to Debug, try 2 or three wakes, then set the binding back to info. Post the log (using the brackets).
Console means-get to command line of your pi–type sudo openhab-cli console; first password is your login, second is habopen
Read the Zwave documentation, especially at the bottom where it says “when things do not go as planned” Set the binding to Debug, try 2 or three wakes, then set the binding back to info. Post the log (using the brackets).
hm… there is not a lot of traffic I guess: along this post Z-Wave Debugging in openHAB
Blockquote
2022-11-27 16:01:33.438 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:01:33.441 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2022-11-27 16:01:45.952 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:01:45.955 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:01:45.958 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2022-11-27 16:01:53.905 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:01:53.908 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:01:53.910 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2022-11-27 16:01:53.919 [INFO ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Maximum Awake time period reached, state VERSION count 20, messages 1
2022-11-27 16:02:46.760 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:02:46.763 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2022-11-27 16:02:59.273 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:02:59.276 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2022-11-27 16:02:59.278 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2022-11-27 16:03:07.241 [INFO ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Maximum Awake time period reached, state VERSION count 20, messages 0
Console means-get to command line of your pi–type sudo openhab-cli console; first password is your login, second is habopen
Here’s the problem. The binding does not support “7” level Zsticks. “7” level devices are fine, just not the zstick. For the RPI4 you will need a “5” level Aeotec that is marked a “compatible” with Rpi4 (early Aeotec versions were not) OR some other brand of Zstick.
You can search the forum for 700 level Zwave for more information.
Alright… Thank you very much for your time and support!!
That would have given me a headache for a long time to comet I spend a lot of time to troubleshot without a solution. At the end it was that easy
Thanks man and have a great weekend. From what is left.
Phil
Are you sure that Z-Stick 7 isn’t supported? Sure, the binding doesn’t support Z/IP, but doesn’t the Z-Stick 7 support a backward compatibility mode? IIRC, for backward compatibility the latest firmware is required:
… so it would be helpful to know which Z-Stick 7 firmware the OP is using.
I’m just going on what has been discussed in the forum. Maybe there is a backward compatibility firmware option. That sounds good as it would mean new hardware would not have to be purchased by OP.
Another indirect indication that this is a 700 issue is from two observations. One is the presence in the log above of this line
Hi openhabgs!
thanks for this post. Well I must say I’ve now bought a Z-Stick Gen5 update to Gen5+ and now my sensors are working as a charm
The wakeup move is also working well.
As I’ve not found a solution for my requierement no other option are available.
There were some improvement in zwave battery device initialization in OH3.3. I have some of these devices. Before was as described in earlier post; After no problem