The XML files not being written indicates that the startup phase is not completing.
You should take a look through the log to see what’s going on - does the log show that initialisation is completed? If not, what does it show?
Looking at the code, node-1 will not normally save the XML file. The controller jumps over the save during initialisation, so I don’t think that’s an issue…
Chris
Can you enable DEBUG logging and then post the log. It’s difficult to see what’s happening with the very limited log.
One other point to note is that the SP814 is a battery device, so depending on the wakeup configuration, it won’t respond very often. I think the default is 10 minutes, but it could be a lot longer (I have mine set to 1 hour!).
On the back of the unit you will find a little switch - if you press this 3 times after starting the binding it will wake the device up and it would be useful to see if that helps communications.
Looking at your zwave.log file, there’s certainly something wrong somewhere here (but you knew that :) ). There’s some weird stuff happening on startup and initialisation doesn’t seem to complete - but clearly from your SP814-kicked log, the initialisation does ultimately complete, so I guess this isn’t a major issue…
One question on your controller - it looks like the vision security stick - is it new? I just note that the API version reported by the controller is a much older version than the Aeon Labs one I have - it’s presumably not an issue, but just something I’ve noticed.
Looking at the sp814 log, this all looks fine for the SP814 initialisation. Have you configured an association at all? If not, you should use HABmin, go to the Devices tab, select the SP814, node 2, then select Association Groups, click on Reports, and change Node 1 to Member. Then click the little button on the SP814 3 times an hopefully this will be set. Without this, the device won’t send any movement alarms to openHAB.
Can I suggest that you change the binding to use the one on the HABmin site (https://github.com/cdjackson/HABmin/blob/master/addons/org.openhab.binding.zwave-1.5.0-SNAPSHOT.jar). There are a few reasons for this - firstly, it has some code to try and resynchronise the stick when the binding starts. This has helped out another user who had problems with the binding started (although not the same problem you have). Also, it will help me with debug as I can then compare your logs to my current binding…
Also, when working with battery devices updating associations and configuration can be confusing as the values can change - yesterday I implemented a “pending” indicator in HABmin to show that a value was queued for battery devices and it now shows it in yellow - this will only work correctly with the latest binding, and the latest HABmin files - older files will still allow you to set the configuration, but the values might flick around in the display (I hope that makes sense!).
Chris
now I'm trying to make AEON Labs Multisensor 4 in 1 work. I get so far the Node3.xml, openHAB seems to manage it somehow without explicitly associating with AEON Labs. At initialization stage I got values for Temperature, Humidity, Luminescence and Battery. Also, if I click the sesor's button, I get the Node Frame with all mentioned values. But, there are no incoming events on manually triggered movement. Not at all!
I tried to make an association like you have recommended me relating to the SP814. The problem is, I don't see, if it worked, because the HABmin backend resets the value "Member" to "Non-Member" every time back again (it was also the case with SP814, however, the association is definitely done for that sensor, cause I get movement trigger and battery).
Another question: Afaik on such a wake-up I should get also all values from all its sensors and battery. Is it the case for all battery sensors?
now I'm trying to make AEON Labs Multisensor 4 in 1 work. I get so far the Node3.xml, openHAB seems to manage it somehow without explicitly associating with AEON Labs. At initialization stage I got values for Temperature, Humidity, Luminescence and Battery. Also, if I click the sesor's button, I get the Node Frame with all mentioned values. But, there are no incoming events on manually triggered movement. Not at all!Strange - looking at the manual, it seems that both the sensor data and the motion notifications are all sent to association group 1.However, I see that there's a parameter called 'Motion Sensor' which can disable the motion sensor - you should make sure this is enabled.
There may also be an error in the 4in1ms.xml file since I see configuration parameters for association groups 1 to 3, but only group 1 is listed. The manual I've found online doesn't mention the number of association groups or what they are for - I'll try and find a better manual and update this if I can...
I tried to make an association like you have recommended me relating to the SP814. The problem is, I don't see, if it worked, because the HABmin backend resets the value "Member" to "Non-Member" every time back again (it was also the case with SP814, however, the association is definitely done for that sensor, cause I get movement trigger and battery).I would recommend upgrading to the latest HABmin files - not just the JAR file, but also the files in the webapps/habmin directory. If you've done this, you might need to refresh the cache. The latest version (as from last weekend) handles battery devices better - by this I mean that it displays data in a 'pending' state while it's still waiting for the device to respond. This stops the change from member to non-member, and highlights the change parameter in yellow while it's waiting for the device to respond.With the version you have, as you've found, the association will still work - it's just that in the GUI it wasn't really displayed well and it was confusing...Note that the release version on github doesn't have this, but I might make a new release tonight as I think the old one will stop working on recent OH snapshots as a library used by HABmin has been changed...
However, I see that there's a parameter called 'Motion Sensor' which can disable the motion sensor - you should make sure this is enabled.Sorry, I'm pretty new to this all stuff.. How do I know this parameter value? The habMIN doesn't show it.. And how can I trigger with OH such a config call, setting this param to "1"?
There may also be an error in the 4in1ms.xml file since I see configuration parameters for association groups 1 to 3, but only group 1 is listed. The manual I've found online doesn't mention the number of association groups or what they are for - I'll try and find a better manual and update this if I can...And which role plays this xml exactly?
Great! By the way: Like I anderstand, the zwave binding comes from you, so the one you offer (1.5.0) it is the newest one. So upgrading now to OH 1.5.0 is not of essence to me.
However, I see that there's a parameter called 'Motion Sensor' which can disable the motion sensor - you should make sure this is enabled.Sorry, I'm pretty new to this all stuff.. How do I know this parameter value? The habMIN doesn't show it.. And how can I trigger with OH such a config call, setting this param to "1"?HABmin can show this. In the device list, select the device you want to configure, select 'Configuration Parameters', and click on the Refresh button. This will queue a request to get this informaiton from the device - it will hopefully be downloaded next time the device wakes up.That will allow you to view the value - you can then change it in the same way as the Association Groups (just change the value and it will again be set next time the device wakes).
There may also be an error in the 4in1ms.xml file since I see configuration parameters for association groups 1 to 3, but only group 1 is listed. The manual I've found online doesn't mention the number of association groups or what they are for - I'll try and find a better manual and update this if I can...And which role plays this xml exactly?
Great! By the way: Like I anderstand, the zwave binding comes from you, so the one you offer (1.5.0) it is the newest one. So upgrading now to OH 1.5.0 is not of essence to me.
I’m not sure what’s causing this. Unfortunately there’s no indication that I can see that says where the error is actually caused but I’m not sure that it’s caused by HABmin - there are a lot of error messages about Atmosphere and Filters and these are not used by HABmin.
So, this _might_ be a problem somewhere else - what other UIs are you running?
> Regarding 4in1: it gives reaction on movement (not as Command Class SENSOR_BINARY, but as BASIC). How can it be? And secondly, I was running OH whole night, and did not get any data from 4in1. So the reports are not coming.. But, if I click the z-wave button once, I get sometimes battery, sometimes humidity, sometimes luminance (never temperature!).
What is the Wakeup Command class time set to? - this should be displayed in HABmin once the device finishes its initialisation.
Looking at the manual, in order to send the wakeup notification you need to “hold” the button on the 4in1 - I don’t know for how long - I guess a few seconds, or maybe until it beeps. I think in the past we’ve been talking about pressing the button 3 times (which is correct for other sensors like the Everspring). For the 4in1, pressing the button 3 times wakes it up for 10 minutes, but I don’t think this will help since the binding will still tell it to go back to sleep when it’s sent all data. You should use the “Button Held” option.
I would concentrate on getting the device past the initialisation phase (green dot in HABmin) and reading the configuration parameters and wakeup command class information. Once you have that, we can see how the device is configured and we’ll be able to make better decisions about what’s happening….
Yes - please post this log. Hopefully it will help narrow this down - especially if it happens every time.
What hardware are you running OH on?
Chris
Unfortuntely I don’t know what this log is from :( It looks like the one you had the other day but it’s got no reference to any binding specific code so I don’t know how it’s possible to work out where it’s from :(
> And while I'm trying to update config, I get also "Error sending action to the server" together with the log errors like "Malformed domain request in getConfiguration 'nodes/node3/parameters/configuration111'" :-(
The domain request error I think might be an issue with the GUI. I’ve seen this before so will take a look tonight.
The error sending action to server is possibly related to the issue with seeing the “HABmin connected / unconnected” errors. My guess is that even though HABmin only sends information to openHAB every few seconds, and these are only small PING type packets, that this might be overloading the PI :(
I’ve just pushed some changes to HABmin to increase the times - let me know if that helps.
The domain request error I think should be fixed now.
First of all: cool, it works. Indeed, I get no more openHAB is offline messages, and the boring exception is away!
However, there are some further issues with configuring devices (or at least the 4in1). Thus, I tried to push 60 sec time interval for reports sending to group 1 (param. 111). Somehow strange, that I get it now instead every 4 minutes = 240 sec (previously I got every 720 sec - default setting). And in the HABmin view it is still 720, even after clicking the button "refresh" and waiting for wakeUp cycle or klicking the zwave-button of the 4in1.
The next issue is, if I just open the configuration of 4in1 to look at values (also after openHAB full restart), I get following exception every 5 seconds (all 6 messages together):
However, there are some further issues with configuring devices (or at least the 4in1). Thus, I tried to push 60 sec time interval for reports sending to group 1 (param. 111). Somehow strange, that I get it now instead every 4 minutes = 240 sec (previously I got every 720 sec - default setting). And in the HABmin view it is still 720, even after clicking the button "refresh" and waiting for wakeUp cycle or klicking the zwave-button of the 4in1.I can't comment too much about the device since I don't have one, however, I can comment on the HABmin side... If you change the Parm 111 time in HABmin, HABmin should highlight the new time in yellow (meaning that it knows you've changed it, but it's not been acknowledged by the device). Once this yellow background goes away, it means that the response has been received, and at that time, I think the value displayed in HABmin should be updated with the latest data from the device. It should display the value that has just been sent by the device. I'm happy to look at a logfile if you want to send one during this procedure (ie change the value in HABmin, then wake up the device and send me the log). Also, after this the XML file in the /etc/zwave folder should be updated - it would be interesting to send me that as well... I can then see if HABmin is working correctly and showing the value that's reported by the device.
The next issue is, if I just open the configuration of 4in1 to look at values (also after openHAB full restart), I get following exception every 5 seconds (all 6 messages together):Hmmm - don't worry about this - it's not a problem. However, I thought I'd removed this message so maybe you have a slightly older version of the JAR file? (or maybe I haven't removed it!). This was something I added for debugging the device XML files and isn't a problem.
The 4in1 one sends the motion data and the other data every 240 secs (don't understand why, HABmin shows still 720). It is also green in HABmin. I changed 2 values: param 111 to 120 and wake-up interval to 60. But, the values stay forever yellow. Than at 13:37 I held some seconds the zwave button of 4in1. Results:
1) zwave-logfile (attached): at 13:37 controller gets wakeup from 4in1.
13:37:04.520 NODE 3: Wake up interval report, value = 240 seconds, targetNodeId = 1
Why is this the wake-up 240? I cannot remember I set it anytime (except now, but it was 60!). And what's about param 111?
The minimum Wake Up interval time is 4 minutes (240 seconds) rounded up. Thus if the interval time is set to 1 minute, then Wake Up Notifications will be send every 4 minutes. Likewise if the interval time is set to 7 minutes, Wake Up Notifications will be send at 8 minute intervals. Default is 0.
2) At the very moment the famous error is to see in the output:
13:37:07.905 INFO runtime.busevents[:26] - Aeon_Labs_4_in_1_Lumin state updated to 153
Exception in thread "Thread-38" java.lang.ArrayIndexOutOfBoundsException: 9
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveCommandClass.extractValue(ZWaveCommandClass.java:235)
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSensorCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSensorCommandClass.java:145)
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:79)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:166)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:146)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:140)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveReceiveThread.processIncomingMessage(ZWaveController.java:858)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveReceiveThread.run(ZWaveController.java:914)
3) The situation in HABmin:
param 111 is still yellow with value 120
wakeup period is NOW 240 (formerly 0) INSTEAD OF 60
I got the version from branch "actions" where you have increased the times. So I don't know if it can be too old. :-/
2) At the very moment the famous error is to see in the output:
13:37:07.905 INFO runtime.busevents[:26] - Aeon_Labs_4_in_1_Lumin state updated to 153
Exception in thread "Thread-38" java.lang.ArrayIndexOutOfBoundsException: 9
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveCommandClass.extractValue(ZWaveCommandClass.java:235)
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveMultiLevelSensorCommandClass.handleApplicationCommandRequest(ZWaveMultiLevelSensorCommandClass.java:145)
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:79)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:166)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:146)
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:140)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveReceiveThread.processIncomingMessage(ZWaveController.java:858)
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveReceiveThread.run(ZWaveController.java:914)
09.04.2014 | 22:46:52 0 | 3:59:0 | Aeon_Labs_4_in_1_BTR | 82 | |
09.04.2014 | 22:46:52 0 | Aeon_Labs_4_in_1_BTR | 82 | ||
09.04.2014 | 22:46:52 0 | Aeon_Labs_4_in_1_Lumin | 5 | ||
09.04.2014 | 22:46:52 0 | Aeon_Labs_4_in_1_Lumin | 5 | ||
09.04.2014 | 22:46:52 0 | Aeon_Labs_4_in_1_Humid | 55 | ||
09.04.2014 | 22:46:52 0 | Aeon_Labs_4_in_1_Humid | 55 | ||
09.04.2014 | 22:46:53 0 | 1:0 | Aeon_Labs_4_in_1_Temp | 20.6 | |
09.04.2014 | 22:50:52 0 | 3:59:0 | Aeon_Labs_4_in_1_BTR | 82 | |
09.04.2014 | 22:50:52 0 | Aeon_Labs_4_in_1_BTR | 82 | ||
09.04.2014 | 22:50:52 0 | Aeon_Labs_4_in_1_Lumin | 6 | ||
09.04.2014 | 22:50:52 0 | Aeon_Labs_4_in_1_Lumin | 6 | ||
09.04.2014 | 22:50:52 0 | Aeon_Labs_4_in_1_Humid | 55 | ||
09.04.2014 | 22:50:52 0 | Aeon_Labs_4_in_1_Humid | 55 | ||
09.04.2014 | 22:50:53 0 | 1:0 | Aeon_Labs_4_in_1_Temp | 20.7 | |
09.04.2014 | 22:54:52 0 | 3:59:0 | Aeon_Labs_4_in_1_BTR | 82 | |
09.04.2014 | 22:54:52 0 | Aeon_Labs_4_in_1_BTR | 82 | ||
09.04.2014 | 22:54:53 0 | 1:0 | Aeon_Labs_4_in_1_Lumin | 7 | |
09.04.2014 | 22:54:53 0 | Aeon_Labs_4_in_1_Lumin | 7 | ||
09.04.2014 | 22:58:52 0 | 3:59:0 | Aeon_Labs_4_in_1_BTR | 82 | |
09.04.2014 | 22:58:52 0 | Aeon_Labs_4_in_1_BTR | 82 | ||
09.04.2014 | 22:58:53 0 | 1:0 | Aeon_Labs_4_in_1_Lumin | 5 | |
09.04.2014 | 22:58:53 0 | Aeon_Labs_4_in_1_Lumin | 5 |
I got the version from branch "actions" where you have increased the times. So I don't know if it can be too old. :-/Hmm - I haven't touched the actions branch since December and I suspect the version you have is much more recent that that... You should just get it from the master branch anyway...
Sorry for confusion - I used the rules branch. But now I'm updating to the master branch.
> FIrst of all good news: the param 111 has now value 120 and is not yellow anymore! Maybe it needed some more time.. As I now understand, it has no sense to set it under the wakeup value, so value 240 would be a logical minimum also for param 111. Please correct me if I'm wrong.
I’m not really sure how the device works - the wakeup and the association times may be independent. However, you will very likely deplete your battery quite quick if you have the times set this short...
> But it results in restart of the zwave binding, so it would be great if you can catch the error to avoid restart or something like that (as you mentioned).
I’ll upload a new version in a few minutes - hopefully it will stop the problem.
> I hope it's ok if I ask in this thread about ever new problems?
Sure…
> I'm testing now Fibaro Dimmer fgd 211. Somehow HABmin dont recognise it - no name, firma, parameters. But I can dim it down (it works very poor now, so I want to configure it).
> What could be wrong / what could I do? Node4.xml you can find attached.
The problem will likely be that Fibaro use a lot of different Type/Id pairs for their devices. The database needs to know these to link the device correctly. I’ll take a look at this tomorrow, but it should be easy to add.
> I'm testing now Fibaro Dimmer fgd 211. Somehow HABmin dont recognise it - no name, firma, parameters. But I can dim it down (it works very poor now, so I want to configure it).
> What could be wrong / what could I do? Node4.xml you can find attached.
The problem will likely be that Fibaro use a lot of different Type/Id pairs for their devices. The database needs to know these to link the device correctly. I’ll take a look at this tomorrow, but it should be easy to add.
Thanks. I could also look into the logs and try to see the ids to correct the fibaro-xml.
I've just got a look into products.xml and saw, that fgd211 is assosiated with ids 0104, 0106, 0107, 0109, 100A and 300A. In this database it has 0103. Maybe it should be added there? Can I get my device id without debugging?
> But the problem is, the Type and ID are in HABmin and in the xml both 0!!
Strange. I would delete the XML files and restart the binding to see if this helps. The manufacturer information is data that is only read from the device if the XML file doesn’t exist, so this will force the binding to update it…
I just deleted Node4.xml and it helped!! Great!
Are you saying USB Power is better than battery as far as connectivity goes? Or worse?
Is there a Send_Command I can do to disable the motion sensor? I would like to only enable it when I "ARM" the security system.
Also I am not sure if that CT30 products I gave you is OK because1. There is no Product sub node2. THe Node Name is Radi Thermostat Company of America [ID:1e,Type:1], no mention of CT303. There is no Configuration Parameters element