pimatic-echo@0.5.4

---

Just released a new version of pimatic-echo.

Changelog:

• #67 Default port for hue emulator is 80 again, also some changes to the upnp device discovery

This relates to https://github.com/bwssytems/ha-bridge/issues/1133.

After the update please make sure to remove all previous devices from alexa.amazon.com. The new devices will be of type Royal Phillips Electronics intelligent device. If you still find devices of type dimmable light, make sure they get removed. You might have to remove every single device by its own. The “Remove all” button doesn’t seem to work properly sometimes.

Hi all,

I’ve been reading a lot here and there and I didn’t find any solution to my problems with pimatic-echo. I have the feeling that it is a stupid issue but I’m going nuts and I’m a little desperate. I’ll try to provide as much information as I can.

I’m having issues getting my echo finding the devices in my pimatic.

The Raspi running pimatic is connected to the network through both Ethernet and Wifi. Ethernet has the IP 192.168.0.x while wifi has IP 192.168.86.x.

Echo is connected through WIFI with an IP 192.168.86.y.

By the way, I can access to 192.168.0.x:80 from a cellphone connected to the same wifi (i.e. with an IP 192.168.86.xx).

I’ve tried with another raspi I have connected to the wifi (192.168.86.z) and pimatic-echo is working well there (Alexa is finding the devices). Therefore I assume it should be a silly thing setting up my network, but I couldn’t find the issue.

So far I’ve tried:

• Disconnecting the raspberry from either ethernet or wifi
• Setting echo plugin configuration to IP 192.168.86.x
• Setting echo plugin configuration to IP 192.168.0.x
• Setting port forwarding for port 80 in the wifi node to 192.168.86.x
• Changing the port in the echo plugin configuration to 1900

Just a note, I’ve rebooted pimatic after any change in the plugin. Of course I’m hitting on “discover devices” while Alexa is searching.

Please find also below the log of one of the tries (I don’t remember which one) just in case it can provide any clue:

21:21:33.731 [pimatic-tuya] debug: Turned off
21:21:35.811 [pimatic-echo] debug: << server got: M-SEARCH * HTTP/1.1
21:21:35.811 [pimatic-echo] debug:>HOST: 239.255.255.250:1900
21:21:35.811 [pimatic-echo] debug:>MAN: "ssdp:discover"
21:21:35.811 [pimatic-echo] debug:>ST: upnp:rootdevice
21:21:35.811 [pimatic-echo] debug:>MX: 5
21:21:35.811 [pimatic-echo] debug:>
21:21:35.811 [pimatic-echo] debug:> from 192.168.0.4:33533
21:21:35.813 [pimatic-echo] debug: complete sending all responses.
21:21:36.465 [pimatic-echo] debug: >> sent response ssdp discovery response: HTTP/1.1 200 OK
21:21:36.465 [pimatic-echo] debug:>HOST: 239.255.255.250:1900
21:21:36.465 [pimatic-echo] debug:>CACHE-CONTROL: max-age=100
21:21:36.465 [pimatic-echo] debug:>EXT:
21:21:36.465 [pimatic-echo] debug:>LOCATION: http://192.168.0.4:80/description.xml
21:21:36.465 [pimatic-echo] debug:>SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
21:21:36.465 [pimatic-echo] debug:>hue-bridgeid: XXXXXXXXXXXX
21:21:36.465 [pimatic-echo] debug:>ST: upnp:rootdevice
21:21:36.465 [pimatic-echo] debug:>USN: uuid:XXXXXXXXXXXX::upnp:rootdevice
21:21:36.465 [pimatic-echo] debug:>
21:21:36.465 [pimatic-echo] debug:>
21:21:36.468 [pimatic-echo] debug: >> sent response ssdp discovery response: HTTP/1.1 200 OK
21:21:36.468 [pimatic-echo] debug:>HOST: 239.255.255.250:1900
21:21:36.468 [pimatic-echo] debug:>CACHE-CONTROL: max-age=100
21:21:36.468 [pimatic-echo] debug:>EXT:
21:21:36.468 [pimatic-echo] debug:>LOCATION: http://192.168.0.4:80/description.xml
21:21:36.468 [pimatic-echo] debug:>SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
21:21:36.468 [pimatic-echo] debug:>hue-bridgeid: XXXXXXXX
21:21:36.468 [pimatic-echo] debug:>ST: uuid:XXXXXXX
21:21:36.468 [pimatic-echo] debug:>USN: uuid:XXXXXXXX
21:21:36.468 [pimatic-echo] debug:>
21:21:36.468 [pimatic-echo] debug:>
21:21:36.470 [pimatic-echo] debug: >> sent response ssdp discovery response: HTTP/1.1 200 OK
21:21:36.470 [pimatic-echo] debug:>HOST: 239.255.255.250:1900
21:21:36.470 [pimatic-echo] debug:>CACHE-CONTROL: max-age=100
21:21:36.470 [pimatic-echo] debug:>EXT:
21:21:36.470 [pimatic-echo] debug:>LOCATION: http://192.168.0.4:80/description.xml
21:21:36.470 [pimatic-echo] debug:>SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
21:21:36.470 [pimatic-echo] debug:>hue-bridgeid: XXXXXXXXXXX
21:21:36.470 [pimatic-echo] debug:>ST: urn:schemas-upnp-org:device:basic:1
21:21:36.470 [pimatic-echo] debug:>USN: uuid:XXXXXXXXXXX
21:21:36.470 [pimatic-echo] debug:>
21:21:36.470 [pimatic-echo] debug:>

Any idea?

Thank you in advance for your help!

@jorge-martínez If you enabled debug logging, you should see which IP address is used. On pimatic startup there should be a line saying Using ip address: <address>. Please see which one is used. pimatic-echo uses the first non-loopback IPv4 interface by default. This can be overridden in the config by setting the properties address and mac. See plugin options here https://pimatic.org/plugins/pimatic-echo/

Hi! Thanks for the quick reply.

I confirm it is listening to either 192.168.0.x or 192.168.86.x (depending on what I set up), but in none of these options Alexa is finding the devices.

I’ve tried a couple of days ago setting with the MAC address too, with no success.

@jorge-martínez Did you try to completely disable the wifi, so there is just one ethernet device?

Tried and nothing…

@jorge-martínez since you have a rather strange network setup, you should make sure that the raspberry pi ist in the same subnet as the echoes. So for wifi this would be 192.168.86.x. And pimatic-echo must use the correct ip address and mac address. Since you tried another raspberry with a standard network configuration, which works, I can’t really help you.
Why are you having two different networks anyway?

Well, to be honest there should be no need of having two networks, but I’m using Google Wifi devices and they do it by default. Since it has been working always with no problem I have not dedicated time to change it.

I had an epiphany and I finally managed to solve the issue.

Basically I disconnected the ethernet cable and reboot completely the raspberry (maybe something was stuck in the routing tables latest time I disconnected the cable). Then I could finally find the devices.

Then after connecting the cable I had to ensure to force echo plugin to use the Wifi IP and MAC (with IP only it didn’t work). And so far, everything is working!

Thanks @michbeck100 for your help. Without it, I think I wouldn’t have tried again several networking configurations.