After being pretty steady for the last couple of releases, I'm getting daily zigbee off/on events again. (sigh)
But "ssdpTerm" is a new one on me. Can anyone tell me what this means?
UPNP reference seems to indicate that a LAN/Network-based integration may be involved.
Have you searched the forum for ssdpTerm? That'd be my first step.
Does this help?
Yes, thanks!
I'm guessing it was recreating the HomeKit interface.
(And sorry. I'm usually better at searching.)
1 Like
Fwiw, in my case it was the Advanced Hue Bridge Integration. There was a bug causing it to keep running discovery on a schedule. Armand pushed an update out this morning that fixed it.
1 Like
Hi All,
My hub is experiencing the same issue as shown in the attached snapshot. Hopefully, the new updated fix it.
Any suggestion would be appreciated. Thank you.
I've seen significantly fewer radio reboots w/.135. HE staff has said that having a reboot immediately after an update is not necessarily an indication of a problem, so hopefully your hub will also be calmer on .135 over time.
Hello danbw
Thank you. Indeed no more radio reboots for the last couple of days after the last upgrade.
Mine also was quiet for a day or two but the restarts have also returned on .135.
2 Likes
I had 3 restarts the day after the last update, then 2 days with no restarts, then 4 restarts yesterday. No idea what is causing it and no offline devices.
1 Like
Yeah, it's really hard to think of what could be triggering the reboots when they are so seemingly random.
I'm still loosing devices, recently mostly Samsung leak sensors for some reason, in very different parts of the house, in rooms at one end of the house from the other. Also had one Sengled classic white bulb that didn't need to be rejoined, just woked it up by turning power to the bulb off and then on again.
Oddly, the Iris motion sensors that had kept falling off until the most recent one on the fifth, have been OK since that day (going on three days now). I hate to even mention that, as the universe will likely punish me by kicking all my Iris v2 sensors off my mesh. 
2 Likes
It's really strange what drops,... My 5 Samsung leak detectors have all been problem-free, but both of my Yale lock ZB modules have started dropping recently. My Third Reality blinds have been troublemakers ever since the C8 release, but the Yale modules just started acting up in the last week.
Hopefully Mike and crew are getting closer to the bottom of all this!
Are you still at 8 for Zigbee power level? I don’t remember seeing you posting about dropped devices when you were at 16.
1 Like
I am at 12 now...my Zigbee power-level journey has been:
- 16 at migration (default)
- 8 at .130 (the release that dropped default power)
- 12 four days ago (~4th of May) upped the power back to 12 when I starting having problems on .135 pairing the Iris v2 motion sensors that were falling off - upping the power didn't help w/pairing. The significant pairing issues I've been having seem coincident w/ .135, but can't be sure of course.
I was actually losing devices prior to the power reduction in .130, the devices dropping off were likely more about the repeated radio reboots than the Zigbee power setting. As usual, hard to tell what's causing what.
I have been thinking about moving Zigbee power back up to 16 and see what happens w/the drop-offs, reboots, and pairing...if the Samsung leak sensors prefer to join directly to the hub, maybe that might make them happier? And I am getting overall fewer radio reboots on .135 (and they seem to cause fewer device drops) so maybe higher power and fewer reboots might for me be the right direction.
I think I've talked myself into trying 16 Zigbee power level again. May not help w/pairing issues if those are mainly .135 FW related.
2 Likes
Have you ever tried 4?
Not yet...next on my list after letting 16 settle for a few days, but not feeling like it will help given 8 wasn't a blazing success. 
1 Like
