Closed thopiekar closed 8 years ago
Are you using the UI for your configuration, or is it configured manually? I’m not sure what this error is but I’m not sure how it can happen if things are configured in the UI.
Yes, I used the Paper UI for that. Simply clicked on uninstall, waited and made a install again.
Is the bridge properly initialised?
No, all ZWave devices are "Uninitialised".
Ok, so I think this must be caused by the bridge being uninitialised. Any idea why that is?
No, sorry :disappointed:
Ok - I think you need to sort this out first then. If you have a log, then I’m happy to take a look, but if the controller isn’t working, then nothing else will so we need to fix that first.
In the mean time I unzip an 3-days-old offline zip and set up my controller. After a time it found all the devices again, but again the zwave binding broke with:
22:10:45.986 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:ea35ed86:node8' changed from OFFLINE to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): org.eclipse.smarthome.core.thing.internal.ThingImpl cannot be cast to org.eclipse.smarthome.core.thing.Bridge
online
.Log: openhab.txt
PS: Tried now alternatively with OpenJDK 8 and got the same. When running OpenHab (new installation) on my notebook only one thing where I sent a wake signal just got online (which I assume is correct).
As stated earlier, there is something wrong with your controller. The binding is not talking to it, and this is causing the errors. You need to rectify this first.
I never thought this might be the cause, but when I rename the thing "Z-Wave Serial Controller" into "Controller (Z-Wave)" it gets broken. I removed the controller, re-added it and it works again :smile:
Strange - ok, I’ll take a look at this…
If you rename it, and restart OH completely, is it still broken?
Yes, even after restarting it is still broken. I tried to set the default name to get it working, but it doesn't fix the problem.. Just readding that thing will make it work (at least for me).
This doesn't seem to be related to the ZWave binding - I can replicate this with other bindings - so it's either an issue with HABmin and the way it saves the thing information, or it's a problem with ESH. Given PaperUI doesn't seem to provide the ability to change the name of a thing, I can't test which at the moment but suspect it's an ESH issue.
Given PaperUI doesn't seem to provide the ability to change the name of a thing
- open the Paper UI
- use the nagivation menu to go to: Configuration, Things
- url should be http://.../ui/index.html#/configuration/things
- press on a displayed thing
- url should be http://.../ui/index.html#/configuration/things/**view**/...thingid...
- press on the pencil in the top of the page
- url should be http://.../ui/index.html#/configuration/things/**edit**/...thingid...
- there is a field where you can edit the name (the first editable line)
Thanks - not sure why I didn’t see what before…
Anyway, the error doesn’t seem to occur with PaperUI, so it looks related to the way HABmin saves the thing configuration. I’ll check the difference between the two….
So the difference is that HABmin is sending the full thing back to ESH, while PaperUI is only sending an object with the label, and an empty configuration. I guess the REST interface is doing something ‘bad’ with some of the other members.
I remember that we decided it is a good idea not to send the configuration if it is not changed (https://github.com/eclipse/smarthome/issues/1168#issue-140306478), but it surely should work and I would consider that as an bug if this is not working.
Absolutely - HABmin uses other config methods for setting most of the config, but it needs to use this API to set the label, and some other stuff (channel config I think). I don’t null everything else out - I don’t mind doing it but I really think that ESH shouldn’t kill the thing if this API is used...
I have experienced this bug as well in both HABmin and PaperUI both, FWIW. I'm running OpenHAB from a 2.x snapshot that I grabbed within the last week or two at the most. In fact, the only reason I installed HABmin was to try and get around this problem in PaperUI until I stumbled across this bug.
Is there some way to fix my Z-Wave devices manually without having to reconnect them?
You need to delete the thing and add it back, but you don't need to exclude and re-include the device into the network. So, delete the thing, hit the discovery button and it will immediately be found again (don't do anything to the node) and then add the thing back. It should pick up all the previous channels and items with any luck.
Thanks @cdjackson, that did the trick.
While trying to get my door/window sensors working, I made a reinstall again for researches in #850.
I'm not sure whether it is related to https://github.com/openhab/openhab2-addons/commit/3998733edd34ea3380fd82800e338feda1a4b765, so I made a new issue here.