[hueemulation] Some Alexa devices do not discover all tags #4293

5iver · 2018-11-29T11:32:44Z

I updated from 1415 to 1445, excited to test #4216, and lost control of most of my items. None of my Items tagged as Switchable are being discovered. Sorry if this is not enough information, but I'm guessing this should be easily reproducible. If any more detail is required, please let me know. I am in the US and use 2nd gen Dots. This is also being reported outside the US.

community discussion

gdgeist · 2018-11-30T11:56:32Z

build 1446 and same experience. Items tagged with "Switchable" not discovered. "ColorLight" discovered as a light but Alexa marks it as a Color Capabilities = None. All items show up in API.

Example of the color light from API:

{"state":{"hue":8373,"sat":139,"xy":[0.0,0.0],"alert":"none","effect":"none","transitiontime":0,"colormode":"ct","bri":254,"ct":500,"on":true,"reachable":true},"type":"Extended color light","modelid":"LCT010","uniqueid":"8790e48e-7152-4795-9b5b-39ec9620fdc8-66","manufacturername":"Philips","swversion":"1.15.2_r19181","swconfigid":"F921C859","productid":"Philips-LCT010-1-A19ECLv4","friendsOfHue":true,"colorGamut":"C","hascolor":true,"name":"Kitchen Desk Lamp Color"}

Example Switchable Item:

{"state":{"on":true,"reachable":true},"type":"On/Off plug-in unit","modelid":"Plug 01","uniqueid":"8790e48e-7152-4795-9b5b-39ec9620fdc8-52","manufacturername":"OSRAM","swversion":"66012040","friendsOfHue":true,"hascolor":false,"name":"Kitchen Sink Lamp"}

Also Null pointer exceptions for items that are not reachable during Alexa discovery (Hue bulbs exposed through the hue emulation)
Example:
2018-11-30 06:09:14.626 [WARN ] [org.eclipse.jetty.server.HttpChannel] - /api/ji2WsId63e9X33ub4QqCgguJZkxSUVDMDa2N1LVA/lights/33

java.lang.NullPointerException: nullNo tagged groups

davidgraeff · 2018-11-30T13:21:20Z

Alexa marks it as a Color Capabilities = None

Alexa does not natively (within the local network) support coloured hue bulbs. This is only possible via skills unfortunately. Try with hue compatible apps and it should be presented as a coloured bulb.

Switchable Item

It works with my alexa (German firmware, which usually lacks behind the US version).
It may help to fake another device and not the OSRAM plug for a broader compatibility.

Null pointer exceptions

That should not happen. What do you mean by "item that is not reachable"? An item does not have a reachable state. Did I miss something?

gdgeist · 2018-11-30T23:58:40Z

Thanks. The null pointer exceptions are for real world hue bulbs things that are "unreachable" i.e. hue bulb switched off by a hard wired light switch.

dainosan · 2018-12-01T08:55:06Z

BUILD 1446 I have similar issues. reduced to 1 THING, 1 ITEM and still not being discoverable by the 3rd Gen echo Dot.

ITEM:
Switch Luce_disimpegno_bagno "Disimpegno Bagno" (gLivingRoom) ["Lighing"] { channel="openwebnet:bus_on_off_switch:mybridge:Luce_disimpegno_bagno:switch" }

rest API :
[{"link":"http://192.168.1.22/rest/items/Luce_disimpegno_bagno","state":"OFF","editable":false,"type":"Switch","name":"Luce_disimpegno_bagno","label":"Disimpegno Bagno","category":"light","tags":["Lighing"],"groupNames":["gLivingRoom"]}]

dainosan · 2018-12-01T09:38:09Z

this could help (or not)but i noticed that every time i change the configuration in paperUI
the config file

/var/lib/openhab2/config/org/openhab/hueemulation.config

contains a "B" in the string

pairingEnabled=B"true"

davidgraeff · 2018-12-01T10:24:39Z

That is correct behaviour @dainosan. If you enable pairing mode a "boolean" value "true" is stored in the configuration and about 60 seconds later this is overwritten with a "false" value again.

