Zwave bindings, Diffrence between Physical State of a device and displayed state

Can someone help me out?

I have a Zwave dimmer connected to on OpenHab2 with the Zwave Binding. I can control them with PaperUI and the Rest-API.

But when I turn On of Off the dimmer manually OpenHab still displays the old state. after a couple of hours if I refresh the page, it refreshes to the right state… but obviously this is not realistic for home automation.

Is there a way to make sure/force OpenHab2 actually reads the state of the physical device and adjust this state in PaperUi and the Rest-API

I saw something about Associations and HABmin2 but (beside having no clue how that works) I really Would rather make it work directly on OpenHab.

Did someone manage to make it work with OpenHab. Have any examples how can I replicate it?


You need to read up about associations - this is how openHAB keeps in sync with your devices state.

Hi Ben, yes indeed, but all I have been reading so far is related to HABMIN2. Would you have any links to examples that use associations in openhab2, either through static or dynamic bindings, this doesn’t seem to be happening automatically with my hardware (zwave stick gen5 and enerwave dimmer).
Note that the energy state does reflect the real current consumption (the dimmer has an energy meter in it), it is just doesn’t update the on/off state when switched manually.

You will need to use Habmin in order to check/set the associations.

Interesting, thanks Ben.

I’m wondering does habmin use the same openhab REST APIs?
if so how can it do things openhab cannot?

Associations are a feature of ZWave devices, and HABmin is effectively part of openHAB - it’s another UI - the same as there are a number of other UIs around.

Yes, it uses the same API, but it’s generally more designed with ZWave in mind. You can probably do the same with PaperUI, but I’m not 100% sure it works as I don’t use it.

I’ve never had to manually change associations - all my zwave devices work fine out of the box. Am I just lucky?

It probably means that the database has been configured appropriately for your device. Associations are not set by default (ie when you initially include the device), but they are configured automatically by the binding based on information in the database. If the database isn’t set correctly, then the associations won’t be set…