Pairing problem with Hue emulation and Harmony hub

Setup, Configuration and Use Beginners
1
  • Platform information:
    • desktop PC, fast CPU, 64GB ram
    • OS: windows 10
    • Java Runtime Environment: which java platform is used and what version
    • openHAB version: 2.5.3
  • Issue of the topic:

The android setup and control program for the Logitech Harmony lets one to add Hue devices. I have a TP-link dimmer configured in OH that I’m trying to make available through the Hue emulation service to the harmony hub and remote.

I have gotten to the point where the Harmony app discovers the OH Hue emulation service and am being asked by the app to press the center button on the Hue bridge device. I obviously don’t have such a device or button to press.

image
image672×1185 71 KB

I’ve tried toggling the “Device Pairing” switch to “on” in the Hue Emulation configuration page, but the app doesn’t detect the emulated hub.

I’ve been using this page to get things working to this point.

I have added “set OPENHAB_HTTP_PORT=80” to start.bat. Prior to doing this, the app didn’t detect the emulated hue bridge, probably because OH was running on port 8080.

I opened the firewall for incoming port 1900/udp connections.

I expect to run into other problems as the documentation (above) has several methods for configuring the item I want to expose, including setting tags, but I don’t see any tags in the item’s configuration page in PaperUI. Also, the Category was set to DimmableSwitch (I think), not Switch or Dimmer as required by the doc, and a bunch of new things have been discovered (CLIP Generic …" since I added the Hue emulator service.

Anyways, trying to get past this one hurdle right now.

  • Please post configurations (if applicable):
    • Items configuration related to the issue

Configuration file: D/openhab-2.5.3/userdata/config/org/openhab/hueemulation.config

:org.apache.felix.configadmin.revision:=L"12"
createNewUserOnEveryEndpoint=B"false"
discoveryIp="10.0.0.4"
ignoreItemsWithTags="internal"
pairingEnabled=B"false"
pairingTimeout="60"
permanentV1bridge=B"false"
restrictToTagsColorLights="ColorLighting"
restrictToTagsSwitches="Switchable"
restrictToTagsWhiteLights="Lighting"
service.pid="org.openhab.hueemulation"
temporarilyEmulateV1bridge=B"false"
uuid="028fe059-db90-4df4-bbea-aa52e0d1d3a7"

Response from http://localhost:80/description.xml:

1
0

http://[fe80:0:0:0:69ff:9b12:a368:f5e4]:80/

  urn:schemas-upnp-org:device:Basic:1
  openHAB Hue Emulation ([fe80:0:0:0:69ff:9b12:a368:f5e4])
  Royal Philips Electronics
  http://www.openhab.org
  Philips hue Personal Wireless Lighting
  Philips hue bridge 2015
  BSB002
  http://www.meethue.com
  028FE059DB90
  uuid:028fe059-db90-4df4-bbea-aa52e0d1d3a7
  openHAB
  index.html
  
  	
  		image/png
  		48
  		48
  		24
  		hue_logo_0.png
  	
  	
  		image/png
  		120
  		120
  		24
  		hue_logo_3.png

Any assistance will be appreciated!

Thanks,
- Eric

2

Don’t know how the harmony hub works exactly. You do need to toggle the pairing mode switch when you ask the harmony to look for devices.

The question is do you have any devices configured to pair. If using files config you need to add the lighting or switchable tags. The docs should specify this. Don’t know how to do it in paper ui. I believe you need to update in the rest api.

I am feeling you have the hue hub setup but no items shared.

3

I Have the same problem. Did you solve it?

4

Nope. This put my minor home automation project on hold. I’m going to check out Home Assistant instead when I get back to this project since it can also run entirely on-premises/cloudless too. That’s my only criteria beyond “does it work?”

Thanks,
- Eric

5

Are you on windows or Linux? On Linux I would install nginx if using openhabian menu there is an option to do this. Make sure you can access openHAB in port 80.

6

Linux and docker with nginx already on port 443 and 80. I can access the xmls from http://192.168.1.3/description.xml from a laptop on the same network.

7

Ok my problem is resolved. I stopped all my other containers and restarted openhab container. Then the pairing worked. After that i started all the containers i had stopped. The problem was probably because of som port conflict.