You probably need to delete all the devices and driver. Then install them again. There’s been few hiccups with LAN devices lately. I had to delete several devices I monitored with this driver.
thanks
just tried that but still no luck
@montyfert - I’m sorry to hear about your trouble. There has been some glitchy things happening on the platform lately; I suspect your driver may not be running.
Can you provide some more info - maybe a screen shot of your device Controls screen so I can see the exact state?
I’m not sure exactly what you’ve tried so far, but here is would I would suggest in order of things to try:
- Turn monitoring off for your device, wait a few seconds, then turn back on again
- Try creating a new device and see if you can get that one working after configuring
- Reboot hub
- Retry #1 & #2 above
- If still not working, delete all LAN Device Monitor devices then run an Add device / Scan nearby devices to see if you get a new LAN Device Monitor device in your No room assigned room.
- If you get a device created, try configuring it and seeing if it is working
- If still nothing working, delete all LAN Device Monitor devices, go to the channel invite and choose to UNINSTALL the driver.
- Wait an hour and then return to the channel invite and choose to INSTALL the driver again
- Once driver is installed to your hub, perform an Add device / Scan nearby devices to create your first device, configure it, and fingers crossed it will work.
If you are still unable to get it to work we may need to use the CLI to get some logs, as there must be something very unusual going on.
Wow I’m surprised none of that got you back up and running!
The CLI is the SmartThings ‘command line interface’, which is just an application you download to a computer (Windows/Linux/Mac) that allows you to perform a number of tasks such as getting info and issuing commands for devices, drivers, channels, etc. It also allows you to display log output for a chosen driver. So in this case it may allow us to see if some error is occurring with the driver, or if it is even installed and running on your hub.
See this link for instructions on how to get it downloaded and running on a Windows computer.
│ # │ Driver Id │ Name │
├───┼──────────────────────────────────────┼─────────────────────────┤
│ 1 │ cdb5df02-8915-474d-941c-3bc6acd46032 │ LAN Device Monitor │
│ 2 │ 55cde59c-2ba4-40dc-abe7-d2feb24980c6 │ LG.TV │
│ 3 │ d981b6ea-8f27-4984-8d3b-9922404ff363 │ RDG - Zigbee Button │
│ 4 │ 3c9378c1-79ab-4534-b8c3-4502bc0257b2 │ Roku Driver v0.1b │
│ 5 │ d281b4fc-b962-4ba1-919f-6bc122805c33 │ UPnP Explorer │
│ 6 │ 3fb97b6c-f481-441b-a14e-f270d738764e │ Zigbee Button │
│ 7 │ d620900d-f7bc-4ab5-a171-6dd159872f7d │ Zigbee Motion Sensor │
│ 8 │ 00425c55-0932-416f-a1ba-78fae98ab614 │ Zigbee Motion Sensor Mc │
└───┴──────────────────────────────────────┴─────────────────────────┘
? Select a driver. 1
2022-06-16T19:52:07.621549038+00:00 TRACE LAN Device Monitor Setup driver landevmonDriver with lifecycle handlers:
DeviceLifecycleDispatcher: landevmonDriver
default_handlers:
removed:
driverSwitched:
added:
infoChanged:
doConfigure:
init:
deleted:
child_dispatchers:
2022-06-16T19:52:07.645836705+00:00 TRACE LAN Device Monitor Setup driver landevmonDriver with Capability handlers:
CapabilityCommandDispatcher: landevmonDriver
default_handlers:
partyvoice23922.wakeonlan:
push
partyvoice23922.createanother:
push
partyvoice23922.moncontrol:
setSwitch
child_dispatchers:
2022-06-16T19:52:07.654539330+00:00 INFO LAN Device Monitor LAN Device Monitor Driver v1.1 started
2022-06-16T19:52:07.685529246+00:00 TRACE LAN Device Monitor Received event with handler environment_info
2022-06-16T19:52:07.698320288+00:00 TRACE LAN Device Monitor Received event with handler environment_info
2022-06-16T19:52:07.710273996+00:00 DEBUG LAN Device Monitor Z-Wave hub node ID environment changed.
2022-06-16T19:52:07.719431705+00:00 TRACE LAN Device Monitor Received event with handler discovery
2022-06-16T19:52:07.740467830+00:00 DEBUG LAN Device Monitor Creating landevmon device: label=<LAN Device Monitor #1>, id=<landevmon_1655409127.739>
2022-06-16T19:52:07.764019246+00:00 DEBUG LAN Device Monitor Exiting device discovery
2022-06-16T19:52:07.769691330+00:00 DEBUG LAN Device Monitor discovery device thread event handled
2022-06-16T19:52:09.013642580+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:52:09.033171663+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received lifecycle event: added
2022-06-16T19:52:09.059832538+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:52:09.073799830+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received lifecycle event: doConfigure
2022-06-16T19:52:09.094155163+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:52:09.102677955+00:00 INFO LAN Device Monitor ADDED handler: <884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> successfully added; device_network_id = landevmon_1655409127.739
2022-06-16T19:52:09.117486996+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“state”,“capability_id”:“partyvoice23922.upnpstate”,“component_id”:“main”,“state”:{“value”:"-unknown-"}}
2022-06-16T19:52:09.158769080+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-06-16T19:52:09.178012621+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T19:52:09.195177663+00:00 DEBUG LAN Device Monitor ADDED handler exiting for LAN Device Monitor #1
2022-06-16T19:52:09.199885246+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:52:09.205908871+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:52:09.211508413+00:00 DEBUG LAN Device Monitor INIT handler for LAN Device Monitor #1
2022-06-16T19:52:09.217350955+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T19:52:09.232994955+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:52:09.241494080+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:52:09.246982996+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:52:09.262839288+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:52:14.850147872+00:00 TRACE LAN Device Monitor Received event with handler discovery
2022-06-16T19:53:31.419440465+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:53:31.426327090+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received lifecycle event: infoChanged
2022-06-16T19:53:31.431405131+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:53:31.434361756+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T19:53:31.437268131+00:00 DEBUG LAN Device Monitor Icon changed to other
2022-06-16T19:53:31.444715465+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:53:32.040350298+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:53:32.046075131+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received lifecycle event: infoChanged
2022-06-16T19:53:32.051021715+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:53:32.053920631+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T19:53:32.056753923+00:00 DEBUG LAN Device Monitor ****** DRIVER RESTART ASSUMED ******
2022-06-16T19:53:32.059510048+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:54:05.763495957+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:54:05.770678947+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received lifecycle event: infoChanged
2022-06-16T19:54:05.775297637+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:54:05.778263028+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T19:54:05.781274105+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:54:24.383189536+00:00 TRACE LAN Device Monitor Received event with handler capability
2022-06-16T19:54:24.389402203+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received command: {“args”:{“value”:“on”},“capability”:“partyvoice23922.moncontrol”,“command”:“setSwitch”,“component”:“main”,“positional_args”:[“on”]}
2022-06-16T19:54:24.392736828+00:00 TRACE LAN Device Monitor Found CapabilityCommandDispatcher handler in landevmonDriver
2022-06-16T19:54:24.395861036+00:00 INFO LAN Device Monitor Monitor control switched to on
2022-06-16T19:54:24.399132328+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-06-16T19:54:24.415898661+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:58:59.513417915+00:00 TRACE LAN Device Monitor Received event with handler capability
2022-06-16T19:58:59.526161124+00:00 INFO LAN Device Monitor <Device: 884e2b33-79a2-40c7-aa1a-9c6a9878e980 (LAN Device Monitor #1)> received command: {“args”:{},“capability”:“partyvoice23922.createanother”,“command”:“push”,“component”:“main”,“positional_args”:{}}
2022-06-16T19:58:59.529431749+00:00 TRACE LAN Device Monitor Found CapabilityCommandDispatcher handler in landevmonDriver
2022-06-16T19:58:59.532269415+00:00 DEBUG LAN Device Monitor Createdev handler- command received: push
2022-06-16T19:58:59.535645749+00:00 DEBUG LAN Device Monitor Creating landevmon device: label=<LAN Device Monitor #2>, id=<landevmon_1655409539.534>
2022-06-16T19:58:59.543000665+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T19:59:00.383186165+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:59:00.399424582+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> received lifecycle event: added
2022-06-16T19:59:00.434297957+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:59:00.444818915+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> received lifecycle event: doConfigure
2022-06-16T19:59:00.469324082+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:59:00.474325415+00:00 INFO LAN Device Monitor ADDED handler: <29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> successfully added; device_network_id = landevmon_1655409539.534
2022-06-16T19:59:00.477628124+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> emitting event: {“attribute_id”:“state”,“capability_id”:“partyvoice23922.upnpstate”,“component_id”:“main”,“state”:{“value”:"-unknown-"}}
2022-06-16T19:59:00.510977374+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-06-16T19:59:00.571837165+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T19:59:00.622877957+00:00 DEBUG LAN Device Monitor ADDED handler exiting for LAN Device Monitor #2
2022-06-16T19:59:00.642142040+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
2022-06-16T19:59:00.647615457+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:59:00.653280749+00:00 DEBUG LAN Device Monitor INIT handler for LAN Device Monitor #2
2022-06-16T19:59:00.658658124+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T19:59:00.679731624+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
2022-06-16T19:59:00.684359457+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:59:00.691840165+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
2022-06-16T19:59:00.706703707+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
2022-06-16T19:59:52.880317213+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T19:59:52.888020505+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> received lifecycle event: infoChanged
2022-06-16T19:59:52.899241547+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T19:59:52.902229755+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T19:59:52.905332338+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
2022-06-16T20:00:18.213185175+00:00 TRACE LAN Device Monitor Received event with handler capability
2022-06-16T20:00:18.218748050+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> received command: {“args”:{“value”:“on”},“capability”:“partyvoice23922.moncontrol”,“command”:“setSwitch”,“component”:“main”,“positional_args”:[“on”]}
2022-06-16T20:00:18.222025508+00:00 TRACE LAN Device Monitor Found CapabilityCommandDispatcher handler in landevmonDriver
2022-06-16T20:00:18.225023925+00:00 INFO LAN Device Monitor Monitor control switched to on
2022-06-16T20:00:18.228246300+00:00 INFO LAN Device Monitor <Device: 29023f59-05c6-467a-9059-b714c5f41b14 (LAN Device Monitor #2)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-06-16T20:00:18.243336716+00:00 DEBUG LAN Device Monitor LAN Device Monitor #2 device thread event handled
listening for logs… -
its all dutch to me
Nice! Thank you for the log.
I take it the logging output just stopped spitting anything more out at the end there?
Let me study this some more and I’ll get back to you.
The first thing I’m noticing is that I don’t see you configuring the devices. For example, you have to go into device Settings and provide a valid IP address of the physical device you want to monitor. The physical device has to support UPnP for it to work. You said you had it working before, so I assume you have a UPnP device. There won’t be much more in the log until you configure at least one device and it is found and responding on the network.
yes one is a pc the other a phone and they were working before
hi i added two one at
2022-06-16T19:54:24.389402203+00:00
and 1 at
2022-06-16T19:58:59.535645749+00:00
I see where added them, but I don’t see where you provided the IP addresses.
EDIT: Disregard, I guess I didn’t log that info when it is updated
just added a new 1 after removing other two
? Select a driver. 1
2022-06-16T22:44:20.746470609+00:00 TRACE LAN Device Monitor Setup driver landevmonDriver with lifecycle handlers:
DeviceLifecycleDispatcher: landevmonDriver
default_handlers:
driverSwitched:
infoChanged:
doConfigure:
removed:
added:
init:
deleted:
child_dispatchers:
2022-06-16T22:44:20.778187692+00:00 TRACE LAN Device Monitor Setup driver landevmonDriver with Capability handlers:
CapabilityCommandDispatcher: landevmonDriver
default_handlers:
partyvoice23922.createanother:
push
partyvoice23922.moncontrol:
setSwitch
partyvoice23922.wakeonlan:
push
child_dispatchers:
2022-06-16T22:44:20.785045984+00:00 INFO LAN Device Monitor LAN Device Monitor Driver v1.1 started
2022-06-16T22:44:20.825181900+00:00 TRACE LAN Device Monitor Received event with handler environment_info
2022-06-16T22:44:20.836513984+00:00 TRACE LAN Device Monitor Received event with handler environment_info
2022-06-16T22:44:20.845239567+00:00 DEBUG LAN Device Monitor Z-Wave hub node ID environment changed.
2022-06-16T22:44:20.860997651+00:00 TRACE LAN Device Monitor Received event with handler discovery
2022-06-16T22:44:20.881691984+00:00 DEBUG LAN Device Monitor Creating landevmon device: label=<LAN Device Monitor #1>, id=<landevmon_1655419460.88>
2022-06-16T22:44:20.900442151+00:00 DEBUG LAN Device Monitor Exiting device discovery
2022-06-16T22:44:20.909916776+00:00 DEBUG LAN Device Monitor discovery device thread event handled
2022-06-16T22:44:21.617925776+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T22:44:21.631673443+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> received lifecycle event: added
2022-06-16T22:44:21.649302234+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T22:44:21.655180776+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> received lifecycle event: doConfigure
2022-06-16T22:44:21.666546651+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:44:21.671840109+00:00 INFO LAN Device Monitor ADDED handler: <bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> successfully added; device_network_id = landevmon_1655419460.88
2022-06-16T22:44:21.678219984+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“state”,“capability_id”:“partyvoice23922.upnpstate”,“component_id”:“main”,“state”:{“value”:"-unknown-"}}
2022-06-16T22:44:21.700482943+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-06-16T22:44:21.719264151+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T22:44:21.735318984+00:00 DEBUG LAN Device Monitor ADDED handler exiting for LAN Device Monitor #1
2022-06-16T22:44:21.738959651+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:44:21.745007901+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:44:21.750122068+00:00 DEBUG LAN Device Monitor INIT handler for LAN Device Monitor #1
2022-06-16T22:44:21.755438026+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“Monitoring Off”}}
2022-06-16T22:44:21.770081109+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:44:21.779381943+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:44:21.784741443+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:44:21.800192568+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:44:23.880758194+00:00 TRACE LAN Device Monitor Received event with handler discovery
2022-06-16T22:45:56.881571030+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T22:45:56.888429946+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> received lifecycle event: infoChanged
2022-06-16T22:45:56.893551363+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:45:56.896535030+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T22:45:56.899507280+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:45:59.905189031+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T22:45:59.916086573+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (LAN Device Monitor #1)> received lifecycle event: infoChanged
2022-06-16T22:45:59.938871198+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:45:59.945351239+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T22:45:59.962165948+00:00 DEBUG LAN Device Monitor Icon changed to other
2022-06-16T22:45:59.969621031+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:46:00.798676740+00:00 TRACE LAN Device Monitor Received event with handler device_lifecycle
2022-06-16T22:46:00.809742657+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (pc)> received lifecycle event: infoChanged
2022-06-16T22:46:00.823996073+00:00 TRACE LAN Device Monitor Found DeviceLifecycleDispatcher handler in landevmonDriver
2022-06-16T22:46:00.826960240+00:00 DEBUG LAN Device Monitor INFOCHANGED handler; event= infoChanged
2022-06-16T22:46:00.829857657+00:00 DEBUG LAN Device Monitor ****** DRIVER RESTART ASSUMED ******
2022-06-16T22:46:00.832761365+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
2022-06-16T22:46:06.003159534+00:00 TRACE LAN Device Monitor Received event with handler capability
2022-06-16T22:46:06.010207159+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (pc)> received command: {“args”:{“value”:“on”},“capability”:“partyvoice23922.moncontrol”,“command”:“setSwitch”,“component”:“main”,“positional_args”:[“on”]}
2022-06-16T22:46:06.013579201+00:00 TRACE LAN Device Monitor Found CapabilityCommandDispatcher handler in landevmonDriver
2022-06-16T22:46:06.016664409+00:00 INFO LAN Device Monitor Monitor control switched to on
2022-06-16T22:46:06.020463492+00:00 INFO LAN Device Monitor <Device: bb3f8cc6-29e6-4f24-83a9-8165113a86e0 (pc)> emitting event: {“attribute_id”:“switch”,“capability_id”:“partyvoice23922.moncontrol”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-06-16T22:46:06.031088659+00:00 DEBUG LAN Device Monitor LAN Device Monitor #1 device thread event handled
listening for logs… /
I see the problem. There have been some changes to the platform recently that has caused headaches with device controls and fields. In this case, it is the switch that you use to turn on and off monitoring. For some reason it is no longer returning the same value as it was before when you turn it on. As a result, monitoring never gets started.
I’m glad you uncovered this. Please give me a day to figure out a fix. I’ll get back to you!
2 Likes
oh thanks your a star, i also tried the upnp explorer is ti but it only found my cctv recorder nothing else. thanks again for the help
martin
All users of the LAN Device Monitor Driver:
Due to recent platform changes, I’ve needed to make a change to this Edge driver to address a problem with the Monitoring switch. If your mobile app is on Andriod and you tried to turn monitoring off or on after a recent app update, your device may seem to no longer work. Thanks to @montyfert for first reporting this problem.
The good news is that I’ve corrected this, but the bad news is I have to release the fix as a new driver. It could not be done as an update to the current driver or devices. However if your current devices are still working for you and/or you have no need to ever turn on or off monitoring for a device, then you are welcome to continue using the current driver. It will not be deleted from your hub. However be forewarned that all future changes/enhancements will be made to the new driver version described below.
If you ARE experiencing the problem described above, then you will need to get the new driver installed to your hub and recreate your devices. I apologize for the inconvenience - I wish I could have made it easier!
If you are transitioning to the new driver, I would recommend first deleting your current LAN Device Monitor devices in order to cease their UPnP activity with your physical devices, and then create them again under the new driver.
The new driver can be found on my shared projects channel and is called LAN Device Monitor V1.3, and the driver version is 2022-06-18T18:15:30.352910308.
As usual, you’ll need to perform an Add device / Scan for nearby devices in the app to get the first device created in your ‘No room assigned’ room.
2 Likes
I’ve been giving this a whirl today. I have tried, using IP address to find a printer, several Xboxes, a Windows laptop and a Mac. So far it hasn’t found any of them.
I have read the instructions. I’m using the 1.3 version. Any clues?
EDIT: Nevermind. After installing a uPnP explorer I see that many devices on my network are not showing-up for some reason. Trying a device that the explorer found works in the Lan Device Monitor.
1 Like
thanks for sorting it
1 Like
Are these devices that are not showing up claiming to be UPnP compatible? Sometimes you have to explicitly enable it through a configuration option.
It’s probably my lack of understanding. I thought Xbox for eg was uPnP. I didn’t think you had to enable anything there. None of my Xboxes show up (not in the explorer either).
I use fing and it is not reporting the Xboxes (for example) as having the uPnP service.
All my Sonos, and two Yamaha receivers do show up.
I have had problems with my Xbox S too. LAN device monitor work just fine until few weeks ago. I couldn’t find uPnP also, but still managed to connect the device monitor with IP and MAC address. My Samsung tv has all the time worked flawlessly even with the faulty drive. But that one is the only device it LAN device monitor is working with right now. I’ll try the new driver asap.