ssdpTerm / upnp:rootdevice in hub events

I just started getting a bunch of these in my hub event logs. I understand what upnp and ssdp is for, but not what hubitat is using it for or what is causing it? Looking thru the other logs, nothing stands out.

As for network based apps, I have a few but nothing I could think of that requires upnp. Hue, Tplink kasa, echo speaks, etc.

There is nothing in hub events before these messages started besides system startup a few days ago.

These are generated when a hubitat app subscribes to upnp messages during a device discovery phase.
They should only be active during the device initial discovery.
Hubitats built in apps only run this for a few minutes, then shut it down.

I would look at whatever app was installed/activated when these messages started...

1 Like

I'll have to poke thru the logs and filter by time in order to narrow that down. Nobody was home when they started. I'm not sure if they're still continuing or not but I'll check tonight.

I can't find any apps or integrations that have log entries that match these ssdp ones.

They're still continuing. I also don't know if the events limit how many are in the log, but the ones I screenshotted from yesterday are gone but now have this mornings date/time on them.

Also for what it's worth, I dont think I'm having any issues or devices/apps not working.

From just now:

ssdpTerm upnp:rootdevice 2023-04-18 08:06:13.878 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:06:12.902 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:06:12.874 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:06:12.148 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:06:12.093 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:01:13.938 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:01:13.925 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:01:12.936 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:01:12.114 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 08:01:12.094 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:56:13.936 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:56:13.890 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:56:12.931 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:56:12.158 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:56:12.100 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:51:13.853 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:51:12.850 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:51:12.257 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:51:12.108 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:51:12.087 AM EDT
ssdpTerm upnp:rootdevice 2023-04-18 07:46:13.931 AM EDT

disable any lan integrations one by one, leave them off for 10 minutes, check logs, then do another one...
Or, look for a scheduled job in a lan app thats running every 5 minutes...

1 Like

At one point the Konnected integration would do similar logging to that (I haven't used it in a long time now, so can't verify current behavior). If you have that one,start there.

Ah ha! It's my Advanced Hue integration. I'm not sure why I don't ever remember seeing those log entries in the past unless there was an update to the app and I didn't notice it.

I had been checking hub events daily looking for zigbee stuff and don't ever recall seing these.

I'm assuming they're nothing to worry about?

3 Likes

Assuming that your Hue bridge isn't going to change IP addresses on you, then this job is unnessicary and is creating unnessicary lan and hub traffic.

Other than that, its fine...

2 Likes

Thanks. I'll open this conversation in the thread for the app.

3 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.