dainosan · 2018-12-01T10:26:12Z

thanks. whatever it is the discovery is not working. i am trying to debug but i cannot see anything that could be going wrong but when the discovery completes there are no devices

davidgraeff · 2018-12-01T10:34:39Z

You can use a REST addon for your favourite browser and verify that the xmls generated by the hue emulation are correct. Alexa is also picky about the port nowadays, openhab should be running on port 80, or a reverse proxy forwards traffic from :80 to :8080.

With the rest plugin in your browser you do a GET request on http://your-openhab:80/api/config as a start and http://your-openhab:80/description.xml while discovery is enabled.

dainosan · 2018-12-01T10:50:42Z

aware of the port forwarding and that is in place. 80 to 8080 via Iptables.

i get data back from both :
http://192.168.1.22/api/config
AND
http://192.168.1.22/api/description.xml

gdgeist · 2018-12-01T12:46:31Z

BUILD 1446 I have similar issues. reduced to 1 THING, 1 ITEM and still not being discoverable by the 3rd Gen echo Dot.

ITEM:
Switch Luce_disimpegno_bagno "Disimpegno Bagno" (gLivingRoom) ["Lighing"] { channel="openwebnet:bus_on_off_switch:mybridge:Luce_disimpegno_bagno:switch" }

rest API :
[{"link":"http://192.168.1.22/rest/items/Luce_disimpegno_bagno","state":"OFF","editable":false,"type":"Switch","name":"Luce_disimpegno_bagno","label":"Disimpegno Bagno","category":"light","tags":["Lighing"],"groupNames":["gLivingRoom"]}]

@dainosan Lighting is mispelled.

dainosan · 2018-12-01T12:56:32Z

no that was probably one of the latest copy and paste. this is how the item appears in rest API

[{"link":"http://192.168.1.22/rest/items/Luce_disimpegno_bagno","state":"NULL","editable":false,"type":"Switch","name":"Luce_disimpegno_bagno","label":"Disimpegno Bagno","tags":["Lighting"],"groupNames":["gLivingRoom"]}]

gdgeist · 2018-12-01T13:11:37Z

@dainosan I was hoping it was an easy fix for you ;)

gdgeist · 2018-12-01T13:38:45Z

Alexa marks it as a Color Capabilities = None

Alexa does not natively (within the local network) support coloured hue bulbs. This is only possible via skills unfortunately. Try with hue compatible apps and it should be presented as a coloured bulb.

@davidgraeff This one stumps me as I have a Hue hub and have never used the Hue cloud account i.e. Alexa/Echo has only ever been connected locally and before I deleted the pairing in order to use the hue emulation the color bulb worked just fine i.e. the only way Alexa would have discovered my color bulb was local discovery....

davidgraeff · 2018-12-01T13:51:34Z

@gdgeist Maybe in non European firmware versions? I read about non color support in various forums and that Amazon is never intending to add support to the local hue support. The hue emulation is emulating a A14 extended color bulb from 2014, I think. My alexa is not recognising it as color bulb (eg "change color to red"). If anybody knows what to emulate to make this work, I'd happy to make the necessary changes.

davidgraeff · 2018-12-01T13:53:54Z

no that was probably one of the latest copy and paste. this is how the item appears in rest API

It doesn't help to post the OH rest response. Alexa is using the hue emulation rest API under /api. You need to generate an api-key and then post the contents of /api/[api-key]/lights. I have no time to explain the details, please google that up, please.

dainosan · 2018-12-01T14:15:47Z

we can figure this out.

here is the long output of the /api/[api-key]/lights

api key is created but nothing is returned to alexa

ScottKinSF · 2018-12-02T17:32:23Z

I too have existing rules and items that use group items to control dimmer items in the same area. As noted by @5iver, the updated version of Hue Emulation breaks that functionality.

