Hi,
I need to install the homematic binding with the version 2.1 (latest snapshot). When I put the binding in the addon folder it
is not visible in Paperui.
How do install the latest snapshot in the right way? I don’t want to put the kar file in the addon folder.
Thanks
Désirée
@MHerbst or @gerrieg as this get’s asked quite often, would you care to answer it in Frequently Asked Questions (FAQs)
Thanks!
If @gerrieg is not faster than me, I can create an entry in the FAQ. But before I need to check that the answer is really correct 
Hi @desiw,
If you put a binding into the add-on folder this binding won’t be shown in Paper UI as installed under “Add-Ons”. But as far as I remember it should be visible under Configuration/Bindings. Do you see it there?
If not it possible could not be loaded. In this case the openhab.log should help us.
Martin
Hi Martin,
no can’t see the binding in Paper UI.
Tomorrow I will send the openhab.log.
Kind regards
Désirée
Hi Désirée,
it’s strange that the openhab logs show nothing. I think we need the karaf console.
Can you open the karaf console and check the output of bundle:list | grep Homematic . If it shows 2.0.0. then the old version is loaded from the cache. In this case run bundle:uninstall org.openhab.binding.homematic and restart openHAB.
Is now the binding loaded from the addons folder? You can check the bundle state again with bundle:list | grep Homematic.
If not please please active the debug log (log:set DEBUG org.openhab.binding.homematic) and restart openHAB. Does the log now contain information regarding the Homematic binding.
Kind regards
Martin
Hi Martin,
I followed your description, but the snapshot 2.1 never was displayed in the Paper UI. I tested a bit and installed the homematic binding 2.0 and uninstalled it again via karaf. After the restart of karaf I added the homematic binding 2.1. The karaf console showed me then:
In my inbox 8 items was added. I did not install the binding 2.1 via Paper UI or karaf.
Here is my log:
2017-04-08 16:48:46.112 [INFO ] [core.karaf.internal.FeatureInstaller] - Uninstalled ‘openhab-binding-homematic’
2017-04-08 16:53:44.413 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent INSTALLED - org.openhab.binding.homematic
2017-04-08 16:53:45.221 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent RESOLVED - org.openhab.binding.homematic
2017-04-08 16:53:45.233 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent STARTING - org.openhab.binding.homematic
2017-04-08 16:53:45.328 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.type.ChannelTypeProvider, org.openhab.binding.homematic.type.HomematicChannelTypeProvider}={component.name=org.openhab.binding.homematic.type.HomematicChannelTypeProviderImpl, component.id=233, service.id=382, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.354 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider, org.openhab.binding.homematic.type.HomematicConfigDescriptionProvider}={component.name=org.openhab.binding.homematic.type.HomematicConfigDescriptionProviderImpl, component.id=234, service.id=383, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.367 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingTypeProvider, org.openhab.binding.homematic.type.HomematicThingTypeProvider}={component.name=org.openhab.binding.homematic.type.HomematicThingTypeProviderImpl, component.id=235, service.id=384, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.405 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.type.HomematicTypeGenerator}={component.name=org.openhab.binding.homematic.type.HomematicTypeGenerator, component.id=237, service.id=385, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.474 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.homematic.handler.HomematicThingHandlerFactory, component.id=236, service.id=386, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.515 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={component.name=org.eclipse.smarthome.binding.homematic.discovery.bridge, component.id=238, service.id=387, service.bundleid=260, service.scope=bundle} - org.openhab.binding.homematic
2017-04-08 16:53:45.528 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent STARTED - org.openhab.binding.homematic
2017-04-08 16:53:45.601 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.21,callbackHost=192.168.178.35,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=ccu,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,groupPort=9292,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2017-04-08 16:53:45.611 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=388, service.bundleid=260, service.scope=singleton} - org.openhab.binding.homematic
2017-04-08 16:53:45.985 [INFO ] [ternal.communicator.client.RpcClient] - Interface ‘WIRED’ on gateway ‘5d69f156’ not available, disabling support
2017-04-08 16:53:46.164 [DEBUG] [ommunicator.AbstractHomematicGateway] - Initializing gateway with id ‘5d69f156’
2017-04-08 16:53:46.168 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=CCU,type=CCU2,firmware=2.27.7,address=LEQ0114342,wired=false,hmip=true,cuxd=true,group=true]
2017-04-08 16:53:46.170 [DEBUG] [ommunicator.AbstractHomematicGateway] - Used Homematic transfer modes: RF:BIN_RPC, HMIP:XML_RPC, CUXD:BIN_RPC, GROUP:XML_RPC
2017-04-08 16:53:46.274 [DEBUG] [nal.communicator.server.BinRpcServer] - Initializing BIN-RPC server at port 9126
2017-04-08 16:53:46.280 [DEBUG] [nal.communicator.server.XmlRpcServer] - Initializing XML-RPC server at port 9125
2017-04-08 16:53:46.465 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value ‘true’ for ‘KEQ0172385:0#STICKY_UNREACH’ from gateway with id ‘5d69f156’
2017-04-08 16:53:46.472 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value ‘true’ for ‘KEQ0172385:0#UNREACH’ from gateway with id ‘5d69f156’
2017-04-08 16:53:46.473 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value ‘true’ for ‘KEQ0968404:0#STICKY_UNREACH’ from gateway with id ‘5d69f156’
2017-04-08 16:53:46.474 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value ‘true’ for ‘KEQ0968404:0#UNREACH’ from gateway with id ‘5d69f156’
2017-04-08 16:53:56.580 [DEBUG] [ommunicator.AbstractHomematicGateway] - Starting event tracker for gateway with id ‘5d69f156’
2017-04-08 16:53:56.585 [DEBUG] [ommunicator.AbstractHomematicGateway] - Starting connection tracker for gateway with id ‘5d69f156’
2017-04-08 16:53:56.590 [DEBUG] [very.HomematicDeviceDiscoveryService] - Stopping Homematic discovery scan
2017-04-08 16:53:56.595 [DEBUG] [very.HomematicDeviceDiscoveryService] - Starting Homematic discovery scan
2017-04-08 16:53:56.599 [DEBUG] [very.HomematicDeviceDiscoveryService] - Waiting for finishing Homematic device discovery scan
2017-04-08 16:53:57.185 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘BidCoS-RF’ (HM-RCV-50) with 156 datapoints
2017-04-08 16:53:57.191 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘HM-RCV-50’ with 156 datapoints
2017-04-08 16:53:57.308 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-RCV-50:5d69f156:BidCoS-RF’ to inbox.
2017-04-08 16:53:57.585 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘KEQ0172385’ (HM-LC-Sw1-Pl-2) with 21 datapoints
2017-04-08 16:53:57.587 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘HM-LC-Sw1-Pl-2’ with 21 datapoints
2017-04-08 16:53:57.602 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-LC-Sw1-Pl-2:5d69f156:KEQ0172385’ to inbox.
2017-04-08 16:53:58.760 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘KEQ0968404’ (HM-ES-PMSw1-Pl) with 87 datapoints
2017-04-08 16:53:58.762 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘HM-ES-PMSw1-Pl’ with 87 datapoints
2017-04-08 16:53:58.775 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: POWERMETER|BOOT, BOOT
2017-04-08 16:53:58.815 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-ES-PMSw1-Pl:5d69f156:KEQ0968404’ to inbox.
2017-04-08 16:53:58.828 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘LEQ0535149’ (HM-ES-PMSw1-Pl) with 87 datapoints
2017-04-08 16:53:58.836 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-ES-PMSw1-Pl:5d69f156:LEQ0535149’ to inbox.
2017-04-08 16:53:59.286 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘LEQ0875283’ (HM-LC-Sw1-Pl-2) with 25 datapoints
2017-04-08 16:53:59.294 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-LC-Sw1-Pl-2:5d69f156:LEQ0875283’ to inbox.
2017-04-08 16:53:59.973 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘JEQ0109301’ (HM-LC-Bl1PBU-FM) with 29 datapoints
2017-04-08 16:53:59.975 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘HM-LC-Bl1PBU-FM’ with 29 datapoints
2017-04-08 16:54:00.316 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘LEQ0076970’ (HM-LC-Sw1PBU-FM) with 27 datapoints
2017-04-08 16:54:00.319 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘HM-LC-Sw1PBU-FM’ with 27 datapoints
2017-04-08 16:54:00.335 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘homematic:HM-LC-Sw1PBU-FM:5d69f156:LEQ0076970’ to inbox.
2017-04-08 16:54:03.581 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device ‘CUX2801002’ (EMPTY) with 498 datapoints
2017-04-08 16:54:03.583 [DEBUG] [atic.type.HomematicTypeGeneratorImpl] - Generating ThingType for device ‘EMPTY’ with 498 datapoints
2017-04-08 16:54:03.586 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|RAND, RAND
2017-04-08 16:54:03.589 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_SETS, CMD_SETS
2017-04-08 16:54:03.591 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_EXEC, CMD_EXEC
2017-04-08 16:54:03.592 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|STATE, STATE
2017-04-08 16:54:03.594 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_RETL, CMD_RETL
2017-04-08 16:54:03.595 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|SET_STATE, SET_STATE
2017-04-08 16:54:03.597 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CONTROL, CONTROL
2017-04-08 16:54:03.599 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_QUERY_RET, CMD_QUERY_RET
2017-04-08 16:54:03.601 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|SYSLOG, SYSLOG
2017-04-08 16:54:03.602 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_RETS, CMD_RETS
2017-04-08 16:54:03.605 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|STOP, STOP
2017-04-08 16:54:03.606 [DEBUG] [binding.homematic.type.MetadataUtils] - Description not found for: KEY|CMD_SETL, CMD_SETL
Kind regards
Désirée
If you put the binding into the addons folder it will appear in Paper UI as an installed add-on. But as you can see in the karaf console it is active.
To me everything seems to be OK now or am I missing something? You can ignore the messages regarding the missing descriptions.
Martin
Did you make sure that the original binding is not active anymore? Depending on your setup this could be either in PaperUI or in the addons.cfg activated. The addons from the addons folder will automatically be activated (the same way as it was with openhab 1). I guess if you do not deactivate the stable one, there will be a conflict.
Hi,
the binding 2.0 is not active, but I can’t see the 2.1 binding in Paper UI.
Homemtic is working, but I get sometimes following error:
Max alive time reached for socket on port 2001
I changed already the parameter “alive interval” to 900, but it did not help.
Kind regards
Désirée
The only place where you can see the binding in Paper UI is under Configuration/Bindings. The important information is coming from bundle:list. If you see it here with state “Active” the binding is running.
Max alive time reached for socket on port 2001
I have never had this message. Maybe @gerrieg has an idea.
Hi Martin,
in Paper UI / Configuration/ Bindings I can the homematic binding. I thought when I put the binding into
the addon folder it would be visible.
Kind regards
Désirée
