Testing Z-Wave binding on openHAB-2

bhuism · February 28, 2016, 3:41pm

see: Testing Z-Wave binding on openHAB-2 for version check

openhab should be de last nightly build as wel I believe, I update daily

see: Testing Z-Wave binding on openHAB-2 for update script

ptmuldoon · February 28, 2016, 5:13pm

Success!! Color change on the Aeon Bulb is working for me now as well. And seemed pretty responsive.

I also have 2 Philips Hue RGBW bulbs here as well, and although I like the look and design of the Phillips better, I think the color change response is faster with the Aeon Zwave bulb.

xsnrg · February 28, 2016, 5:17pm

One thing to make note of as well, since people are saying the channels are not getting created. It seems they actually are created correctly and the UI is not reflecting it. A hard browser refresh usually then shows the channels as green and configured. My experience anyway.

@chris 's fix of removing the device and re-adding it for the RGB bulb was the ticket. I also went through and added all the configurations from the engineering document into the database entry for the bulb yesterday. I haven’t had time to test them though. The bulb does have nice colors, I am pretty happy with it compared to the hue colors.

chris · February 28, 2016, 6:16pm

I think I’ve got everything here working as well as I can for now - unfortunately we’ll be stuck with Celsius for a little while. On the binding side, the conversions work, and I think if we can change the configuration, then it should be possible to configure this. However, there seems to be an issue with ESH core, and at the moment the channel config can’t be updated.

As soon as this is resolved I’ll update the configuration handling…

github.com/eclipse-archived/smarthome

Channel configuration updates

opened 04:22PM - 28 Feb 16 UTC

closed 09:45AM - 22 Apr 16 UTC

cdjackson

I don't seem to be able to update channel configuration (although I'm sure this …worked recently). Below shows the PUT request -: ![image](https://cloud.githubusercontent.com/assets/1041475/13380216/8ff89a6e-de35-11e5-926a-7f44ed44268a.png) And this is the response -: ![image](https://cloud.githubusercontent.com/assets/1041475/13380218/a5a079ae-de35-11e5-9a56-14e11cac9ff2.png) This clearly shows the channel parameter request goes out with config_scale = 1, but returns with config_scale=0. The channel config is defined as follows -: ``` xml <config-description> <parameter name="config_scale" type="integer"> <label>Scale</label> <description>Select the scale for temperature readings</description> <default>0</default> <options> <option value="0">Celsius</option> <option value="1">Fahrenheit</option> </options> </parameter> </config-description> ``` To me, everything looks fine - the type is an int in all cases, the values look correct, but it's not updated. If I look in the update method ([ThingResourceL320](https://github.com/eclipse/smarthome/blob/master/bundles/io/org.eclipse.smarthome.io.rest.core/src/main/java/org/eclipse/smarthome/io/rest/core/thing/ThingResource.java#L320)) and follow through the code, it's unclear how this can update the channel configuration. It updates the label and the thing configuration, but not the channel configuration... Below is the relevant code -: ``` java // ask whether the Thing exists at all, 404 otherwise Thing thing = thingRegistry.get(thingUIDObject); if (null == thing) { logger.info("Received HTTP PUT request for update at '{}' for the unknown thing '{}'.", uriInfo.getPath(), thingUID); return getThingNotFoundResponse(thingUID); } // ask whether the Thing exists as a managed thing, so it can get updated, 409 otherwise Thing managed = managedThingProvider.get(thingUIDObject); if (null == managed) { logger.info("Received HTTP PUT request for update at '{}' for an unmanaged thing '{}'.", uriInfo.getPath(), thingUID); return getThingResponse(Status.CONFLICT, thing, locale, "Cannot update Thing " + thingUID + ". Maybe it is not managed."); } // only process if Thing is known to be managed, so it can get updated thing.setBridgeUID(bridgeUID); updateConfiguration(thing, getConfiguration(thingBean)); // Update the label thing.setLabel(thingBean.label); // update, returns null in case Thing cannot be found Thing oldthing = managedThingProvider.update(thing); if (null == oldthing) { return getThingNotFoundResponse(thingUID); } ``` As above, I thought this worked previously using the same calls, but maybe not, or maybe I'm doing something wrong?

bhuism · February 28, 2016, 7:32pm

Some times the dimmers don’t work, then a restart clears it up:

2016-02-28 20:30:15.003 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter set for zwave:aeon_zw098_00_000:1530ad9faba:node8:switch_dimmer

I’ll try to debug this, my dev environment is almost there

mcarlosro · February 28, 2016, 9:38pm

I will give a try. But how do I update the binding? I already found on the thread how to get the binding version and re-discover the thing, but missing the update.

Thanks,

chris · February 28, 2016, 9:44pm

It won’t be in the binding until tomorrow…

To update from PaperUI, just go to the extensions page, uninstall ZWave, and then re-install it…

pf22 · February 29, 2016, 3:52pm

Hi Chris,

I’ve tested th new binding merged in the openhab2 repository. The binding discovered correctly my devices (right names are displayed in inbox) but it seems to stop the discovery because the devices stay off_line.

How can I verify that all the requests are treated completly ?

Regards,

Pascal

chris · February 29, 2016, 4:51pm

You can either check the log files - this is best - or you can simply send a command and see if it works (ie see if your lights come on). However, if the devices are offline, then this probably isn’t a good sign…

mcarlosro · February 29, 2016, 4:52pm

It works. Thanks.

Only one thing, the device is not using the same naming conventions you have for all other devices. Just in case.

chris · February 29, 2016, 5:23pm

What do you mean by this?

pf22 · March 1, 2016, 7:36am

I had a look on logs and all the transactions seemed to be ok.
I tried to send a command (switch on) on plug and nothing happened. I saw in the trace that the binding was looking for a specific xml file for each node and didn’t find it (node3.xml for example). Does the matter come from this ?

Regards,

Pascal

pf22 · March 1, 2016, 7:41am

When I try to switch on I have this on the logs:
2016-03-01 07:37:01 [DEBUG] [io.rest.core.item.ItemResource:282 ] - Received HTTP POST request at ‘items/zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary’ with value ‘ON’.
2016-03-01 07:37:01 [DEBUG] [.c.thing.internal.ThingManager:298 ] - Delegating command ‘ON’ for item ‘zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary’ to handler for channel 'zwave:fibaro_fgwpe_00_000:aa3aa4b2:node3:switch_binary’
2016-03-01 07:37:01 [DEBUG] [.b.z.handler.ZWaveThingHandler:582 ] - NODE 0: Command received zwave:fibaro_fgwpe_00_000:aa3aa4b2:node3:switch_binary --> ON
2016-03-01 07:37:01 [ERROR] [.c.thing.internal.ThingManager:312 ] - Exception occured while calling handler: java.lang.NullPointerExceptionjava.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:206)
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:157)
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:72)
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:56)
at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:301)
at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:46)
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:188)
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Caused by: java.lang.NullPointerException: null
at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleCommand(ZWaveThingHandler.java:599)
at org.eclipse.smarthome.core.thing.internal.ThingManager$2.call(ThingManager.java:304)
at org.eclipse.smarthome.core.thing.internal.ThingManager$2.call(ThingManager.java:1)
… 4 common frames omitted