I have also noted that the commands ON and OFF when issued from Alexa to my dimmer items, no longer function the way they did before this update. The devices now receive a '1' or a '0' respectively, which my devices see as 1% and 0%, which is certainly not the desired behavior. Setting these dimmer items to a percentage value from 0 to 100% does work. <-- I determined that this behavior is unrelated to the HueEmulation binding.

davidgraeff · 2018-12-03T10:18:47Z

Please everyone test if switchables work for you with #4312 and #4313 applied. Please also perform the test with different Alexas (voice command in English might be something like: Alexa, discover new devices). I have the strong feeling that different Echo types support different sets of hue devices.

gdgeist · 2018-12-05T03:47:11Z

2.4.0.201812042313 │ Hue Emulation Service

No devices discoverable at all. I cleared the discovered devices in Alexa. Cleared cache, upgraded, device pairing mode multiple times.

Ran out of time tonight. Will see if anything useful can come from the logs

davidgraeff · 2018-12-05T09:13:57Z

One of the commits made the main api endpoint (/api/user-name/lights) a 404. Therefore the hue emulation development version does not work. I'm on this right now.

davidgraeff · 2018-12-05T19:39:26Z

I have created PR #4324 to fix this and added a test bundle as well for catching breaking commits next time.

For Alexas that are not able to identify an OSRAM plug as a switchable, I have this workaround:

Go to the service configuration on Paper UI and change the tag for white lights to "Lighting, Switchable". This emulates all switchables as white lights, like the former code did.

davidgraeff · 2018-12-08T19:37:40Z

This is a screenshot from the Alexa app. You see devices appear two times. The echo dot finds them as "Royal Philips Electronics intelligentes Gerät" including switches. The echo finds them as as "Dimmable Light" and "Color Light" without switches. Summing this up: The local hue support is a mess, somehow.

…, group items Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de>

…, group items Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de>

…, group items Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. * Add REST API POST support on /api/{username}/groups. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de>

…, group items (#4339) Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. * Add REST API POST support on /api/{username}/groups. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes #4293 Fixes #4307 Signed-off-by: David Graeff <david.graeff@web.de>

davidgraeff · 2018-12-20T15:45:41Z

Amazon is not officially supporting Hue bridges locally, are they?

cee-dee · 2018-12-20T16:07:05Z

I've checked discovery with all of my Echo devices: The large Amazon Echo discovers only those devices which are directly exposed through the Hue Bridge, all other Echo Dots discover all devices, including those exposed by openHAB. The web version via alexa.amazon.com discovers all devices, too. (Tests have been performed using the tags "Lighting,Switchable" configured in the binding.

davidgraeff · 2018-12-20T16:18:38Z

Tests have been performed using the tags "Lighting,Switchable" configured in the binding.

Can you assign "Lighting" to the Coloured bulb and test if coloured bulbs are supported by your Echos?
And test "Switchable" as well with the different Echos, that would help.

5iver · 2018-12-20T16:29:10Z

Amazon is not officially supporting Hue bridges locally, are they?

Yes, without a skill, which is how hueemulation is possible. And also why it is so handy, because you do not need a command word to use it, like when using a skill.

Here is an Amazon support article on it. There is also note in the Hue Skill that alludes to this.

I just reread you post, and don't think I answered your question (probably info you are very wel aware of 🙄 ). I don't think Alexa does anything locally yet.

cee-dee · 2018-12-20T16:49:26Z

@davidgraeff : Can you elaborate on the exact scenario which I shall test? I assume you want this:
a) remove the configuration "Switchable" from the white tags setting
b) editing one my items-file to assign the tag "Lighting" to a single light
c) re-discover the items with web service, Echo and Echo Dot separately
d) verify if the adjusted item is discovered with a certain tag

Is this basically what you want? If so, which tags should be reported?

I don't have a clue what I should test regarding Switchable, since step a) will cause the items to be not discovered.

davidgraeff · 2018-12-20T17:00:16Z

@cee-dee Exactly. I like to know if any/some devices of your setup support colors and switches and with what label the discovered devices are reported. The label differs for me depending on the discovery-performing device.

