ST Wifi Hub + Edge Discovery

@nayelyz Do you know the specifics on discovery of LAN devices with the Wifi hub? Do the devices need to be on the ST wifi subnet, or can they be connected as peer devices to the same network switch?

I have devices that are not discoverable when the driver is installed on a Wifi hub rather than the Aeotec Hub3

@TAustin Maybe you have run into this?

The last I’ve looked at this (and it’s been many months), it appeared that multicast messages weren’t getting out of these wifi hubs when sent by my Edge drivers. We proved this when I provided a network traffic monitoring app to someone who was having this problem, and running it on another LAN computer while the driver was in discovery mode showed that in fact no multicast network messages were getting out. Strange thing was that it seemed to be functional for Edge’s own scanning - just not for a community-developed driver.

1 Like

In your case, how were the devices connected?

  1. Wifi devices connected to the wifi network created by the ST wifi hub (child)
  2. Hardline connected directly to the ST wifi hub (child)
  3. Hardline connected to the same network switch as the ST wifi hub (peer)

I’m not 100% sure since it’s been a while; I’ll try to find the original message exchange.

Found the discussion thread and invited you to it so you can see all the progression. He was trying to discover his Roku devices using one of my drivers. So they would definitely have been wifi devices, presumably connected to his wifi router, as was the SmartThings hub. But we couldn’t see any multicast traffic initiated by the driver coming from the hub.

This was a year ago, and still unresolved.

1 Like

I’m glad to see a light shine thru these issue. I’m one of the ST Wifi users who can’t use any LAN edge drivers (Hue, Lifx, Kasa, Harmony). Hope to see some progress in this issue, does the ST team knows about this?

1 Like

Hoping to get them into this thread. I would like to know which setups are supported for LAN discovery on this hub.

Is there any news on this? I’ve been told that LAN base edge drivers already work with the ST Wifi Hub, and I successfully installed an Harmony Hub driver and is working, but I’m still having trouble discovering my Hue Hub using @blueyetisoftware awesome driver.

Any thoughts?

This is the error I’m having:

2023-07-15T18:35:54.392540281+00:00 DEBUG Philips Hue Beta discovery sending broadcast
2023-07-15T18:36:02.756743543+00:00 ERROR Philips Hue Beta discovery thread encountered error: [string “discovery.lua”]:263: bad argument #3 to ‘format’ (number expected, got nil)

Send me the log, and I’ll take a look. You are the first one to actually get a log. Try to get more of the log before and after. Thanks.

I already have been able to discover the Hue Hub using your driver, but it stays offline and i can linked pressing the button (the hub device is gray out in the ST app) I have rebooted the ST hub and Hue hub a couple of times already (the hue bub has a port reservation if thats important) but the CLI says it scanning for the brigde an nothing happens.

Here is part of the log:

2023-07-16T01:58:40.769248908+00:00 TRACE Philips Hue Beta Received event with handler environment_info
2023-07-16T01:58:40.775545408+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T01:58:40.783405554+00:00 DEBUG Philips Hue Beta Philips hue device thread event handled
2023-07-16T01:58:40.784482991+00:00 TRACE Philips Hue Beta Received event with handler environment_info
2023-07-16T01:58:40.785509366+00:00 DEBUG Philips Hue Beta Z-Wave hub node ID environment changed.
2023-07-16T01:58:40.788965262+00:00 TRACE Philips Hue Beta Found DeviceLifecycleDispatcher handler in Hue
2023-07-16T01:58:40.789601221+00:00 TRACE Philips Hue Beta Found CapabilityCommandDispatcher handler in Hue
2023-07-16T01:58:40.790601471+00:00 WARN Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> offline
2023-07-16T01:58:40.791563950+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> resolving address for bridge
2023-07-16T01:58:40.794797137+00:00 DEBUG Philips Hue Beta Philips hue device thread event handled
2023-07-16T01:58:40.796288991+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T01:58:46.398318819+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T01:58:58.305129183+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T01:59:18.799570476+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T01:59:40.787525976+00:00 DEBUG Philips Hue Beta session 30: uptime 0 minutes, memory 629 KB
2023-07-16T01:59:40.793512413+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T01:59:59.854208458+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T02:00:40.800757856+00:00 DEBUG Philips Hue Beta session 30: uptime 1 minutes, memory 629 KB
2023-07-16T02:00:40.805898502+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:01:20.238555527+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T02:01:40.812659841+00:00 DEBUG Philips Hue Beta session 30: uptime 2 minutes, memory 629 KB
2023-07-16T02:01:40.817998716+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:02:40.815473617+00:00 DEBUG Philips Hue Beta session 30: uptime 3 minutes, memory 629 KB
2023-07-16T02:02:40.820662117+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:03:40.819043184+00:00 DEBUG Philips Hue Beta session 30: uptime 4 minutes, memory 629 KB
2023-07-16T02:03:40.829230914+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:03:58.657089459+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T02:04:40.830969794+00:00 DEBUG Philips Hue Beta session 30: uptime 5 minutes, memory 629 KB
2023-07-16T02:04:40.838684211+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:05:40.825034632+00:00 DEBUG Philips Hue Beta session 30: uptime 6 minutes, memory 629 KB
2023-07-16T02:05:40.831369403+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:06:40.833640804+00:00 DEBUG Philips Hue Beta session 30: uptime 7 minutes, memory 629 KB
2023-07-16T02:06:40.840640742+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:07:40.819547935+00:00 DEBUG Philips Hue Beta session 30: uptime 8 minutes, memory 629 KB
2023-07-16T02:07:40.822882643+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:08:40.844156419+00:00 DEBUG Philips Hue Beta session 30: uptime 9 minutes, memory 629 KB
2023-07-16T02:08:40.862974086+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:09:17.203753718+00:00 DEBUG Philips Hue Beta <Device: caba9b2b-7296-4252-b5cc-bbe22f3a61ca (Philips hue)> scanning for bridge on network
2023-07-16T02:09:40.858473508+00:00 DEBUG Philips Hue Beta session 30: uptime 10 minutes, memory 629 KB
2023-07-16T02:09:40.860943924+00:00 DEBUG Philips Hue Beta driver device thread event handled
2023-07-16T02:10:40.854697821+00:00 DEBUG Philips Hue Beta session 30: uptime 11 minutes, memory 629 KB
2023-07-16T02:10:40.878190999+00:00 DEBUG Philips Hue Beta driver device thread event handled

I determined that this was caused because your Hue hub responded with a packet that didn’t include its ID. This is an issue in the Hue hub side. It could be a bad packet from them, or it could be some other device on your network that is inappropriately responding to the broadcast for Hue devices.