2016-03-01 07:37:01 [INFO ] [arthome.event.ItemCommandEvent:43 ] - Item ‘zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary’ received command ON
2016-03-01 07:37:01 [DEBUG] [.c.thing.internal.ThingManager:341 ] - Delegating update ‘ON’ for item ‘zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary’ to handler for channel 'zwave:fibaro_fgwpe_00_000:aa3aa4b2:node3:switch_binary’
2016-03-01 07:37:01 [INFO ] [smarthome.event.ItemStateEvent:43 ] - zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary updated to ON
2016-03-01 07:37:01 [INFO ] [s.event.ItemStateChangedEvent :43 ] - zwave_fibaro_fgwpe_00_000_aa3aa4b2_node3_switch_binary changed from OFF to ON

Does NODE 0 means that the node3 is unknown ?

Regards,

Pascal

pf22 · March 1, 2016, 8:39am

Also, I have to notice that the plug device worked fine with an older version of your openhab2 zwave binding.

chris · March 1, 2016, 1:10pm

The failure to open the xml files isn’t an issue - it does however indicate that the device probably usnt completing initialisation as these files are generated by the binding when initialisation completes.

The node 0 in the log is strange - I’ll check the log properly when I get a chance.

I don’t think you have said what the device is?

Chris

pf22 · March 1, 2016, 1:53pm

In fact, I saw the files for nodes after staring the setup.

The device is a plug Fibaro FGPWE.
I have replace the binding with the older and it works now with the same plug.

But, this older binding creates two things for the device (the first one which seems to be temporary got the label uknown and status INITIALIZING and the second one have the full label Fibaro SYSTEM FGWPE

Regards,

Pascal

feens · March 1, 2016, 2:37pm

@chris just curious what I need to do to get my doorbell (discussed previously in here) into the database. It’s a battery device and there’s no xml file for it. I had posted the various log entries for it, but not sure what step to take next. Thanks!

chris · March 1, 2016, 4:55pm

Can you open an issue on github for this - I think there’s clearly a problem with the device, and this thread probably isn’t the best place to keep track of it…

Thanks
Chris

chris · March 1, 2016, 4:58pm

When do you mean? Are you talking about your initial setup - ie for an older version of the binding?

What ‘older’ binding are you referring to? Please can you provide a version number - or preferably a logfile as it’s difficult to comment with such limited information…

Christer_Akerlund · March 1, 2016, 8:54pm

Whats the correct way to update the binding when using the snapshot? is that through paper ui and uninstall/install it again or do i need to update the entire snapshot?
Also, what does uninstall/install of the binding do to any links that is set? If they are cleared, can i configure them statically directly in the items files or are the names/ids randomized?

/C