Devices not found - Or no MQTT msg was send

[thommycgn]

Hi!

The device is listening on Port 39900. If I search for devices with alexa: no devices found.

Any Ideas?

Here what netstat says:

---

pi@raspberrypi:~/.node-red $ netstat -l Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 :36519 : LISTEN
tcp 0 0 :5001 : LISTEN
tcp 0 0 :ssh : LISTEN
tcp 0 0 :1880 : LISTEN
tcp 0 0 :1883 : LISTEN
tcp6 0 0 [::]:4050 [::]: LISTEN
tcp6 0 0 [::]:51826 [::]: LISTEN
tcp6 0 0 [::]:ssh [::]: LISTEN
tcp6 0 0 [::]:33339 [::]: LISTEN
tcp6 0 0 [::]:1883 [::]: LISTEN
tcp6 0 0 [::]:39900 [::]: LISTEN
udp 0 0 :bootpc :
udp 0 0 raspberrypi.fritz.b:ntp :
udp 0 0 localhost:ntp :
udp 0 0 :ntp :
udp 0 0 :mdns :
udp 0 0 :50486 :
udp 0 0 :1900 :
udp6 0 0 [::]:dhcpv6-client [::]:
udp6 0 0 [::]:42547 [::]:
udp6 0 0 raspberrypi.fritz.b:ntp [::]:
udp6 0 0 fe80::2d41:bb55:1b8:ntp [::]:
udp6 0 0 localhost:ntp [::]:
udp6 0 0 [::]:ntp [::]:
udp6 0 0 [::]:mdns [::]:
raw6 0 0 [::]:ipv6-icmp [::]: 7
Aktive Sockets in der UNIX-Domäne (Nur Server) Proto RefCnt Flags Type State I-Node Pfad unix 2 [ ACC ] STREAM HÖRT 11298 @/tmp/dbus-2ueJkNwkq9 unix 2 [ ACC ] STREAM HÖRT 11267 /tmp/.X11-unix/X0 unix 2 [ ACC ] STREAM HÖRT 9959 /tmp/ssh-lZpzGv7fLPOL/agent.724 unix 2 [ ACC ] STREAM HÖRT 11611 /tmp/ssh-IRCIA5ghuP98/agent.1271 unix 2 [ ACC ] STREAM HÖRT 12683 /tmp/.pcmanfm-socket--0-pi unix 2 [ ACC ] STREAM HÖRT 11266 @/tmp/.X11-unix/X0 unix 2 [ ACC ] STREAM HÖRT 5179 /run/systemd/private unix 2 [ ACC ] SEQPAKET HÖRT 5201 /run/udev/control unix 2 [ ACC ] STREAM HÖRT 5205 /run/systemd/journal/stdout unix 2 [ ACC ] STREAM HÖRT 12757 /tmp/.menu-cached-:0-pi unix 2 [ ACC ] STREAM HÖRT 9673 /var/run/dhcpcd.sock unix 2 [ ACC ] STREAM HÖRT 9675 /var/run/dhcpcd.unpriv.sock unix 2 [ ACC ] STREAM HÖRT 7664 /var/run/avahi-daemon/socket unix 2 [ ACC ] STREAM HÖRT 7924 /run/user/1000/systemd/private unix 2 [ ACC ] STREAM HÖRT 7667 /var/run/dbus/system_bus_socket

[thommycgn]

Ok, now after reloading the alexa-app the device is in the list. But if I ask alexa to turn the light on/off she just say ok. The status is changing to on/off but no mqtt msg was send.

[biddster]

Have you tried wiring the output of this wemo node into a debug node and watching in the admin console when you ask alexa to turn on and off? If you set the debug node to dump the entire message we should see your configuration from above.

Mine has been super reliable for months so there must be something amiss.

[biddster]

Having thought about it, I think the fault must lie elsewhere. If the status on this node is changing, it must have emitted a msg via node.send({topic: config.onTopic, payload: config.onPayload});.

[thommycgn]

Output:

cmnd/led-deko-lampe/power : msg : Object { "topic": "cmnd/led-deko-lampe/power", "payload": "on", "_msgid": "57254bc9.a8dab4" }

But nothing else happen, no mqtt command goes out.

[biddster]

This looks like an issue elsewhere in your flow. This node is doing what it is supposed to. I suggest asking on the node red Google group.

[VillageThing]

I'm having trouble getting the Alexa app on my iPad to discover the wemo-emulator nodes. I have had them working in the past but at some point in the past month, they have stopped. Alexa won't discover any new instances of the node and existing nodes are listed in the Alexa app as 'offline'.

Furthermore, today, I noticed that one of them is showing a error...

Any help much appreciated.

[biddster]

Thanks for the report @VillageThing. What version of node-red and nodejs are you using?

[VillageThing]

Hi,

Here’s the version details:-

22 May 22:16:04 - [info] Node-RED version: v0.16.2 22 May 22:16:04 - [info] Node.js version: v4.8.3 22 May 22:16:04 - [info] Linux 4.9.24-v7+ arm LE

On 22 May 2017, at 22:05, biddster notifications@github.com wrote:

Thanks for the repot @VillageThing https://github.com/villagething. What version of node-red and nodejs are you using?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/biddster/node-red-contrib-wemo-emulator/issues/10#issuecomment-303219944, or mute the thread https://github.com/notifications/unsubscribe-auth/ARq7e92B1Q1suAHZIqiGyPxxCm3DalVCks5r8fibgaJpZM4LvnVW.

[biddster]

I'm struggling to find this one @VillageThing. This node doesn't do much other than wrap the wemore library. I'm struggling to find where in wemore that error might be thrown.

Have you upgraded nodejs since installing this node?

[VillageThing]

Thanks for looking. I'd really like to get this working. It's such a useful node. Shall I uninstall the wemo emulator and re-install it? Keith.

Sent from Keith's iPhone

On 24 May 2017, at 21:59, biddster notifications@github.com wrote:

I'm struggling to find this one @VillageThing. This node doesn't do much other than wrap the wemore library. I'm struggling to find where in wemore that error might be thrown.

Have you upgraded nodejs since installing this node?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[biddster]

By all means give that a try and let me know.

[biddster]

Closing old issue as no reply for a couple of years.