The file is not available, Guenther.
it is. Click on āDownloadā on the right side.
Yeah, sorryā¦ My mistake 
Itās quite now, but I had to restart OH2. Before it threw lots of exeptions. But now even the Min/Max Values apear.
Happy now 
@gs4711
Just installed the latest binding (from today). Now I receive the same WARNING Funcat have as well.
2020-01-04 14:28:40.816 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.820 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.824 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.843 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.848 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.852 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.858 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.863 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.870 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.877 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.884 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.887 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.889 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.892 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.894 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.898 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.900 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.902 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.904 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
2020-01-04 14:28:40.908 [WARN ] [nal.handler.utils.ThingConfiguration] - exists(): Channel velux:klf200:home:check does not belong to a thing.
I restarted OH, but I did not clear cache/tmp. Just restartedā¦ Can this be the cause?
Also noticedā¦ If I activate the Velux Bridge Reloadā¦ This happens:
2020-01-04 14:38:19.485 [vent.ItemStateChangedEvent] - V_BRIDGE_RELOAD changed from NULL to ON
2020-01-04 14:38:19.488 [GroupItemStateChangedEvent] - gV changed from NULL to ON through V_BRIDGE_RELOAD
2020-01-04 14:38:20.508 [ome.event.ItemCommandEvent] - Item 'V_BRIDGE_RELOAD' received command OFF
2020-01-04 14:38:20.529 [nt.ItemStatePredictedEvent] - V_BRIDGE_RELOAD predicted to become OFF
==> /var/log/openhab2/openhab.log <==
2020-01-04 14:38:20.573 [WARN ] [ternal.bridge.slip.SCgetDeviceStatus] - Gateway response GW_PASSWORD_ENTER_CFM (12289) cannot be handled at this point of interaction.
==> /var/log/openhab2/events.log <==
2020-01-04 14:38:20.711 [GroupItemStateChangedEvent] - gV changed from ON to OFF through V_BRIDGE_RELOAD
2020-01-04 14:38:20.714 [vent.ItemStateChangedEvent] - V_BRIDGE_RELOAD changed from ON to OFF
==> /var/log/openhab2/openhab.log <==
2020-01-04 14:38:21.079 [WARN ] [lux.internal.bridge.slip.SCgetScenes] - Gateway response GW_GET_STATE_CFM (13) cannot be handled at this point of interaction.
2020-01-04 14:38:21.084 [INFO ] [.internal.handler.VeluxBridgeHandler] - Found velux scenes:
Scene "AlleVinduer100" (index 1) with non-silent mode and 0 actions
Scene "Spisestue75" (index 12) with non-silent mode and 0 actions
Scene "KoekkenLuk" (index 16) with non-silent mode and 0 actions
Scene "AlleVinduer75" (index 17) with non-silent mode and 0 actions
Scene "Spisestue50" (index 3) with non-silent mode and 0 actions
Scene "AlleVinduer50" (index 8) with non-silent mode and 0 actions
Scene "Koekken75" (index 10) with non-silent mode and 0 actions
Scene "StueLuk" (index 18) with non-silent mode and 0 actions
Scene "SpisestueLuk" (index 19) with non-silent mode and 0 actions
Scene "Koekken50" (index 2) with non-silent mode and 0 actions
Scene "AlleVinduerLuk" (index 0) with non-silent mode and 0 actions
Scene "SpisestueVent" (index 9) with non-silent mode and 0 actions
Scene "Stue75" (index 14) with non-silent mode and 0 actions
Scene "StueVent" (index 13) with non-silent mode and 0 actions
Scene "Stue100" (index 7) with non-silent mode and 0 actions
Scene "Stue50" (index 4) with non-silent mode and 0 actions
Scene "Spisestue100" (index 6) with non-silent mode and 0 actions
Scene "AlleVinduerVent" (index 15) with non-silent mode and 0 actions
Scene "Koekken100" (index 5) with non-silent mode and 0 actions
Scene "KoekkenVent" (index 11) with non-silent mode and 0 actions
==> /var/log/openhab2/openhab.log <==
2020-01-04 14:38:21.590 [WARN ] [x.internal.bridge.slip.SCgetProducts] - Gateway response GW_GET_SCENE_LIST_CFM (1037) cannot be handled at this point of interaction.
2020-01-04 14:38:21.594 [INFO ] [.internal.handler.VeluxBridgeHandler] - Found velux actuators:
Product "Vindue 2" / SLIDER_WINDOW (bridgeIndex=1,serial=56:08:1D:26:06:30:0A:CD,position=C800)
Product "Vindue 8" / SLIDER_WINDOW (bridgeIndex=7,serial=56:08:1D:26:06:29:14:5C,position=C800)
Product "Vindue 5" / SLIDER_WINDOW (bridgeIndex=4,serial=56:08:1D:26:06:29:14:5B,position=C800)
Product "Vindue 7" / SLIDER_WINDOW (bridgeIndex=6,serial=56:08:1D:26:06:29:0D:0D,position=C800)
Product "Vindue 4" / SLIDER_WINDOW (bridgeIndex=3,serial=56:08:1D:26:06:29:08:7B,position=C800)
Product "Vindue 6" / SLIDER_WINDOW (bridgeIndex=5,serial=56:08:1D:26:06:30:0C:A1,position=C800)
Product "Vindue 1" / SLIDER_WINDOW (bridgeIndex=0,serial=56:08:1D:26:06:29:06:C7,position=C7C0)
Product "Vindue 3" / SLIDER_WINDOW (bridgeIndex=2,serial=56:08:1D:26:06:29:12:03,position=C800)
==> /var/log/openhab2/openhab.log <==
2020-01-04 14:38:22.124 [WARN ] [.bridge.slip.SCsetHouseStatusMonitor] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:22.136 [WARN ] [.internal.handler.VeluxBridgeHandler] - Activation of House-Status-Monitoring failed (might lead to a lack of status updates).
2020-01-04 14:38:22.139 [INFO ] [.internal.handler.VeluxBridgeHandler] - velux Bridge is online with 20 scenes and 8 actuators, now.
2020-01-04 14:38:42.700 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.717 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.734 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.751 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.769 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.781 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_SCENE_LIST_NTF (1038) cannot be handled at this point of interaction.
2020-01-04 14:38:42.783 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_CFM (515) cannot be handled at this point of interaction.
2020-01-04 14:38:42.796 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.808 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.822 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.836 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.849 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.861 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.875 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.886 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2020-01-04 14:38:42.889 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_FINISHED_NTF (517) cannot be handled at this point of interaction.
2020-01-04 14:38:42.892 [WARN ] [ux.internal.bridge.slip.SCgetProduct] - Gateway response GW_HOUSE_STATUS_MONITOR_ENABLE_CFM (577) cannot be handled at this point of interaction.
Hi Guenther,
i installed the binding but i have a somfy roller where i did replace the serial that where all zeros by a name is not accepted in paper ui, i can not use the name there as serial.
Has there being a change there ?
Hi all,
I he just installed the latest snapshoit Guenther provides to us.
Had to restart OH, but now it seems to be ok with less noisy logs.
@Johnny-b, i use only somfy devices, and it s working well.
Here an exemple of things :
Thing actuator klf200_bureau "bureau - volet (somfy)" @ "bureau" [ serial="bureau" ]
Of course the name has to be the same in klf200.
1 Like
Hi Fabien,
but you are using a manual created Thing file i guess, that what i also did with the old binding.
But now after installing the new i had problems and used the auto discovery of the things in paper ui.
But perhaps i should go back to manual created files.
Correct, i use manual things file.
I ve never used auto discovery for klf200 binding, i cannot help more.
Did I get it right, the KLF is ādicoveredā by Paper-UI an the Windows are then created manualy by .things file??
Can you post the .things file as an example, please?
When the things are discovered by paper ui there is no Things file as far as i know.
All things are visible in the things part of paper ui and also the channels are there.
Some properties are adjustable and others not.
But i did not managed to get it fully working and after a day of puzzling i went back to the previous version of openhab 2.4 and binding 1.14 and will look in to it later.
Hi John,
the textual definition for Somfy devices looks like the following definition for the two Somfy switches below:
/**
* OpenHAB thing definition for velux binding:
* define basic Velux bridge parameters
*
* This is a definition which corresponds to the output of the Bridge
* during startup, i.e.
*
* [INFO ] [x.internal.handler.VeluxBridgeHandler] - Found velux actuators:
* Product "#0" / SLIDER_SHUTTER (bridgeIndex=0,serial=56:32:14:5A:12:1C:05:5F,position=0000)
* Product "#1" / SLIDER_SHUTTER (bridgeIndex=1,serial=53:09:40:5A:0C:23:0A:6E,position=0000)
* Product "DG-M-Window" / SLIDER_WINDOW (bridgeIndex=3,serial=56:23:3E:26:0C:1B:00:10,position=C800)
* Product "#2" / SLIDER_SHUTTER (bridgeIndex=2,serial=53:09:40:5A:0C:2A:05:64,position=0000)
* Product "#4" / SWITCH (bridgeIndex=4,serial=Somfy-Switch,position=C800)
* Product "#5" / SWITCH (bridgeIndex=5,serial=Somfy-Switch,position=C800)
*
* @author Guenther Schreiner - Initial contribution
*/
//
// Definition of Velux bridge velux:klf200:home
//
Bridge velux:klf200:home [ ipAddress="192.168.45.9", tcpPort=51200, password="VerySecret" ] {
// Velux scenes
Thing scene windowClosed [ sceneName="V_DG_Window_Mitte_000" ]
Thing scene windowUnlocked [ sceneName="V_DG_Window_Mitte_005" ]
Thing scene windowOpened [ sceneName="V_DG_Window_Mitte_100" ]
Thing scene unknownScene [ sceneName="ThisIsADummySceneName" ]
// Velux IO-homecontrol devices
Thing window V_DG_M_W [ serial="56:23:3E:26:0C:1B:00:10" ]
Thing rollershutter V_DG_M_S [ serial="56:23:3E:26:0C:1B:00:10" ]
Thing rollershutter V_DG_W_S [ serial="53:09:40:5A:0C:2A:05:64" ]
Thing rollershuffer V_DG_O_S [ serial="53:09:40:5A:0C:23:0A:6E" ]
Thing actuator V_SWITCH1 [ name="#4" ]
Thing actuator V_SWITCH2 [ name="#5" ]
// Virtual rollershutter
Thing vshutter V_WINDOW [ sceneLevels="0,V_DG_Window_Mitte_000#5,V_DG_Window_Mitte_005#100,V_DG_Window_Mitte_100" ]
}
For convenience the unnamed Somfy devices will be accessible by gateway registration number prefixed by a hash. Indeed, I prefer to name them on the KLF200 gateway.
Personally I have not tested the Somfy shutters but the Somfy switches work fine.
Regards, Guenther
Within the paperUI the complete process of autodiscovery is supported.
Regards, Guenther
Thanks for this notice! How did you come to this channel? Iād like to reproduce this issue!
In fact, this message should only appear if a channel is created but the related thing has disappeared???
Best regards, Guenther
Hi @gs4711, just wanted to tell you that the links to the textual sample files are broken @ https://github.com/gs4711/org.openhab.binding.velux.
e.g. https://github.com/gs4711/org.openhab.binding.velux/blob/master/doc/conf/items/velux.items
KR, Chris
Thanks, @csi_oh for your comment. Documentation added to github as well as fixed version for 2.5.1 (disposal/deactivation fixed, localization works even when called by OSGi).
1 Like
It happened after I installed the latest binding (from yesterday). It happened both when I first installed it, and also when I restarted OH.
As mentioned, I did NOT clear cache/tmpā¦ Maybe this will solve solve it.
The binding of 2020/01/04 does cause trouble when you deactivate and reactivate a bridge thing (which is easily possible via paperUI). Up to now, I havenāt been able to reproduce your issue.
There are two issues in my post.
The first one is the one happning when I installed the binding, and it happens again, when I restart OH. When the binding is up running, I dont see this issue again, and everything is working as its suppose to.
I will try clear the cache/tmp later to see, if it will fix this specific issue. It probably will.
The other issue is happening when I use the function, āVelux Bridge Reloadā from a switch in my sitemap.
I removed all of the AUtodetected Windows and the KLF and put in by .thing file.
I had to remove, as only restart of OH was still throwing exeptions. But the āinvertā Values wasnāt set, so I put that in the .things file:
Thing window VeluxBuero [ serial="56:36:13:5A:11:28:45:xx", inverted="true" ]
Since then I only get lots of exeptions. I tried to restart OH, cleared cache, restart the pi, nothing helps.
Is the syntax OK like I wrote it? I canāt find an example with inverted values.