No devices found with my alexa after discovering for new devices

[blacktiger333]

I wanted to discover for new devices with my alexa - but no devices were found. I started to discover devices within pimatic and soon afterward with alexa. I also already removed all existing devices within alexa and reinstalled the echo plugin in pimatic. I'm using more than one echo dots 2nd generation (3) and use more raspis - with the other ones everything works fine - but not with this one I use.

Can you see something what's wrong with the log file and config I sent?

pimatic-daemon.log

config.txt

[michbeck100]

Are you using the echo plugin in more than one of the Raspi’s

[blacktiger333]

Yes - is this a problem?

Am 04.01.2018 um 19:51 schrieb Michael Kotten notifications@github.com<mailto:notifications@github.com>:

Are you using the echo plugin in more than one of the Raspi’s

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/michbeck100/pimatic-echo/issues/52#issuecomment-355365969, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVPn3qY5z3NYBWLwA78VWSSMFzIGFHw3ks5tHR2dgaJpZM4RTTOw.

[michbeck100]

I’m not sure. Please start by disabling the other instances.

[blacktiger333]

I disabled all other instances - but it doesn't help, same problem as before. FYI: I also run HA Bridge on this raspi (on port 90) - also tried it after I stopped HA Bridge service, so I assume this should not be the reason. It's quite strange - I don't have any idea why just this raspi doesn't work with your plugin. I need the echo plugin on this raspi because of devices I want to switch with echo....

[michbeck100]

Are you using the echo dot, or the newer echo?

[blacktiger333]

I'm using the echo dot.

[The-Saint2k]

@blacktiger333 put the echo plugin in the config file at the beginning of the section. Like this:

"plugins": [ { "plugin": "echo", "active": true, "debug": true }, ...............

I had the same problem and found this solution in the forum or here on github.

@michbeck100 thank you for your nice plugin

[blacktiger333]

I tried both - disabled all other instances (shut down other raspis) - and did the echo plugin at the beginning of the section, it doesn't help. This is really a strange behavior - I'm the only one with this problem? What I didn't so far is a complete reinstall of my raspi and pimatic - but this is something what I don't want to do now (because all other services are working so far). I join in congratulation of The-Saint2k: @michbeck100 : this is a nice plugin.

[michbeck100]

You wrote

I'm using more than one echo dots 2nd generation (3) and use more raspis - with the other ones everything works fine - but not with this one I use.

Does this mean, that you have the echo plugin working on the other raspis and your echo also discovered the devices from these pimatic instances?

[blacktiger333]

Currently I only use the 2nd raspi with devices for echo. Yes – the second raspi discover all 4 devices I have there – but 2 of them are showing as offline (and cannot be switched with echo) .

Von: Michael Kottenmailto:notifications@github.com Gesendet: Donnerstag, 8. Februar 2018 10:57 An: michbeck100/pimatic-echomailto:pimatic-echo@noreply.github.com Cc: blacktiger333mailto:chris3chris3chris@hotmail.com; Mentionmailto:mention@noreply.github.com Betreff: Re: [michbeck100/pimatic-echo] No devices found with my alexa after discovering for new devices (#52)

You wrote

I'm using more than one echo dots 2nd generation (3) and use more raspis - with the other ones everything works fine - but not with this one I use.

Does this mean, that you have the echo plugin working on the other raspis and your echo also discovered the devices from these pimatic instances?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/michbeck100/pimatic-echo/issues/52#issuecomment-364059831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVPn3h0n2gE1JIJOW4BdPs8pLjUPs2-kks5tSsR-gaJpZM4RTTOw.

[michbeck100]

Really, i have no idea if this can work. I haven't tested with multiple pimatic-echo instances. Even if you switch off all other raspis, you still have the devices stored in the Alexa "memory" in the Amazon cloud. Maybe you have to remove all these devices first, and then try again. And even if it works then, you have the same problem again with your other raspi that was working before. I guess that each pimatic-echo instance needs some unique identifier. But currently i have no idea what this could be. I you like you can play around with some values in hue.coffee starting from here: https://github.com/michbeck100/pimatic-echo/blob/master/lib/hue.coffee#L290

[michbeck100]

Is this still an issue?

[michbeck100]

I'm closing this issue for now. Feel free to reopen if the issue still exists