[SOLVED] Wemo Not Found on Network

Add-ons Bindings
,
1

I have been trying to get my Wemo Insight to show up on my openHab 1.8 system. I admit I just started to play with openHab today, so I’m totally new, but I did manage to get my Nest devices to bind and show up in my self-created homepage, so I’m not a complete failure.

Anyway, first problem is that even in DEBUG mode, I do not get any information about the WEMO’s UDN. I was able to find something that looked like the example UDNs in the wiki using a third-party app, but I thought it would be found automatically and I could bind it to items using that information in the log. Negative.

Using the UDN I eventually DID find, I still don’t get any love from it. In the log, rough sequence, WemoActivator starts binding, WemoDiscovery() is called, A datagram packet is sent, SSDP message received and then times out. Execute() method is called (and called) and then it starts parsing the configuration I entered for my device:

Configuration for WeMo item ‘insight’:
WemoGenericBindingProvider[:76]- UDN = ‘Insight-1_0-221508K120039C’
WemoGenericBindingProvider[:77]- channelType = ‘state’
WemoGenericBindingProvider[:75]- Configuration for WeMo item ‘insight_currentPower’:
WemoGenericBindingProvider[:76]- UDN = ‘Insight-1_0-221508K120039C’
WemoGenericBindingProvider[:77]- channelType = ‘currentPower’

and then later

internal.WemoBinding[:118]- execute() method is called!
02:59:14.409 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item ‘insight’ state will be updated
02:59:14.411 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found for item ‘insight’, start new discovery
02:59:14.412 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is called!
02:59:14.414 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.

The code I have is pretty straightforward:

Items:
Switch insight “Aerogarden” {wemo=“Insight-1_0-221508K120039C”}
Number insight_currentPower “Current Power [%.0f] W” {wemo=“Insight-1_0-221508K120039C;currentPower”}

Sitemap:
Switch item=insight
Text item=insight_currentPower label=“Current Power [%.0f W]”

Any help would be much appreciated, or should I just be using 2.0 even though it’s in beta? Thanks in advance!

1 Like
2

Hi,
could you please give more information about your WeMo devices, especially the firmware versions.
If you didn’t, please update to latest firmware. Belkin has changed the discovery answers two times.
With the latest firmware you should see a message that device with UDN is found, no need to start debug mode.

Best
Hans-Jörg

3

Sure! I only have one device right now, here is a snapshot of the info:

image2.PNG750×1334 56.8 KB

4

Strange, firmware is exactly same as mine.
Could you give some more information on your openHAB Server, OS and Java Version.

Best
Hans-Jörg

5

Thanks for your continued help, in all my troubleshooting searches on the
topic, your name was the one that kept coming up so I was hoping you’d see
this. :slight_smile:

I’m using Java SE 8 (Oracle) on a Synology DS213 running DSM 5.2. One thing
that occurs to me, I installed openHab 1.5 initially as it was a pre-built
package and then copied the 1.8 files in, overwriting where there were
conflicts. My Synology still thinks version 1.5 is installed but I’m
thinking that may be independent of openHab.

Another thing that in the light of a new day may have some bearing, I
notice that while the time on my server is correct, the time that openHab
thinks it is isn’t correct. Would that possibly interfere? I need to get to
the bottom of that, I think my build believes it is in Germany, in the log
files I see it looking up German weather.

I haven’t been able to get XBMC (Kodi) working either, although I just
started getting into that last night, so far the only thing I have been
successful in is getting the Nest thermostats and Protects online and
reading/writing.

Thanks again for your help!

6

Ok, it is not a JAVA version issue, great
Could you please add an entry to your logback_debug.xml like
logger name=“org.openhab.binding.wemo” level="trace"
and post the wemo relevant entries of the logfile.

Best
Hans-Jörg

7