@openhab-5iver Regarding to the Amazon document

Philips Hue devices can connect to Alexa with the V1 Hue Bridge (circle-shaped). To connect these devices, say, "Discover devices," and then press the button on the bridge.

I'm emulating a 2nd gen bridge and it works for me and for you.

Note: Your Echo device can only be associated with one Phillips Hue bridge at a time.

I have two emulated bridges and both are recognised. But maybe they mean, that each Echo can associate to one bridge.

Phillips Hue devices with the V1 Hue Bridge can only turn on/off or brighten lights on compatible Echo devices.

Color and switches are working for me. But that document might be for the US market of course. In the German help center there is no such document at all.

All in all I think this is a relict and nobody noticed that the document is outdated by now. It would be really good to know where Amazon is heading to and what their plans are for local protocols.

5iver · 2018-12-20T18:00:25Z

I'm emulating a 2nd gen bridge and it works for me and for you.

That stands out to me. It was my understanding that a v2 bridge required the Hue skill to work with Alexa. Is this just a configuration setting (like firmware version), or would changes be needed in the API calls to emulate a v1? I ask, because I could try making the changes and testing it out to see if this helps at all.

ScottKinSF · 2018-12-20T19:12:50Z

5iver, the following statement from the 2nd link you provided above contradicts the statement from your 1st link about Alexa local control only being available for Philips Hue V1 bridges:

Note: Basic lighting functionality (on / off / dimming) is available without the Smarthome skill and is compatible with Philips Hue V1 (round) and V2 (square) bridges.

I think David is right, the information in the 1st link is out-of-date.

5iver · 2018-12-20T19:30:45Z

the following statement from the 2nd link you provided above contradicts the statement from your 1st link

I guess I can see that, but I was taking it to mean that this functionality is only available/compatible with a v1 bridge. But this is must be outdated (or incorrect), if hueemulation is emulating a v2 bridge.

I called Alexa support and they said that the Hue skill is required to discover devices on the v2 Hue bridge, but the skill is not required for the v1 bridge. 😕

davidgraeff · 2018-12-21T00:10:28Z

The Alexa support team is required to say whatever the company policy is. And if the tech team is slowly starting to fade out local protocol support, the support will always tell you to use the skill of course.

We need to find out what still works. I have already learned to add a section to the readme telling people to try all different Alexa devices to perform discovery and to add all tags to the dimmable bulb if color and plugs are not recognized.

ScottKinSF · 2018-12-21T20:58:56Z

Update on the SYLVANIA SMART+ Smart Plug:

I received the device this afternoon and have tried numerous times to pair it with my Hue Hub V1 without success. It appears to use a ZigBee HA 1.2 profile rather than the ZLL profile required for compatibility with a Hue Hub.

I would still like to hear from anyone in the US who has one of the older SYLVANIA Lightify versions of this device paired with their Hue Hub. I think I will post an inquiry on one of the Hue Developers forums.

gdgeist · 2018-12-23T13:13:28Z

So trying to understand where I could instrument this in order to cure my ColorLight issue and this Switchable thing.
The discovery exchange questions i have:

Initiate discovery from web/app/device
Since there isn't a "skill" involved - discovery must ask the Hue hub for a current list of devices.
2a. web/app initiated:do all devices devices ask the known hue bridge for the list or is one chosen randomly, ranked?
2b. device initiated: does it still call amazon and ask for the hue token/url for the action or does it have this stored locally?

Answers here would help me understand where to start sniffing the exchange.

davidgraeff · 2018-12-23T14:04:59Z

2a. web/app initiated:do all devices devices ask the known hue bridge for the list or is one chosen randomly, ranked?

One random device.

2b. device initiated: does it still call amazon

An Echo stores its Hue bridge API key locally. It is not stored anywhere at Amazon. Each Echo creates its own Api Key. That's why you usually need to put your bridge into pairing mode if you have multiple Echos even if you have performed a discovery before. A random Echo that does not have an API key yet, could be chosen to perform the request to the Hue bridge.

