Alexa cannot find any devices anymore with the HueEmulation Service

[Terra]

Hi guys,

Since my upgrade yesterday Alexa cannot control my published devices with HueEmulation anymore. I tried uninstalling and reinstalling it, checked my *.item files of the tags are correct and case sensitive however I cannot get it working

Alexa cannot find my devices anymore.

Example Item:

Switch Outlet12 “Christmas Tree” (Outlets) [“Switchable”] { channel=“tplinksmarthome:hs100:A2713C:switch” }

When I look at the URL’s I get the following:

http://192.168.0.15:8080/api/

[{“error”:{“address”:“/”,“description”:“GET not allowed for this resource”,“type”:4}}]

http://192.168.0.15:8080/api/discovery.xml

[{“error”:{“address”:“/discovery.xml”,“description”:“Not Authorized”,“type”:1}}]

http://192.168.0.15:8080/api/testuser/lights

[{“error”:{“address”:“/testuser/lights”,“description”:“Not Authorized”,“type”:1}}]

When I reinstalled the binding the only lines in the log I got were:

2018-12-28 11:43:19.102 [INFO ] [core.karaf.internal.FeatureInstaller] - Uninstalled ‘openhab-misc-hueemulation’
2018-12-28 11:43:19.103 [thome.event.ExtensionEvent] - Extension ‘misc-hueemulation’ has been uninstalled.
2018-12-28 11:44:04.233 [INFO ] [eemulation.internal.ConfigManagement] - Hue Emulation pairing disabled. Service available under /api
2018-12-28 11:44:04.248 [thome.event.ExtensionEvent] - Extension ‘misc-hueemulation’ has been installed.

http://192.168.0.15:8080/api/description.xml
<root xmlns=“urn:schemas-upnp-org:device-1-0”>
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.0.15:8080/&lt;/URLBase&gt;
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>openHAB Hue Emulation (192.168.0.15)</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.openhab.org</manufacturerURL>
<modelDescription>Philips hue compatible Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>45707FAE545B</serialNumber>
<UDN>uuid:45707fae-545b-4ffa-9cb5-90e37899d74b</UDN>
<presentationURL>index.html</presentationURL>
<iconList>
<icon>
<mimetype>image/png</mimetype>
<height>48</height>
<width>48</width>
<depth>24</depth>
<url>hue_logo_0.png</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<height>120</height>
<width>120</width>
<depth>24</depth>
<url>hue_logo_3.png</url>
</icon>
</iconList>
</device>
</root>

Can anyone help?

[Celaeno1 (Alex)]

@Terra

[“Switchable”]

Tag [“Switchable”] is not supported anymore, you have to use tag [ “Lighting” ] instead.

See also here: (not so easy to find… )

["Switchable"] Items no longer found at Amazon Echodot after update to openhab 2.4

Hello, I updated on openhab2.4 yesterday. My Amazon Echodot then had errors with access to all lamps and switches that were created. Then I turned on the pairing mode in the Hue emulation to search the devices again. However, only the lamps with [“Lighting”] are found. The switches that worked with [“Switchable”] are no longer found. But this is set in the Hue emulation. Can anyone give me any tips on how to fix this?

After Upgrade to OpenHAB 2.4 some Hue emulated devices do not react

hi, I have a Little Problem after upgrading openHAB to Version 2.4. I had Hue Emulation running with openHAB 2.3 and was able to publish some “virtual” devices that trigger rules. For example I have a device called “Alle Geräte” (german for “all devices”) that triggers a rule to switch off all devices (Amplifier, TV, XBOX, Bulbs etc) in my Living room. That worked without any Problems. Now, after the upgrade to openHAB 2.4, Alexa is not able to trigger this device any more. It is still possibl…

Hue Emulation only ["Lighting"] tag works for Alexa

I’m using the Hue Emulation now for more than a year for connecting my items to Alexa. Since the last update (2.4 developer build of the todays 2.5 developer build) most of my devices were no longer reachable from Alexa. I’ve deleted all devices from the alexa view, and started new dicovery. Now ony [“Lighting”] taged device found and all are now metioned as “Dimmable Light” I’ve played with the different settings in the Hue Emulation service (incl. changing the tags) settings, but always …

[SOLVED] Alexa discovers zero devices (with openHAB 2.4 M8 and hue-emulation)

