Hello, I’ve been trying to get my Aeotec Muti-Sensor 4 working without success. When open OpenHab, the value for temperature is blank, so I am not sure if my setup is incorrect or maybe it was unable to find the device to bind? What do I look for to confirm that binding was successful in the log?
Here’s an example of what I see when I search z-wave:
2015-10-14 19:31:29.733 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, port = COM4
2015-10-14 19:31:29.733 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, healtime = 2
2015-10-14 19:31:29.733 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started
2015-10-14 19:31:29.733 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
2015-10-14 19:31:29.733 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2015-10-14 19:31:29.733 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port COM4
Highly recommend you set up a separate zwave.log in your logback.xml (or logback_debug.xml) to run at DEBUG level. That will tell you what your controller sees at which z-node and ports within it (if needed).
My zwave log is showing the below. What does the last line mean? Does it mean it cannot find my controller or there is no device paired to my controller? As a quick background, I am using windows 7 and already installed in AEOTEC stick driver and it is associated to COM4 and pretty sure I paired it correctly already.
2015-10-15 09:10:35.237 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding started. Version 1.7.1
2015-10-15 09:10:35.267 DEBUG o.o.b.z.i.ZWaveActiveBinding[:175]- ConverterHandler not initialised. Polling disabled.
2015-10-15 09:10:35.363 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding started. Version 1.8.0.201508211938
2015-10-15 09:10:35.386 DEBUG o.o.b.z.i.ZWaveActiveBinding[:175]- ConverterHandler not initialised. Polling disabled.
Which version of zwave and openHAB are you using?
Looks like your zwave binding jar is not good. I say this because in the past when i eported the plugin from source, I forgot to check “use classe files from project” and the ant task failed with compiling ConverterHandler class. As such some class files were not exported in the jar and i go the same error as yours.
You have two different z-wave binding jars in that log…a 1.7.1 and a 1.8.0.z pointbuild. Check your openhab/addons directory and get rid of one of those jars.
Thanks! I got rid of the 1.8.0.z that I copied over when I installed in hadmin.
Now there is alot more lines in the log. The last line reading “No nodes to ping”. Does this mean that maybe I don’t have my Aeon multi-sensor 4 paired correctly to my Aeon Labs USB Z-Stick?
Now it appears that binding worked. Node 2 is showing my multi-sensor in habmin, but when I open my app to view the sensor details, it is not showing me the temp still but seems like battery is working fine. I had followed this thread to setup the item parameters. Please note I already tried deleting zwave.xml to solve the get request error per another post I read but that didn’t help in my case.
Yes, I believe so. Here’s what I have in item and sitemap-
From .ITEM
Number Multi1_temp “office - Multi Temperature [%.1f °F]” (multi,multiGraph) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=1”}
Number Multi1_humidity “office - Multi Humidity [%.0f %%]” (multi,multiGraph) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=5”}
Number Multi1_luminance “office - Multi Luminance [%.0f Lux]” (multi) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=3”}
Contact Multi1_motion “office - Multi motion [MAP(motion.map):%s]” (multi,motion) {zwave=“2:command=SENSOR_BINARY,respond_to_basic=true”}
Number Multi1_battery “office - Multi battery [%d %%]” (multi,battery) {zwave=“2:command=BATTERY”}
From Sitemap
Frame label=“My First Sensor” {
Text item=Multi1_humidity
Text item=Multi1_temp
Text item=ulti1_luminance
Text item=Multi1_motion
Text item=Multi1_battery
}
Yes, but have you configured the device itself? You need to set the device configuration correctly or it won’t send the temperature etc. Has this been done?
From memory it’s parameters around 100 to 102, but you should check the manual.
yes, I’ve set it to the following based on other people’s setup for this sensor. See below. Double-checking the manual, it also said to associate to group one… which I assume is 101.
101: Which reports to send automatically in timing to group 1: 225
102: group 2: 0
103: group 3: 0
111: Interval to send out reports to group 1: 240 (also personal preference for testing battery life)
112: Interval to send out reports to group 2: 720
113: Interval to send out reports to group 3: 720
Everything looks fine with the config and there’s nothing strange in the log I think.
The configuration should mean that the device sends the data every 12 minutes - the log is only for 7 minutes. I guess you’ve waited longer to see what is received, but at the moment, there are no messages being received from the device yet…
Hmm, configuration for group 1 was 240 and I thought that was for every 4 mins. How did you determine 12 mins? I didn’t think the values in group 2 and 3 matters for me right now… or does it?
As for log, Looking at the zlog file, it seems that it has been loggin data over 1 hr… How did you determine it was 3 minutes? I also attached the entire log here. I had to cut off part of the log when I pasted earlier due to post size limitation.log.pdf (162.0 KB)
I’m not sure then - everything appears ok. One thing you can try is to delete the XML file, and restart the binding. Wake the device up and hopefully it will recreate the XML. What this does is to download all the configuration from the device - it just makes sure that what we are looking at in the XML file is really consistent with what’s in the device - just in case we’re fooling ourselves and the device is actually configured differently (??).
I deleted node2.XML but do not know how to restart binding. How do you manually restart binding?
For now, restarted hab server but experiencing the same issue after the xml file got created. One thing to note is that every time I start hab, I have to click on the button on my device for it to show up on Node 2 in habmin. Could this somehow be contributing to the issue I am experiencing? I figure I would try to resolve issue later after I get the sensor working correctly.
Unenroll the device and enroll it again. The log states that Sensor multilevel is not supported by the device. Maybe it’s gone bad. Try updating the firmware on it.
What do you mean by enroll? When I start the runtime server, the device is showing grey on startup. I have to put the button on my device to change it to ‘green’. Is that what you meant by ‘enroll’? I assume green means good since my aeotec z-stick is always green. Not sure what yellow, red, and grey means.
I looked all over for Aeotec Z-Wave Gen5 Muti-Sensor firmware but can’t find a firmware one Aeotec’s website. They only seem to have firmware for their other multi-sensor that are not GEN5 version I have.
Not sure if this helps, but this is what I see in my configuration in HABMIN:
Will, after doing a rebooting my computer, it started working. Not sure why that worked since I tried that yesterday and still had problems. Thanks everyone for chipping in!