…, group items (openhab#4339) Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. * Add REST API POST support on /api/{username}/groups. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de>

Jitterer · 2018-12-28T16:54:20Z

Same issue here for another german person. I'm running different echo dot v2 and v3. Workaround with hue emulation config does work, but only for switchs. I couldnt manage my roller shutter to work with percentages like "alexa, open roller shutter 60%"... that's very disappointing that such changes got implemented in stable releases :/

…, group items (openhab#4339) Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. * Add REST API POST support on /api/{username}/groups. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de> Signed-off-by: Pascal Larin <plarin@gmail.com>

VitoDeCarlo · 2019-01-16T06:11:17Z

I'm also unable to use Alexa to control the color of my lights (here in the U.S.). I cannot use a direct connection between Alexa and Hue, as I need Alexa to control my Z-Wave devices as well (and I use Google Home to control my Hue lights, also). So this puts me in the situation of not being able to control the color with Alexa for my 60 or so Hue lights on two Hue bridges. Of of my Alexa devices are the Echo Dot v2.

davidgraeff · 2019-01-16T06:43:21Z

Google Home supports local Hue bridges (and hue emulation therefore) as well. Was a bit more tricky if I remember correctly, they also prefer the cloud connection of course.

There is nothing we can do if Amazon is not supporting certain features like color on all their devices.

ersingencturk · 2019-01-22T23:09:57Z

I'm using misc-hueemulation - 2.4.0

item defined as:

Rollershutter LivingRoom_Shutter3 "Kitchen Curtain" <rollershutter>(LivingRoom, gShutter) ["Switchable"] { channel="knx:device:bridge:generic:LivingRoom_Shutter3" }

But It's not visible in http://192.168.1.100/api/discovery hence alexa not finding it.

Is there a workaround ?

davidgraeff · 2019-01-22T23:19:44Z

Yes. Using OH 2.5M1 :)

ersingencturk · 2019-01-22T23:26:29Z

Yes. Using OH 2.5M1 :)

fair enough :) is it possible to just enable this add on for 2.5M1 ? or have to change the whole setup ?

davidgraeff · 2019-01-22T23:30:32Z

There is not much that happened from OH2.4 to OH2.5M1. It is relatively safe to just upgrade.

But you can always just download the "Milestone Add-ons" offline bundle and extract the kar file (it's a normal zip file) and and put the correct .jar file into your addons directory. Up to you.

Jitterer · 2019-01-22T23:32:14Z

Workaround is to setup the item as dimmer instead of rollershutter

ersingencturk · 2019-01-22T23:46:44Z

thanks for your fast responses.will try both

davidgraeff · 2019-02-09T16:10:36Z

Closing, because we have no control over Amazon and their Echo support for local Hue bridges.

5iver · 2019-02-09T23:16:40Z

For completeness, Amazon claims to only support V1 Hue hubs without a skill. This service was "upgraded" to emulate a V2 hub, but the features that were added are unusable. Previously, the Switchable and Lighting tags did the same thing. That was changed, and the Switchable tag no longer works. ColorLight will turn on/off the light, but color and temperature cannot be changed. Currently, only the Lighting tag works properly.

…, group items (openhab#4339) Fixes: * Fix user creation without a proposed username in the request. Incl. test * Fix: The hue value was wrongly applied to the saturation field. Incl. test * Fix usage of StorageService: Set the classloader * Set the saturation to 0 if a ct (color temperature) value is set. This is because Alexa only sets "ct" if you command her to turn the light white. * Only call writeToFile in LightItems once, after all items have been loaded up from the registry. * Don't load items twice from the registry. * Reload items whenever the tags configuration has changed. * Allow group items Features: * Add troubleshoot section to readme. Allow a pretty printed output for /api/{username}/lights?debug=true. * Add REST API POST support on /api/{username}/groups. Tests: * Add LightItems class unit tests for adding/updating items and group items by category and tags. * Add tests for setting the hue and saturation and turn a light from color to white Refactor: * Move UserAuth class out of DataStore into own HueUserAuth class Fixes openhab#4293 Fixes openhab#4307 Signed-off-by: David Graeff <david.graeff@web.de> Signed-off-by: Maximilian Hess <mail@ne0h.de>

5iver mentioned this issue Dec 2, 2018

[HueEmulation] Support Coloured bulbs & other improvements #4216

Merged

davidgraeff mentioned this issue Dec 9, 2018

Hue emulation: Fixes (user creation, storage service, turn light white) #4339

Merged

kaikreuzer closed this as completed in #4339 Dec 9, 2018

davidgraeff added the won't fix Invalid Issues and requests that do not fit the specified add-on label Feb 9, 2019

davidgraeff closed this as completed Feb 9, 2019

[hueemulation] Some Alexa devices do not discover all tags #4293

[hueemulation] Some Alexa devices do not discover all tags #4293

Comments

5iver commented Nov 29, 2018 • edited Loading

gdgeist commented Nov 30, 2018 • edited Loading

davidgraeff commented Nov 30, 2018 • edited Loading

gdgeist commented Nov 30, 2018

dainosan commented Dec 1, 2018

dainosan commented Dec 1, 2018

davidgraeff commented Dec 1, 2018

dainosan commented Dec 1, 2018

davidgraeff commented Dec 1, 2018 • edited Loading

dainosan commented Dec 1, 2018

gdgeist commented Dec 1, 2018 • edited Loading

dainosan commented Dec 1, 2018

gdgeist commented Dec 1, 2018

gdgeist commented Dec 1, 2018

davidgraeff commented Dec 1, 2018 • edited Loading

davidgraeff commented Dec 1, 2018 • edited Loading

dainosan commented Dec 1, 2018

ScottKinSF commented Dec 2, 2018 • edited Loading

davidgraeff commented Dec 3, 2018

gdgeist commented Dec 5, 2018

davidgraeff commented Dec 5, 2018 • edited Loading

davidgraeff commented Dec 5, 2018

davidgraeff commented Dec 8, 2018

davidgraeff commented Dec 20, 2018

cee-dee commented Dec 20, 2018

davidgraeff commented Dec 20, 2018

5iver commented Dec 20, 2018 • edited Loading

cee-dee commented Dec 20, 2018

davidgraeff commented Dec 20, 2018 • edited Loading

5iver commented Dec 20, 2018

ScottKinSF commented Dec 20, 2018

5iver commented Dec 20, 2018 • edited Loading

davidgraeff commented Dec 21, 2018 • edited Loading

ScottKinSF commented Dec 21, 2018

gdgeist commented Dec 23, 2018

davidgraeff commented Dec 23, 2018

Jitterer commented Dec 28, 2018

VitoDeCarlo commented Jan 16, 2019

davidgraeff commented Jan 16, 2019

ersingencturk commented Jan 22, 2019

davidgraeff commented Jan 22, 2019

ersingencturk commented Jan 22, 2019

davidgraeff commented Jan 22, 2019

Jitterer commented Jan 22, 2019

ersingencturk commented Jan 22, 2019

davidgraeff commented Feb 9, 2019

5iver commented Feb 9, 2019

5iver commented Nov 29, 2018 •

edited

Loading

gdgeist commented Nov 30, 2018 •

edited

Loading

davidgraeff commented Nov 30, 2018 •

edited

Loading

davidgraeff commented Dec 1, 2018 •

edited

Loading

gdgeist commented Dec 1, 2018 •

edited

Loading

davidgraeff commented Dec 1, 2018 •

edited

Loading

davidgraeff commented Dec 1, 2018 •

edited

Loading

ScottKinSF commented Dec 2, 2018 •

edited

Loading

davidgraeff commented Dec 5, 2018 •

edited

Loading

5iver commented Dec 20, 2018 •

edited

Loading

davidgraeff commented Dec 20, 2018 •

edited

Loading

5iver commented Dec 20, 2018 •

edited

Loading

davidgraeff commented Dec 21, 2018 •

edited

Loading