Platform information: Hardware: laptop, on 192.168.1.27 OS: windows 10 Java Runtime Environment: 1.8.0_191 openHAB version: 2.4 M8 one Echo and one Echo Dot, latest revisions (bought in December 2018) I’m new to openHab, and trying to setup an integration with Alexa trough hue-emulation for the last 2 weeks. I read several topics related to hue-emulation and Alexa, and got this far: openHAB is correctly configured with my KNX/IP gateway, here’s the .things file: Bridge knx:ip:bridge [ …

[Hue Emulation] Items with Switchable tag are not discovered

I upgraded to snapshot 1445 last night in order to test the recent updates in hue emulation, but only Items tagged with Lighting are showing up. Anything tagged with Switchable is gone. Also, groups tagged with either are not discovered. I created an issue, but thought I’d check here too, just to make sure it’s not just me!

[Terra]

@Celaeno1

Tag [“Switchable”] is not supported anymore, you have to use tag [ “Lighting” ] instead.

I will try to change it, but the documentation clearly states:

The following default tags are setup:

• “Switchable”: Item will be exposed as an OSRAM SMART+ Plug
• “Lighting”: Item will be exposed as a dimmable white bulb
• “ColorLighting”: Item will be exposed as a color bulb

openHAB Hue Emulation - System Integrations

Also “Switchable” is a default tag in the configuration of the binding in PaperUI?

Switch item tags
“Switchable”
The HUE emulation can either publish Switch items if this is set to an empty string or filter items by tags. You can supply multiple tags by separating them with a comma.

[5iver (Scott Rushworth)]

[“Switchable”] works for some people, but not others. I was waiting for some additional testing, in case a solution could be found, before updating the documentation with using the [“Lighting”] tag as a workaround.

[Terra]

@5iver

[“Switchable”] works for some people, but not others. I was waiting for some additional testing, in case a solution could be found, before updating the documentation with using the [“Lighting”] tag as a workaround.

Ok, so for now I configured in PaperUI that the tags for Switchable items are “SwitchableNotWorking” and the tags for Lighting items are “Lighting,Switchable”.
Then Alexa still could not find any devices. So I deleted all devices from Alexa via the Alexa Website and told Alexa to find new devices. They are all back now in the Smart Home List.

Thanks for the help so far, so it is my understanding that this is a BUG and it’s not like Switchable items are not supported anymore?
It seems still most of the items (power plugs) are not reacting with Alexa, I will try some things and report back…

[sroettgermann (roetka)]

Same problem here… still not working either with Lighting or Switchable.

[David_Graeff]

Please read the breaking changes before updating. It clearly says to remove all devices in Alexa and perform a rediscovery.

Switchables were exposed as lights before the update. That was fixed by exposing them as as Osram ZigBee plugs now. Unfortunately Amazon has a very mixed support for this. Even more unfortunate it worked for me as the developer but for most people it doesn’t. If most firmwares do not support this, I will change the tag for lights to include Switchables.

[KidSquid (The Squid)]

@David_Graeff

What list of breaking changes are you referring to as this list from the release announcement does not show anything about removing all Alexa Devices?

openhab/openhab-distro

[Celaeno1 (Alex)]

@KidSquid

If you had followed this sequence, you maybe could have seen it:

Step1 (=releasenotes of openHAB 2.4.0)

there goto “hueemulation” and then click on Enhancements 4216

Step2 (=Enhancements 4216)

and there goto Fixes #3754 or #3753

Step3 (=Fixes #3754)
Step4 (=Fixes #3753)

There you can read the following:

Steps to Reproduce (for Bugs)

1. Remove all [“Lighting”] tags from items.
2. Add a couple of [“Switchable”] tags to items.
3. Delete all devices from Alexa via webinterface alexa.amazon.com or via Alexa app.
4. Start a scan for devices via alexa.amazon.com or voice command.
5. Devices with the above described names show up, although they are not tagged.

Steps to Reproduce (for Bugs)

1. Disable pairing mode in Hue Emulation.
2. Delete all devices from Alexa via webinterface alexa.amazon.com or via Alexa app.
3. Start a re-scan for devices via alexa.amazon.com or voice command.
4. Newly discovered devices via Hue Emulation show up.

If you never had one of these bugs, then you @KidSquid are right!

And the actual problem is still an “open issue” see here #4293

[David_Graeff]

My fault. It is not in that file, but only in the breaking changes note that is shown while upgrading.

[KidSquid (The Squid)]

I just upgraded from 2.3 to 2.4 and all of my previous working devices now respond with…

“DEVICE XXXX isn’t responding…please check it’s power supply or network connection”

Is this the same issue folks are having in this thread or is this something different?

I have not removed any devices from Alexa or made any changes to the settings.

Thanks,

Squid

[David_Graeff]

@KidSquid

Is this the same issue folks are having in this thread or is this something different?

I have not removed any devices from Alexa or made any changes to the settings.

And you have not read the breaking changes ^^.
The storage system has changed and the hue emulation binding reassigned a new ID to each item. Alexa will use the old item ID (and invalid access key on top). You need to rediscover devices.

[KidSquid (The Squid)]

Ok…must have missed that. my apologies…

Couple of questions before I blow everything to hell.

1. I deleted one item from Alexa and tried to run discovery…she was not able to re-discover the device.
2. I’ve also noticed that discovery mode now turns it’self off - this is new? I used to leave discovery mode on.

My fear is that I’ll leave the house in an unusable status…just want to make sure I can bring back voice control if i need to revert back to 2.3

Thanks,

Squid

[David_Graeff]

@KidSquid

1. I’ve also noticed that discovery mode now turns it’self off - this is new? I used to leave discovery mode on.

Yup, the new code tries to mimic a hue bridge to every detail also this specific one. You can extend the timeout to a ridiculous big number though.

@KidSquid

I deleted one item from Alexa and tried to run discovery…she was not able to re-discover the device.

That also never worked for me. Make sure you follow the instructions in the troubleshoot section if you are having troubles. But in general, it works, I’m using it myself. You might need to use the Switchable,Lighting for the dimable lights tag configuration though. Most Echos don’t understand the currently exposed Osram Plug+.

[bulletprooffool (Alan Fenwick)]

Argh,
Finally upgraded last night and seems I have this too. Have there been any further updates, or will I have to clean up and recreate as per above? Guessing the latter… but living in hope

[David_Graeff]

@bulletprooffool

Finally upgraded last night and seems I have this too.

Another storage mechanism is in use now. Clean up and recreate is unfortunately your only option.

[bulletprooffool (Alan Fenwick)]

Thanks David, I got this working but it has produced 2 problems.

1. after another reboot (when I already had this working again), it seems Alexa tagged all devices as offline - and I had to rediscover again? I wouldn’t want to be doing this every time I do a maintenance reboot?

2. it seems the updates mean that if I issue an off command against an off item again, the command gets ignored? My hue binding binds to some dummy switches. One example is ‘tv’ - when I issues a command to switch tv off, it switches a bunch of other devices off too - some of which may have been powers on manually and connected by infrared bindings - so I can’t track state. Is this a known issue? I have tried to automate loads of legacy gear which is stateless - hue emulation WAS my solution before.

[David_Graeff]

@bulletprooffool

• after another reboot (when I already had this working again), it seems Alexa tagged all devices as offline - and I had to rediscover again? I wouldn’t want to be doing this every time I do a maintenance reboot?

The new storage system that I’m using is the json storage. That interface is also used to store Things and Items that are created via Paper UI etc. But unfortunately it resets after every start and non of the core developers has answered my help request yet. See also https://github.com/openhab/openhab2-addons/issues/4602.

[Terra]

@bulletprooffool

it seems the updates mean that if I issue an off command against an off item again, the command gets ignored? My hue binding binds to some dummy switches. One example is ‘tv’ - when I issues a command to switch tv off, it switches a bunch of other devices off too - some of which may have been powers on manually and connected by infrared bindings - so I can’t track state. Is this a known issue? I have tried to automate loads of legacy gear which is stateless - hue emulation WAS my solution before.

I have the exact same issue, I though I am the only one and it is so annoying.
Similar scenario, I have 3 Scenes:

1. “Home Cinema”: turn on AVR, switch to HDMI1, turn on Projector, turn on PC (WOL)
2. “Android”: turn on AVR, switch to HDMI2, turn on Projector
3. “Nintendo”: turn on AVR, switch to HDMI3, turn on Projector

Before the update it was no problem to trigger an Item Scene to ON when it was already ON, the rules fired again, this does not happen anymore after the update.

Why this is an issue:

1. Someone turns on the scene “Home Cinema”
2. Someone forgets to turn it off and the projector and AVR turn of automatically after 30min inactivity or someone uses the remote and switches manually → the state of the scene “Home Cinema” is still ON
3. Now the status of the item “Home Cinema” in OH is still ON but the devices are actually OFF
4. In the past I could just say “Turn Home Cinema On” and everything would turn on again, this now does not happen anymore as the status is already ON.

I can also not determine during runtime what scene apparently is currently on as some devices do not report the status back properly

[David_Graeff]

@Terra

Before the update it was no problem to trigger an Item Scene to ON when it was already ON, the rules fired again, this does not happen anymore after the update.

Are you on OH 2.5M1? The OH2.4 release was more or less very unfortunate for the hue emulation service and MQTT binding.