Alright, I did that, but still no success (I actually don’t see any
additional info in the logfile.

Here’s the line I added to the logback_debug.xml:

And here’s everything WEMO related in the logfile:

23:23:18.981 DEBUG o.o.b.w.internal.WemoActivator[:34]- Wemo binding has
been started.
23:23:19.148 DEBUG o.o.m.i.i.GenericItemProvider[:341]- Start processing
binding configuration of Item ‘insight (Type=SwitchItem,
State=Uninitialized)’ with ‘WemoGenericBindingProvider’ reader.
23:23:19.155 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:75]- Configuration
for WeMo item ‘insight’:
23:23:19.181 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:76]- UDN =
'Insight-1_0-221508K120039C’
23:23:19.184 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:77]- channelType =
'state’
23:23:19.203 DEBUG o.o.m.i.i.GenericItemProvider[:341]- Start processing
binding configuration of Item ‘insight_currentPower (Type=NumberItem,
State=Uninitialized)’ with ‘WemoGenericBindingProvider’ reader.
23:23:19.214 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:75]- Configuration
for WeMo item ‘insight_currentPower’:
23:23:19.228 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:76]- UDN =
'Insight-1_0-221508K120039C’
23:23:19.230 DEBUG o.o.b.w.i.WemoGenericBindingProvider[:77]- channelType =
'currentPower’
23:23:19.460 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:23:19.506 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:23:19.524 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
23:23:20.538 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:23:20.564 INFO o.o.c.s.AbstractActiveService[:169]- Wemo Refresh
Service has been started
23:23:20.566 DEBUG o.o.b.w.internal.WemoBinding[:118]- execute() method is
called!
23:23:20.598 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item ‘insight’
state will be updated
23:23:20.600 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight’, start new discovery
23:23:20.601 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:23:20.607 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:23:20.609 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
…
23:23:21.617 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:23:21.620 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight’ received
23:23:21.621 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item
’insight_currentPower’ state will be updated
23:23:21.622 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight_currentPower’, start new discovery
23:23:21.623 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:23:21.625 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:23:21.626 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
…
23:23:22.689 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:23:22.691 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight_currentPower’ received
…
23:24:22.697 DEBUG o.o.b.w.internal.WemoBinding[:118]- execute() method is
called!
23:24:22.699 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item ‘insight’
state will be updated
23:24:22.700 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight’, start new discovery
23:24:22.701 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:24:22.765 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:24:22.804 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
23:24:23.827 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:24:23.829 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight’ received
23:24:23.830 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item
’insight_currentPower’ state will be updated
23:24:23.831 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight_currentPower’, start new discovery
23:24:23.832 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:24:23.834 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:24:23.835 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
23:24:24.847 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:24:24.849 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight_currentPower’ received
…
23:25:24.857 DEBUG o.o.b.w.internal.WemoBinding[:118]- execute() method is
called!
23:25:24.858 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item ‘insight’
state will be updated
23:25:24.860 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight’, start new discovery
23:25:24.861 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:25:24.863 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:25:24.864 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
23:25:25.867 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:25:25.869 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight’ received
23:25:25.870 DEBUG o.o.b.w.internal.WemoBinding[:123]- Wemo item
’insight_currentPower’ state will be updated
23:25:25.871 DEBUG o.o.b.w.internal.WemoBinding[:450]- No Location found
for item ‘insight_currentPower’, start new discovery
23:25:25.872 DEBUG o.o.b.w.internal.WemoBinding[:301]- wemoDiscovery() is
called!
23:25:25.874 DEBUG o.o.b.w.internal.WemoBinding[:354]- Send datagram packet.
23:25:25.875 DEBUG o.o.b.w.internal.WemoBinding[:359]- Receive SSDP Message.
23:25:26.887 DEBUG o.o.b.w.internal.WemoBinding[:383]- Message receive
timed out.
23:25:26.889 DEBUG o.o.b.w.internal.WemoBinding[:498]- New raw
InsightParams ‘null’ for device ‘insight_currentPower’ received
…
and so on. Is it possible there’s some port or something that I have to
open on the router or the NAS? I’m really not sure what else to do here.

8

Are you sure that you did set loglevel to trace ?
I don’t see anny message traces in the log, which is the important part.

9

Oh weird, I didn’t copy that line but yes I set it to trace unless there’s
a certain part of the logback that it needs to be placed in?

Without the tags/GT/LT signs, I put in this: logger
name=“org.openhab.binding.wemo” level=“TRACE”

10

It needs to be placed into logback_debug.xml, not in logback.xml

11

Oh yes sorry, I put it in logback_debug I was just shortcutting here…

12

Now I am running out of clues.
Could you try the openhab 2.0 beta and see if your WeMo is discovered there.

13

I took the easy route and went back to 1.7.1 which supports friendly names and works like a charm. Just can’t use all the features of the Insight but I don’t have one myself.

14

I’d like to move to 2 since I have Lifx bulbs anyway, but I haven’t found
any great documentation on getting it running on Synology and I’m not quite
sure how to go about it. I do have a suspicion that the Openhab launcher is
not starting the startup_debug script but again, I tried to manually
execute that in ssh and no idea why it didn’t work or what I’m supposed to
do. I think I’d need to relearn Unix to really get this thing going… :frowning:

15

Do you have plex installed and running? I was having the same problem and when I stopped plex OH found my wemo devices. Just give OH few minutes and it will find the devices and you can start plex again. After I do that both wemo devices and plex work fine. my config are 214play, java 18.5_65 and OH 1.8.

2 Likes
16

I -DO- have Plex installed and running. Unfortunately, I broke my 1.8
install trying to upgrade to 2 but if I revert back to 1.8 for now then I
will definitely give that a try! Thanks for the idea, I wonder what would
cause that? How did you figure that out?

17

discovered by chance after few days of troubleshooting. Hope it helps you

18

In the interest of not creating another thread I’m posting with the same issue. 1.7.1 still works flawlessly with “friendly names” but I’ve playing with 1.8.1 and Wemo is just failing. I have my UDN for my single device without the state since it is just a switch:

Switch CoopLight “CoopLight” (GF_Garage) {wemo=“Socket-1_0-221438K0100073”}

And it just doesn’t work. My mqtt device and Insteon stuff works fine in 1.8.1. Just Wemo being a no go. And no plex running. Just the echo-ha-bridge running on that dedicated machine.

1 Like
19

Hey would you mind detailing how you found the device ID?

Wemo addon starts up fine for me. But it doesn’t list active devices on the network. But I can use them with no problem from my phone.

I’ve been trying to get this to work for weeks. It’s very frustrating.

20

Hi,
Belkin sometimes changes how WeMo devices react on discovery calls and it seems that I forgot to update this to the latest changes in the 1.x Version of the WeMo Binding.
I will provide a fix tonight, so it should be back working with the next nightly builds.

Best
Hans-Jörg