Closed openPhiL closed 3 years ago
@openPhiL please tell us what version of OpenHAB you are running. And what version of the Velux binding?
There were a lot of changes made in OH v2.5.10 and even more in OH v3.x
using release candidate openHAB3.0.0
Oops, I see you said what version you are running (but which RC is it actually ??)
You should certainly try OH 3.0.0 FINAL or even today's 3.1.0-SNAPSHOT (Build #2154)
ok, will update as soon as 3.1 is out and let you know. Thanks
Just to note: the KLF200's connection socket can get into a zombie state if the OH computer is hard powered off, hard rebooted, or hard disconnected from the LAN; which requires you to power cycle the KLF200 to recover. So what you need to do is run the soft OH 'shutdown' or 'systemctl stop openhab' before doing any of those hard things.
that sounds like my symtoms. Yes, sometimes connecting issues appear, power goes down or openhab hangs. But... is there nothing you can do about it? I assume that is because of the "experts" at velux.. I just throw in the idea of disconnecting the binding after each request in a "valid" way.. as I personally only have actuators, so I don't need the binding to communicate other when I ask it to send information to the device.
You are right that the issue is because the binding uses connection keep-alive. And in theory if one closed the socket after each transaction, this would not be an issue. However, there are two problems with closing after each transaction -- a) the KLF is slooow, it takes 2-3 seconds to establish an SSL connection, and b) after you send commands to the KLF it may send several notification responses (e.g. position notifications when a window is moving) so if you would close the connection after sending the command you would lose the position notifications.
will update as soon as 3.1 is out
If you want to try the 3.1 jar already, you can get it here
Would you have any hint for me how to read out/get the serial (8 HEX) of the rollershutter. I'd really appreciate any help.
When you install the binding, it will first auto discover the Bridge, then if you create a Bridge Thing, it will auto discover all actuators and scenes in the Bridge. You will see their serial numbers in the openhab.log file, and also in the main UI.
Thanks a lot for the immediate response. I must have missed that because the log shows the actuators by its name given in the klf200.velux interface, e.g., Product "RS3" / SLIDER_SHUTTER (bridgeIndex=0,serial=RS3,position=0091). I thought that the serial is some kind of "mac adress" given by the device (per default)
On a real Velux device the serial is indeed something like a mac address. So I suppose that your RS3 device is not from Velux; is it a Somfy device?
you are right, it's a somfy device, but it's still working with the name. thank you!
Closed by #10449
Hi. I use the velux binding for about a year now, and I continue to have issues with it when I restart openhab while the KLF200 remains online. Somehow, it does not reconnect. I need to unplug it, then deactivate the binding, then plug KLF back to power and then activate the binding. Now I start with OH3 and see the same behavior, so I thought to reach out to you. Here is a log where you can see how I start OH3.. only to receive a READ-Timeout, then a connection refused error. You see some timeouts, that is where the KLF200 is unplugged from power.
I wonder why it's me. Looking at the forum, people do not have my issue. Because I just started with a brand new system only to see the same issues, I expect it to be something "strange" on my side. The only thing I can think of is that my openHAB server(10.0.1.12) is not in the same network as my KLF200 (172.16.10.21).
the rest is pretty normal, using release candidate openHAB3.0.0 on Debian 10 VM that I installed using openhabian. I only have velux and astro binding currently.
and this is how it looks like after stopping the binding, power-cycle the KLF200, then starting the binding:
Thanks for checking!! PhiL