Z-Wave Shutting Down -- OH2 B1 #111
Comments
|
Haven't seen this before. Can you provide a debug log please. Sent from my iPhone
|
|
Sure. That used to get added to logback.xml, right? Where should I enable that now with OH2? |
|
Same place but the files in a different location. From memory it's now in the runtime/etc folder or something similar... Otherwise the file format etc is the same as in the Zwave wiki Sent from my iPhone
|
|
Ok. There isn't a logback.xml in the OH2 tree. I've copied the one from the OH1 install to the /opt/openhab/userdata/etc folder. Doesn't appear to be picking anything up though. |
|
The default logging now uses pax it seems. The config file is called org.ops4j.pax.logging.cfg and located in runtime/karaf/etc. Existing addons that use logback would still log I would think, just need to figure out where to put the config xml file so it picks it up ? |
|
Thanks. Flipped a couple "INFO"s to "DEBUG"s and it appears to spit out a bunch more. Attached are the two logs. |
|
I changed the default level to DEBUG in mine through the karaf console (log:set DEBUG). It should have the same effect as jiggering the config file with non-permanent results. When I did this, I noticed it changed the log level only for the karaf runtime, which makes sense I guess. We need to figure out how to pass DEBUG to the z-wave addon instead... Reading... I am having the same issue when trying z-wave with 2.0 b1, adding it with the PaperUI interface. |
|
Ok - it used to be there but everything changed with the introduction of karaf this week. I'll need to try and work out what's up :( Sent from my iPhone
|
|
This should now be working again. @carpenike where did you change the log level to get the debug logs? |
|
Changed it in the file xsnrg mentioned above. I don't think it actually increased the logging from the bindings though. |
|
Kai has enlightened me -:
https://community.openhab.org/t/logging-under-oh2-karafa
:)
|
|
Wow that log filtering is awesome. Still not working for me. |
|
Agreed - it’s still not fixed... |
|
Ah sorry. Just saw your comment above that it should be working again. #111 (comment) Also, does the issue also exist with your ZWave v2.0 source tree? |
|
I’m not sure as I’ve not had the chance to run the v2 binding since Karaf was introduced…
|
|
OK. Is the source for v2 located here? https://github.com/cdjackson/openhab2.git if so mvn clean install has some errors that I can post on another thread if it's helpful. |
|
Feel free - once I get this OH1 issue resolved I’ll look at v2 again… If you fancy fixing anything, then feel free to create a PR into my repo...
|
|
Potential fix for the OH1 zwave issue is here -: openhab/openhab1-addons#3837 |
|
Pulled the latest this morning from cloudbees and things are looking better. Getting this error at the start but at least it's polling my devices: Also having issues with the devices themselves but this is may not be related. Do you know why I have this node 255 showing up? I only have 2 devices on my ZWave network at the moment. They were more stable / showed properly in HABMin on OH 1.8 as well. |
|
The error is the one that we see that caused the whole problem associated with startup - the binding should restart the COM port connection now (which it did) but it's interesting that the issue might still occur occasionally (FYI @kaikreuzer - I might update the other services to also start immediately to see if this helps, but I'm still unclear why there's this semaphore interrupt issue).
Yes - this is the controller :) |
|
Ahh makes sense. :) Was that Node 0 in OH1? |
|
No - it's always been node 255 (and this binding is still the OH1 binding - you're just running under OH2, but it's the same). The controller though has a dual personality in that it also has another ID (normally node 1). This is the controllers node for communicating with other devices, and node 255 is the node used for commands sent from OH... Node 0 doesn't exist. |
|
Gotcha. That's what I remember seeing -- 1 in HABmin. Thanks again for the help. No pressure -- Is HABmin2 ready for testing yet on OH2/Karaf? |
|
Yes - I think HABmin2 should work ok under Karaf - I did a quick test the other night so I think it’s now ok…
|
|
Sounds good. I'll give it a try. Still require HABmin1 to be installed? |
|
HABmin 1 won’t work on OH2 due to the way the web side it handled…
|
|
Right. There just used to be a requirement to have the HABmin1 jar file installed on the OH2 system in order to get HABmin2 to load wasn’t there? From: Chris Jackson [mailto:notifications@github.com] HABmin 1 won’t work on OH2 due to the way the web side it handled…
— |
No - there was (IS with the current version) the requirement to have the OH1 ZWAVE binding installed - not the OH1 HABmin binding... |
|
Got it – thanks. From: Chris Jackson [mailto:notifications@github.com]
No - there was (IS with the current version) the requirement to have the OH1 ZWAVE binding installed - not the OH1 HABmin binding... — |
|
The ZWave startup issue under OH2 is now resolved... |
Hey All,
I'm not sure if this is the right place to ask a question about the Z-Wave binding itself, if not please re-direct me to where I should ask!
It appears that the 1.9 Z-Wave binding installed via the PaperUI console does not stay running on my fresh install. It configures, log shows that it comes up fine, but then it immediately shuts down.
Is this a known issue?
The text was updated successfully, but these errors were encountered: