Alexa findet Phoscon nicht

General
1

Hallo, bei mir läuft auf Docker eine Instanz von Deconz auf dem ioBroker.
Ich versuche vergeblich das System mit Alexa zu verbinden…
( Gateway/Erweitert/App Verbinden) → Alexa sucht und findet nichts…
Hat wer einen Tipp für mich?

2

Hi,

Please translate your post to English as we are an English community.

Kind regards,
Dennis

3

Sorry, here are in English :smiling_face: :smiling_face:

Hello, I have an instance of Deconz running on Docker on the ioBroker.
I’m trying in vain to connect the system to Alexa…
(Gateway/Advanced/App Connect) → Alexa searches and finds nothing…
Does anyone have a tip for me?

4

Hello!

I have a similar issue, however my Alexa finds the deconz (it’s named “Configuration Tool 1”) and some new lights, but then I can’t control them. Alexa tells me Server is unreachable.
Parallel I checked registered apps with Hue Essentials and but there is no Echo.

Do you have both devices on same Network? Deconz running on Port 80? You can try and test to connect Hue Essentials App.
You may also have a look at Alexa does not detect Conbee gateway · Issue #112 · dresden-elektronik/phoscon-app-beta · GitHub or Gateway not discovered by Alexa · Issue #759 · dresden-elektronik/deconz-rest-plugin · GitHub

5

Hallo Tscheurgen,

thx for your answer.
Yeah, both devices are in the same network. Ports 80 & 8080 are published.

I tried the Hue Essentials App → there was finding some Tasmotas but no Alexa…

6

My intention was to test if you can connect essentials App with Deconz, there you can see all registered Apps on the gateway.

Which Echo device do you use?
I’ve now turned of my Echo Dots Gen 3,4,5 and with my left over Echo Show I can’t find anything.
Maybe someone else can give us a hint.
http:///description.xml is looking good to me.

7

Hallo,

i use different Echo´s ( 1x Studio, 2xEcho Plus, 1x Show)…

8

While investigating further I’ve found this link which seems to be my issue as well

In deconz HTTP Log I see several unauthorized requests from echo devices, but I didn’t manage to authenticate them and receive the API key for them

9

After seeing my Echo devices use API keys which aren’t registered in the deCONZ db, is it a possible solution and good idea to add the API keys manually in the zll.db Database?
May I corrupt the database when adding manually a line?
Can someone give me a hint?
Thank you all!

10

Can you show the “unauthorized requests” ? They happen during the autenticate procedure ? If I m right you have a special flag to see http request on logs.
From my memory Hue bridge need a “special type of requests” it’s the API mode, visible on logs

            if ((!(i->useragent.isEmpty()) && i->useragent.startsWith(QLatin1String("iConnect"))) || i->devicetype.startsWith(QLatin1String("iConnectHue")))
            {
                req.mode = ApiModeStrict;
            }
            else if (i->devicetype.startsWith(QLatin1String("Echo")))
            {
                req.mode = ApiModeEcho;
            }
            else if (i->devicetype.startsWith(QLatin1String("Hue Essentials")))
            {
                // supports deCONZ specifics
            }
            else if (i->devicetype.startsWith(QLatin1String("hue_")) ||
                     i->devicetype.startsWith(QLatin1String("Hue ")) ||
                     gwHueMode)
            {
                req.mode = ApiModeHue;
            }
            DBG_Printf(DBG_HTTP, "ApiMode: %d\n", req.mode);

The last time I have see this issue, deconz just stop to use the “ApiModeHue”, because it don’t reconise the Hue Gateway.

But there is no reason for the Hue gateway was not able to get a valid API key, for me it’s more a “recognition” issue.

11

I’m sorry, I’ve missed your comment recently. How is hue bridge included in this process?
In deconz GUI in HTTP Log I see these lines when unauthorized

22:46:49:535 HTTP API GET /api/1363F1A101/lights/14 - 10.100.13.118
22:46:49:536 	host: 10.100.13.118
22:46:49:536 [{"error":{"address":"/lights/14","description":"unauthorized user","type":1}}]

So I opened the zll.db Database and added the API key manually there and see it can get light properties. I used Echo as devicetype so ApiMode is 2.

22:50:31:408 HTTP API GET /api/1363F1A101/lights/2 - 10.100.13.118
22:50:31:409 ApiMode: 2

So I can control existing lights with Alexa, but I don’t find new ones. So I’m still missing something.
From which file is your code from? Am I still missing something?

12

Also with conbee II I’m not lucky to connect alexa with it. This is quite weird and I don’t know where to check further.

13 
enum ApiMode
{
    ApiModeNormal,
    ApiModeStrict,
    ApiModeEcho,
    ApiModeHue
};

So from the code, you are in mode “ApiModeEcho” (=2) but honnestly I don’t remember the differences.