Thanks, I totally forgot about custom commands! I set it up to run at 0400 like yours. Appreciate the help!
1 Like
I'm seeing this message in my log:
sys:12019-02-04 09:18:00.444 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B870, 24F5A24633DB or 0A00005F.
sys:12019-02-04 09:13:30.369 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86F, 24F5A24633DB or 0A00005F.
sys:12019-02-04 09:09:00.268 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86E, 24F5A24633DB or 0A00005F.
sys:12019-02-04 09:04:30.182 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86D, 24F5A24633DB or 0A00005F.
sys:12019-02-04 09:00:00.639 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86C, 24F5A24633DB or 0A00005F.
sys:12019-02-04 08:55:29.768 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86B, 24F5A24633DB or 0A00005F.
sys:12019-02-04 08:50:59.677 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B86A, 24F5A24633DB or 0A00005F.
sys:12019-02-04 08:46:29.615 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B869, 24F5A24633DB or 0A00005F.
sys:12019-02-04 08:41:59.552 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B868, 24F5A24633DB or 0A00005F.
sys:12019-02-04 08:37:29.429 am warnReceived data from 10.0.0.95, no matching device found for 10.0.0.95, 0A00005F:B867, 24F5A24633DB or 0A00005F.
That IP address is one of my two Wemo Mini outlets which seems to be work find from Hubitat, meaning I can turn it on and off.
Any idea what's going on here?
thank you.
Well... I figured it out right after I posted, looking in my device list, I noticed that one of the two WeMos had "NULL" in the DNI (Device Network ID) field:
After filing it in with the correct value, that message in my log stopped.
I am having an issue lately where I see " warnConnection refused (Connection refused)" and my WEMO appears offline even though I have a routine to resubscribe every morning...
Anyone know of any trouble shooting tips other than deleting and restarting?
I have a lot of connection problems with mine. I don't use them for anything critical. For example, right now I can control one of them from HE but not from the Wemo app itself! They're very frustrating.
I recently had to switch out my router. Since then I cannot get my Wemo Outlet Minis to work with Hubitat and the app/drivers from @jason0x43. I have deleted my old devices, verified the control of my outlets directly from the Wemo app and ran discovery multiple times to add the devices back to Hubitat.
I do believe the processes are executing successfully. The logs show:
app:1322019-05-24 10:40:14.110 am debugCreating WeMo with MAC: 24F5A24889E9
app:1322019-05-24 10:40:14.094 am traceFound device; looking for existing child with dni 24F5A24889E9
app:1322019-05-24 10:40:14.092 am traceLooking for selected device 24F5A24889E9 in known devices...
app:1322019-05-24 10:40:14.078 am traceInitializing devices
app:1322019-05-24 10:40:14.068 am debugInitializing
app:1322019-05-24 10:40:14.067 am debugUpdated
app:1322019-05-24 10:40:04.318 am traceKnown devices: [24F5A24889E9:Wemo1]
app:1322019-05-24 10:40:04.317 am traceAdded discovered device 24F5A24889E9:Wemo1
app:1322019-05-24 10:40:04.307 am traceCreating list of known devices
app:1322019-05-24 10:40:04.306 am traceVerifying devices
app:1322019-05-24 10:39:34.371 am traceHandling setup.xml for urn:Belkin:device:controllee:1 (friendly name is 'Wemo1')
app:1322019-05-24 10:39:34.333 am traceKnown devices: [:]
app:1322019-05-24 10:39:34.328 am traceCreating list of known devices
There are references to child devices existing but no devices show up in Devices. No matter how many times I run Discovery, no devices get recreated. Any suggestions?
1 Like
Just to make sure, do you have the drivers installed (in that case, the WeMo Switch driver)? It looks like the connect app wasn't able to match up the device data with a driver name. At least, the next statement in the log above should have been something like "Created Wemo1 with id: something, MAC: 24F5A24889E9, MAC:".
I pushed an update to the WeMo Connect app that will log more information about the device it's trying to install. Update your connect app, give that a try, and post the logs.
I do have the drivers and app installed. Here is what I have done so far:
- Uninstalled existing driver and app
- Installed latest Wemo Switch and Wemo Switch and Insight drivers
- Installed latest Wemo Connect app
- Ran Discover process. It took a while but both devices finally showed up. Within 30 seconds of devices showing up in Discover process, I pressed Done.
- Checked my Devices page to see if devices show up. Nothing.
- Waited about 5 minutes (while composing this reply) and checked to see if the devices show up but nothing; no progress.
My suspicion is that my older devices are lingering phantom or ghost devices in Hubitat. But I do not see any way to verify or remove ghost devices.
Here is the latest log of the Wemo Connect app.
app:1612019-05-24 01:37:51.277 pm errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 454 (updated)
app:1612019-05-24 01:37:51.236 pm debugCreating WeMo device for [ssdpTerm:urn:Belkin:device:controllee:1, hub:1, port:c001, ip:C0A80210, name:Wemo1, verified:true, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:
Belkin:device:controllee:1, mac:24F5A24889E9]
app:1612019-05-24 01:37:51.221 pm traceFound device; looking for existing child with dni 24F5A24889E9
app:1612019-05-24 01:37:51.216 pm traceLooking for selected device 24F5A24889E9 in known devices...
app:1612019-05-24 01:37:51.204 pm traceInitializing devices
app:1612019-05-24 01:37:51.195 pm debugInitializing
app:1612019-05-24 01:37:51.193 pm debugUpdated
app:1612019-05-24 01:37:39.111 pm traceKnown devices: [24F5A24889E9:Wemo1, 24F5A2487571:Wemo2]
app:1612019-05-24 01:37:39.108 pm traceAdded discovered device 24F5A2487571:Wemo2
app:1612019-05-24 01:37:39.106 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:37:39.100 pm traceCreating list of known devices
app:1612019-05-24 01:37:39.098 pm traceVerifying devices
app:1612019-05-24 01:37:09.249 pm traceHandling setup.xml for urn:Belkin:device:controllee:1 (friendly name is 'Wemo2')
app:1612019-05-24 01:37:09.129 pm traceKnown devices: [24F5A24889E9:Wemo1]
app:1612019-05-24 01:37:09.128 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:37:09.119 pm traceCreating list of known devices
app:1612019-05-24 01:37:09.115 pm traceGetting setup.xml for null at 192.168.2.11:49153
app:1612019-05-24 01:37:09.111 pm traceVerifying devices
app:1612019-05-24 01:36:39.892 pm traceParsed discovery message: [mac:24F5A24889E9, ip:C0A80210, port:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, hub:1]
app:1612019-05-24 01:36:39.891 pm traceAdding new device 24F5A2487571
app:1612019-05-24 01:36:39.882 pm traceParsed discovery message: [mac:24F5A2487571, ip:C0A8020B, port:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0100A5D:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, hub:1]
app:1612019-05-24 01:36:39.878 pm traceParsing discovery message: mac:24F5A24889E9, networkAddress:C0A80210, deviceAddress:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, ssdpNTS:
app:1612019-05-24 01:36:39.872 pm traceParsing discovery message: mac:24F5A2487571, networkAddress:C0A8020B, deviceAddress:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0100A5D:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, ssdpNTS:
app:1612019-05-24 01:36:39.731 pm traceKnown devices: [24F5A24889E9:Wemo1]
app:1612019-05-24 01:36:39.730 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:36:39.720 pm traceCreating list of known devices
app:1612019-05-24 01:36:39.716 pm traceSending discovery message for [urn:Belkin:device:insight:1, urn:Belkin:device:controllee:1, urn:Belkin:device:sensor:1, urn:Belkin:device:lightswitch:1, urn:Belkin:device:dimmer:1]
app:1612019-05-24 01:36:09.740 pm traceKnown devices: [24F5A24889E9:Wemo1]
app:1612019-05-24 01:36:09.739 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:36:09.730 pm traceCreating list of known devices
app:1612019-05-24 01:36:09.728 pm traceVerifying devices
app:1612019-05-24 01:35:38.941 pm traceKnown devices: [24F5A24889E9:Wemo1]
app:1612019-05-24 01:35:38.940 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:35:38.935 pm traceCreating list of known devices
app:1612019-05-24 01:35:38.934 pm traceVerifying devices
app:1612019-05-24 01:35:21.913 pm errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 454 (installed)
app:1612019-05-24 01:35:21.880 pm debugCreating WeMo device for [ssdpTerm:urn:Belkin:device:controllee:1, hub:1, port:c001, ip:C0A80210, name:Wemo1, verified:true, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, mac:24F5A24889E9]
app:1612019-05-24 01:35:21.869 pm traceFound device; looking for existing child with dni 24F5A24889E9
app:1612019-05-24 01:35:21.864 pm traceLooking for selected device 24F5A24889E9 in known devices...
app:1612019-05-24 01:35:21.850 pm traceInitializing devices
app:1612019-05-24 01:35:21.841 pm debugInitializing
app:1612019-05-24 01:35:21.840 pm debugInstalled
app:1612019-05-24 01:35:15.501 pm traceKnown devices: [24F5A24889E9:Wemo1]
app:1612019-05-24 01:35:15.500 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 01:35:15.491 pm traceCreating list of known devices
app:1612019-05-24 01:35:15.490 pm traceVerifying devices
app:1612019-05-24 01:34:45.643 pm traceHandling setup.xml for urn:Belkin:device:controllee:1 (friendly name is 'Wemo1')
app:1612019-05-24 01:34:45.537 pm traceKnown devices: [:]
app:1612019-05-24 01:34:45.532 pm traceCreating list of known devices
app:1612019-05-24 01:34:45.528 pm traceGetting setup.xml for null at 192.168.2.16:49153
app:1612019-05-24 01:34:45.509 pm traceVerifying devices
app:1612019-05-24 01:34:15.567 pm traceAdding new device 24F5A24889E9
app:1612019-05-24 01:34:15.563 pm traceAdding new device 24F5A2487571
app:1612019-05-24 01:34:15.555 pm traceParsed discovery message: [mac:24F5A24889E9, ip:C0A80210, port:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, hub:1]
app:1612019-05-24 01:34:15.551 pm traceParsed discovery message: [mac:24F5A2487571, ip:C0A8020B, port:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0100A5D:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, hub:1]
app:1612019-05-24 01:34:15.505 pm traceParsing discovery message: mac:24F5A24889E9, networkAddress:C0A80210, deviceAddress:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, ssdpNTS:
app:1612019-05-24 01:34:15.500 pm traceParsing discovery message: mac:24F5A2487571, networkAddress:C0A8020B, deviceAddress:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0100A5D:Belkin:device:controllee:1, ssdpTerm:urn:Belkin:device:controllee:1, ssdpNTS:
app:1612019-05-24 01:34:15.312 pm traceKnown devices: [:]
app:1612019-05-24 01:34:15.292 pm traceCreating list of known devices
app:1612019-05-24 01:34:15.289 pm tracesubscribed to urn:Belkin:device:dimmer:1
app:1612019-05-24 01:34:15.282 pm tracesubscribed to urn:Belkin:device:lightswitch:1
app:1612019-05-24 01:34:15.275 pm tracesubscribed to urn:Belkin:device:sensor:1
app:1612019-05-24 01:34:15.268 pm tracesubscribed to urn:Belkin:device:controllee:1
app:1612019-05-24 01:34:15.261 pm tracesubscribed to urn:Belkin:device:insight:1
app:1612019-05-24 01:34:15.237 pm traceSending discovery message for [urn:Belkin:device:insight:1, urn:Belkin:device:controllee:1, urn:Belkin:device:sensor:1, urn:Belkin:device:lightswitch:1, urn:Belkin:device:dimmer:1]
app:1612019-05-24 01:34:15.234 pm traceResetting refresh count and discovered devices
Additional information: I had 2 Wemo mini outlets I had never previously configured. I configured them as new devices and verified their operation. I ran the Discover process again and they too were not added as devices to my device list.
There does seem to be a Java error being logged.
app:1612019-05-24 02:44:08.246 pm errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 454 (updated)
app:1612019-05-24 02:44:08.217 pm debugCreating WeMo device for [ssdpTerm:urn:Belkin:device:controllee:1, hub:1, port:c001, ip:C0A80210, name:Wemo1, verified:true, ssdpPath:/setup.xml, ssdpUSN:uuid:Socket-1_0-221802K0101499:Belkin:device:controllee:1, mac:24F5A24889E9]
app:1612019-05-24 02:44:08.207 pm traceFound device; looking for existing child with dni 24F5A24889E9
app:1612019-05-24 02:44:08.205 pm traceLooking for selected device 24F5A24889E9 in known devices...
app:1612019-05-24 02:44:08.195 pm traceInitializing devices
app:1612019-05-24 02:44:08.186 pm debugInitializing
app:1612019-05-24 02:44:08.185 pm debugUpdated
app:1612019-05-24 02:44:01.371 pm traceKnown devices: [24F5A24889E9:Wemo1, 24F5A2493F01:Wemo3, 24F5A2494AA3:Wemo4, 24F5A2487571:Wemo2]
app:1612019-05-24 02:44:01.370 pm traceAdded discovered device 24F5A2487571:Wemo2
app:1612019-05-24 02:44:01.368 pm traceAdded discovered device 24F5A2494AA3:Wemo4
app:1612019-05-24 02:44:01.367 pm traceAdded discovered device 24F5A2493F01:Wemo3
app:1612019-05-24 02:44:01.366 pm traceAdded discovered device 24F5A24889E9:Wemo1
app:1612019-05-24 02:44:01.358 pm traceCreating list of known devices
1 Like
I am seeing the exact same thing.
I tried rediscovering the wemo switches, then "deleted" them (unchecked the boxes) then added them back (checked the boxes) then looked at the log. This line looks a bit off to me, the IP address and port seem quite stranges..
Parsed discovery message: [mac:94103E50825D, ip:C0A8010B, port:c001, ssdpPath:/setup.xml, ssdpUSN:uuid:Lightswitch-1_0-221545K13015CC:Belkin:device:lightswitch:1, ssdpTerm:urn:Belkin:device:lightswitch:1, hub:1]
So . . . were you successful in getting them added back to your device list?
They come up on the list, I can check them, but I can’t turn the switches on or off, etc. is there a file I can manually edit to plug in the IP address and port to see if that is the issue?
1 Like
That's what I get too. They show up on the list. I can check/uncheck them but they never get added to Devices. As far as I know, you cannot add the IP address. I think they use the MAC address anyway. I have all of my switches set to DHCP static.
I am beginning to suspect a problem with the latest Hubitat firmware update. The Wemo Connect and now another app (Holiday Lights) are generating Java errors. I may try downgrading my firmware to 2.0.9.x from the latest 2.1.0.x. I did not have any of these issues with the prior firmware.
1 Like
I got this error as well.
java.lang.NullPointerException: Cannot invoke method getAt() on null object on line 454 (updated)
I can't find getAt() in the app code, so I guess it is from Hubitat?
Anyway, I can discover devices but they never show up in the list. I believe it is caused by this exception.
And I am on 2.1.0.x.
Explanation here:
1 Like
I made that update, but PRs in general are always welcome!
Did you do this just installing the driver and without installing the app?
I tried, but the device just said offline.
I also tried removing ":" from MAC and capitalizing all letters of MAC''
Device has static ip as well
