I don’t
I have the following installed:
bindings: insteonplm1, nest1, ntp, chromecast, astro, mqtt1, network, harmonyhub
UI: paper, basic, classic
Voice: voicerss
Persistance: openhabcloud
And I have the hue emulator jar installed from this thread but that’s it. I did run the commands listed above to redirect port 80:
And I added an aliased IP address, but that was messing with my SSH abilities so I removed the aliased IP and reset the iptables back to default. Do I need to reroute and add an aliased IP if I’m not running anything else on port 80? Or is one of my bindings running on port 80 that I’m not aware of?
Yup, I sure do, and my devices are listed there to. Plus it lists the manufacturer as Phillips. So what is causing the discovery to be listed on port 8080 instead of 80? And is there a way to take care of it that still allows me to SSH into the raspberry pi to do remote configuration? I may have messed up when trying to set up the iptables but I use SSH for all of my configuration.
You would still need to redirect port 80… So just run the iptables command with the one IP you have and it should work fine.
So; this command if your IP is 192.168.1.2:
In case anyone needs to know, that did the trick. You can’t run ha-bridge at the same time as hue emulation since they’re basically trying to do the same thing and occupying the same ports. Disabling ha-bridge and running the iptables command above resolved all the issues and it’s all working great now!
I’m still having the issue where everything looks good from the server end, just not seeing the google home or the android phone that I am setting it up with send ANY packets, with trace logging enabled in the emulator.
Is there anything that can block the application from sending that information out? I can use other programs like BubbleUpnp and they seem to work fine… just not seeing anything when the hue app from google home tries to connect.
Any ideas? Can someone show me log files from when they click “pair” in the app with trace logging enabled for the emulator? Is there anything I can do to try and debug this, or help someone debug this?
Home & Hue emulation is generally working well for me since a couple of weeks.
But today I added two lights to openhab: one simple switch and one Fibaro Dimmer 2.
I have linked items and can control the dimmer and switch just fine from the openhab UI.
Naturally, I then want Google Home to be able to control them so I go into the file org.eclipse.smarthome.core.items.Item.json and adding tag “Lighting” and a label for the switch. It then works fine with Google Home.
But I can not find the dimmer anywhere in this file. What am I missing?
I had similar issues, I found that my firewall was blocking the UPNP requests. Try to use an UPNP browser app on your phone/tablet and see if you see the Hue Emulator. I even see it in the windows 10 network browser now.
And I found the error why my dimmers did not show up in org.eclipse.smarthome.core.items.Item.json:
Items will not be created for ‘real’ if you use Simple Mode, so I will simply create the links manually from now on.
So i tried deleting the files in the /var/…openhab/…folder, renaming them in my items file and restarting openhab.
I unlinked and relinked hue in the ghome app.
I now have triplicate items in the app.
What is going on here?