Hello
I’m using the development version of the z-wave binding. thanks, it’s great what you do.
With the development version of the 24-04-2018 all works fine. I have now updated to
the version of 26-06-2018. With this newest version, i don’t see any z-wave things in
habmin. (newest version downloaded with the link on 1st entry in this topic)
What i have to do to make the new version work again?
Thanks, @sihui, you made my day! When “going back to the future” (hence, removing 2.4 and using the newer 2.3 dev branch) all my problems with the former working and currently non-working things went away and I am back on track with my installation.
@mhilbush please try this version. This adds support for alarm_entry and also tries to resolve the issue with initialising battery devices that you are having.
For the alarm_entry - I just aggregate all the different alarms into one - so MANUAL, AUTO, KEYPAD etc are all used to show the lock state. I think this is fine - if we need to spit this at some stage to provide more detail, then we can look at that later…
but how do I know if it is stable, snapshot or whatever else?
Yes, that’s the one in addons folder. It is installed but not active, so it’s not working.
It seems to work:
19 │ Active │ 80 │ 3.12.0.OH │ nrjavaserial
and yet I receive that error:
openhab> bundle:start 277
Error executing command: Error executing command on bundles:
Error starting bundle 277: Could not resolve module: org.openhab.binding.zwave [277]
Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:="optional"
Unresolved requirement: Import-Package: org.eclipse.smarthome.config.discovery.usbserial
(I reinstalled so the number changed from 272 to 277).
The zwave binding I had running was installed in habmin, so I went to karaf and uninstalled zwave from there (bundle:uninstall xxx). Then I dropped new binding in the addons folder (to keep the dependencies, as proposed by @chris). It reported installed (but not active) and starting failed with errors as above. I “chown”-ed the binding to openhab:openhab btw, should I not?
Has anybody seen those errors before? Is my only hope to reinstall openhab?
What are those “jdt.annotation” and “smarthome.config.discovery.usbserial” anyway?
Sidenote:
All I want is to get the Fibaro Dimmer2 and Qubino Flush Dimmer to report their state. It’s only possible in development binding, isn’t it? (Associations seem not to work well as well ATM, but that’s sth I can live with, or without to be strict.)
That is a pretty old snapshot version. Current snapshot is #1307.
You should at least upgrade to openHAB 2.3 stable.
The proper way to do that is:
uninstall the binding the way you did install it. So if you did install it via GUI, uninstall it via GUI.
If it does not work uninstall it via karaf.
If it is still not gone (check via bundle:list), clear cache and tmp.
After you got rid of the binding drop the jar into the addons folder. It should be active automatically.
If the transport serial is missing install it.
If you are finished restart openHAB. It will take a while because you cleared tmp and Cache …
I think that once this issue with the wakeup is resolved, I will merge this new DEAD NODE code into the main dev branch, and if there’s no major complaints merge dev into master in a week or two. @5iver I’m not really sure where we are with your issues?
Yep - my initial change was ok, but it was caught by this one . I will remove this check - it should be safe as it should only get this far if it is a battery device (as there’s a listening check above). There may be some corner cases though where devices don’t listen, but also don’t support the wakeup class (I know there are one or two that strangely do this!).
Edit: Let’s see what you see with this - there might be another error I think (for sure you will have another similar error, and maybe even an exception for good luck!). I’m rushing as I’m about to go out - I really need to spend a bit more time on it either late tonight or tomorrow…
Here’s what I’ve found so far. Results are mostly good.
Aeon Wallmote - discovered correctly and is working correctly
Fibaro Button - discovered correctly and is working correctly
Ecolink TILTZWAVE2 - discovered correctly and is working correctly
Minimotes - I have 3 devices with mixed results (I’m really starting to hate these devices )
– one was discovered correctly, and is working correctly
– one was discovered correctly, but is complaining about the COMMAND_CLASS_SCENE_ACTIVATION not found when I press a scene button. This one and the one above both report the same firmware version (1.19). There is no node.xml for this one either. I also tried to exclude/reset/include the node. I’m not sure what to make of this at this point.
We’d need to look earlier in the initialisation to see what’s up. It’s not completed initialisation yet, although it should have received the NIF so should know the supported classes already. This will be why it’s not saved the XML - it’s not finished the static initialisation (ie still at SET_WAKEUP).
I just restarted OH, so I’m going to wait a while for the zwave network traffic to settle down. Then I’ll do a delete/rediscover test on the 2 problematic Minimotes, nodes 95 and 96.
I’m having trouble securely pairing a Schlage BE469. I tried a while ago with one that was already installed, but put it off until I got my second one so I could have it on my desk rather than on a door while debugging.
I’m trying a version posted for mhilbush yesterday
196 │ Active │ 80 │ 2.3.0.201806301554 │ ZWave Binding
I start the secure inclusion using openhab, and then start the inclusion on the lock itself. The lock shows an X to indicate inclusion failure. I did end up with a new node (NODE 27 in the logs below), but it’s not securely included, and in habmin, it’s just listed as “Unknown Device” with no Manufacturer, Type/ID etc (although it does show Neighbors and SPECIFIC_TYPE_SECURE_KEYPAD_DOOR_LOCK)
Here’s a log from the first inclusion (which was my first inclusion event since my upgrade from 2.2 to 2.3, so there is a lot of messaging. I had TRACE turned on when I was trying to debug my first lock):
Here’s a subsequent inclusion attempt:
Note that the lock itself thinks it’s not included, according to an on-lock procedure