[velux] New OpenHAB2 binding - feedback welcome!

tstark · January 6, 2020, 9:23pm

Hi Guenther.

Sorry for the delay. Holidays and the kids needed attention . Anyway I did remove all things (bridge and shutter) and recreated them using different thing IDs. Apparently openhab did reuse an old configuration when using the old id. Now I only get that bunch of Thing 'velux:klf200:360b7a8c' has been updated. messages but that is much less disturbing … Just in case… here is my current log tail.

2020-01-06 22:12:10.037 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - Initializing Velux veluxBridge handler for 'velux:klf200:360b7a8c'.
2020-01-06 22:12:10.045 [hingStatusInfoChangedEvent] - 'velux:klf200:360b7a8c' changed from ONLINE to UNKNOWN
2020-01-06 22:12:10.055 [INFO ] [.binding.velux.internal.VeluxBinding] - veluxConfig[protocol=slip,ipAddress=192.168.178.53,tcpPort=51200,password=**********,timeoutMsecs=500,retries=5,refreshMsecs=10000,isBulkRetrievalEnabled=true,isSequentialEnforced=false,isProtocolTraceEnabled=false]
2020-01-06 22:12:10.062 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2020-01-06 22:12:15.249 [INFO ] [ab.binding.velux.bridge.slip.SClogin] - velux bridge connection successfully established (login succeeded).
2020-01-06 22:12:16.269 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - Found velux scenes:
2020-01-06 22:12:16.823 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - Found velux actuators:
2020-01-06 22:12:17.331 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - velux Bridge is online with 0 scenes and 2 actuators, now.
2020-01-06 22:12:17.338 [hingStatusInfoChangedEvent] - 'velux:klf200:360b7a8c' changed from UNKNOWN to ONLINE
2020-01-06 22:12:47.944 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:12:47.986 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:12:48.544 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:12:48.562 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:12:49.151 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:12:49.173 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:49.779 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:49.806 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:50.342 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:50.356 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:50.996 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:13:51.007 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:51.631 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:51.655 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:52.196 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:52.210 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:52.820 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:14:52.834 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:53.483 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:53.506 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:54.059 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:54.076 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:54.626 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.
2020-01-06 22:15:54.637 [me.event.ThingUpdatedEvent] - Thing 'velux:klf200:360b7a8c' has been updated.

If you want more information I will be happy to share but for me its okay as it is now.

Thanks a lot and keep on with your great work. Andreas

Cernon · January 6, 2020, 9:58pm

Thanks for the answer. I‘m Not a programmer. I Use the 2.5 Binding over Papier UI and than text configuration. Where I should type isProtocolTraceEnabled=true? With the console i have no expierience…

For me the delay is Not so bad because I want to use the Commands in rules. I have 7 rollershutter. When I set the group switch for all rollershutter there is the delay. The rollershutter goes one after the other up or down and Not at the Same time. I‘m Not sure how Long the Delay is for only one rollershutter

gs4711 · January 7, 2020, 9:26am

Hello,

the configuration can be done via paperUI under the KLF200 configuration page: Please activate the switch Enable Protocol Trace. It should look like:

To move all shutters in parallel, a good idea could be to define such a scene.

Windrad · January 7, 2020, 11:09am

I use Window -Motors, and there is a short delay from clincking to Motormovement of about 1s, not much more. And all 5 Motors do move simultaneously.

Cernon · January 10, 2020, 7:55pm

wow, what a difference.

I Install the newest binding. I had problems and had delete all things an re install them.

But now it works great.

The log ist calm. And there ist no delay. I can count 21,22 and the roller shutter run. When I activate all rollershutter, there ist nearly no delay between the start of the different rollershutter.

@gs4711: great work!! I am happy I think you don’t need an log, anymore.

Celaeno1 · January 17, 2020, 10:55pm

Today I paired my 7 new Somfy Oximo IO rollershutters with Velux KLF 200 and afterwards with openHAB2.

I would like to praise this fantastic binding. Everything works flawlessly and straight away. Support of @gs4711 also was excellent. Thanks a lot!

P.S. Had a little problem with API password at the beginning. It is the same like the Wifi password. But Guenther also helped me immediately.

P.P.S: Integration with Alexa also works.

gs4711 · January 23, 2020, 5:01am

Note to all current users of this binding. Out of the review process some modifications will occur within the next version of this binding: Some information being present as channel will exist only as property of the bridge furthermore. In fact, that are:

“firmware”
“ipAddress”
“subnetMask”
“defaultGW”
“DHCP”
“WLANSSID”
“WLANPassword”
“products”
“scenes”
“check”

Will keep you informed. Rgds, Guenther

andres_meyer · January 23, 2020, 8:56am

Thanks for all the effort and great progress in getting this mainlined!

funcat · January 23, 2020, 12:24pm

