I suggest that the Velux binding is expanded, so it can reboot the KLF 200 device. This is becuase the KLF 200 device is not always stable and needs a power recycling with regular intervals.
It seems that a reboot api is available in the SLIP protocol - search for GW_REBOOT_REQ. I guess the binding should then go in wait and after a while perform a login again when KLF 200 is ready.
Thanks.
Remember to update the documentation, which currently states, there is no autodiscovery of the KLF200.
Please also include the reboot function and a rule example.
Thanks.
I suggest that the Velux binding is expanded, so it can reboot the KLF 200 device. This is becuase the KLF 200 device is not always stable and needs a power recycling with regular intervals.
It seems that a reboot api is available in the SLIP protocol - search for GW_REBOOT_REQ. I guess the binding should then go in wait and after a while perform a login again when KLF 200 is ready. Thanks.