Hi Alex,
Glad to see another somfy user =)
I have a question for you about this binding for somfy devices :
Do you use the “MY/favorite” position on somfy rollershutter ?
If so, could you tell me if the binding read the position properly when the rollershutter is at this position ?
For me and some friends it does not (INFO/WARN inside logs).
Just curious to see another user setup , it could help.
Thx

Celaeno1 · January 23, 2020, 12:54pm

Sorry. I do not use it actually. But I will try out soon.

I’ll inform you then.

csi_oh · January 24, 2020, 3:19pm

Hi there,

updated today from 1.14.0.201903161709 to 2.5.1.202001051139 and adopted textual configs according to sample files from https://github.com/gs4711/org.openhab.binding.velux.

Got a successful connect (shortened):

2020-01-24 15:48:43.276 [INFO ] [.internal.handler.VeluxBridgeHandler] - Found velux actuators:
[...]
Product "Office" / SLIDER_SHUTTER (bridgeIndex=3,serial=56:32:14:26:0F:0C:00:B1,position=0000)
[...]
2020-01-24 15:48:43.788 [INFO ] [.internal.handler.VeluxBridgeHandler] - velux Bridge is online with 0 scenes and 6 actuators, now.

Unfortunately the above mentioned isn’t moving at all with this definitions;

velux.things

Bridge velux:klf200:home "KLF200" @ "KLF200" [ ipAddress="X.X.X.X", protocol="slip", tcpPort=51200, password="X" ] {
    Thing rollershutter VELUX_Office [ serial="56:32:14:26:0F:0C:00:B1" ]
}

velux.items

Rollershutter VELUX_Office "Büro Velux [%d]" { channel="velux:klf200:home:VELUX_Office" }

Unfortunately I don’t have any further log-entries except from events.log:

2020-01-24 15:51:33.625 [ome.event.ItemCommandEvent] - Item 'VELUX_Office' received command DOWN
2020-01-24 15:51:33.631 [nt.ItemStatePredictedEvent] - VELUX_Office predicted to become NULL

Many thanks and KR,
Chris

csi_oh · January 28, 2020, 6:17am

Hi there,

anyone else having that problem with non-moving rollershutters? 1.14.0.201903161709 is working fine, but I can’t get 2.5.1.202001051139 to work - tried in several variations.

The binding reads data from the KLF200 successfully (bridge status, SW version, …).

Any ideas @gs4711? Otherwise I’d need to roll-back.

Many thanks & KR,
Chris

Celaeno1 · January 28, 2020, 7:10am

@csi_oh

Could you please post your latest .things, .sitemap and .items configuration? (or is it still the same like in your post?

csi_oh · January 28, 2020, 7:45am

Hi @Celaeno1,

many thanks for reply. The textual configs are the same - sitemap is displaying the whole group (gVelux).

I tried with different element-names (.things and .items) and different environments with OH stable (Debian9+Zulu8, Debian9+JDK11, Debian10+Zulu8, Debian10+JDK11, Debian10+JDK13) - in no combination I could get the rollershutters moving, but in every combination I was able to read data from the KLF200 (like bridge status, etc.).

When I use the old .jar (1.14.0.201903161709) everything is working fine (with old textual configs of course).

I get no errors, whatsoever. Also, when I “find products” via the KLF interface, the rollershutters are moving so I can safely say that my problem is somewhere within the OH environment.

KR,
Chris

Celaeno1 · January 28, 2020, 8:14am

.
Your item Rollershutter VELUX_Office is not in group (gVelux) ?
.

Are your sitemap elements for rollershutter looking like this?

Or like this?

csi_oh · January 28, 2020, 8:34am

Hi @Celaeno1,

please find attached a current screenshot from that sitemap. VELUX_Office is in that group (=“Büro Velux”), I didn’t post it because I wanted to show only relevant declarations.

Celaeno1 · January 28, 2020, 10:02am

Mhhh, the only “strange” thing is that the thing name VELUX_Office is exactly like the item name VELUX_Office. Could you please change the item name?

When you use PaperUI --> Control --> your rollershutter: e.g. like this…

Is it also not running?

csi_oh · January 28, 2020, 10:09am

Hi,

I’ll investigate at home - thanks meanwhile :)!

Actually i got that identical naming out of official documentation @ https://github.com/gs4711/org.openhab.binding.velux/blob/master/doc/conf/items/velux.items:

// Velux Actuator channels

Rollershutter	V_DG_M_W	"DG Fenster Bad [%d]"    	{ channel="velux:klf200:home:V_DG_M_W" }

KR,
Chris

Celaeno1 · January 28, 2020, 10:13am

Then it should be no problem…

Celaeno1 · January 28, 2020, 11:48am

What happens when you execute the following command (in karaf console)?

smarthome:links list |grep VELUX_Office