Yes, I was at my friend house, then I wanted to show to another guy my setup, indirect sales, and I connected to my VPN and the hub did not respond. I looked my router and the hub was offline, well, I lost the sale, then I returned home, the hub has blue lights.
I rebooted everything, the hub, the switch, the router, connected the hub directly to the router, connected without USB stick, replaced the power supply.
It turns on the light red then blue but I can't connect to it, it's not connecting to the router.
You have a lot of views but no replies, so I thought I would post a response even if my knowledge is very limited. I have very similar logs on my hub, so I don't think what you are showing is an issue you need to be concerned with. I believe the logs are indicating other devices it sees on the network (possibly ones that are open or looking for a connection?) - mine shows my harmony hub and some others I don't immediately recognize. Could be wrong, but that's my guess.
Thanks, I found those logs are from konnected, I just commented the lines in the code to keep the log clear(not working, I need to look more later). Still asking why when I connected the hub directly to the router, I used another lan cable, but did not worked. I think it's impossible that both, the lan cable and power supply, were the cause of the lockout. Both went bad at the same time?
Edit: To answer my own question, the hub was not booting, I can see 4 logs of system start, but those are after I replaced the cables, this is so weird.
I have those logs as well and I believe it's from Lan devices. Pretty sure my logs came from my Phillips bridge when I was replacing it. Your log is most likely created when konnect and HE talking to each other after the hub connected to your Lan network. As for the Lan cable. Just try it on another device if you are curious.
As others have mentioned the ssdp logs are normal and are created when any ssdp device does a discovery request. When this happens, ALL device that support the ssdp protocol respond and show up in the logs. My list of devices is large so I see a full listing every time any device does a discovery. I also have Konnected, but disabled the discovery on all my nodemcu'ss to limit the amount of logging.
What concerns me about your screenshot is that every systemStart log is showing a different build. It seems like your hub may be detecting database corruption and trying to revert to different versions.
Only one of those is from Konnected. It's the one with Konnected in the urn name.
It's designed to run the SSDP discovery process every 5 minutes in the background. This is to refresh the IP address of the Konnected device(s) in case the IP address has changed due to DHCP leases expiring or a router reboot or something.
If you set an IP address reservation on your router for the Konnected device(s) then you can disable the periodic SSDP by commenting out that line in the Konnected-connect app.
Ohh well, now replacing the temporary cables the hub died again, I think I have a bad LAN port because the hub turns on. Tested the ST power supply and LAN cables again and hub is dead.
Tried different port on the switch? Tried a known good Ethernet cable that has been functioning on another device for a long time?
Not sure what you have for testing cables. Most continuity testers won’t give you enough information to detect bad connections in the RJ45 plug or a break in the cable that gives intermittent connections when flexed a certain way.
You looked in the hub RJ45 port with a flashlight to make sure none of the pins are misaligned?
Man that stinks. Hopefully a replacement hub with your existing usb stick and a database restore will get you fixed. This would have never been possible in ST land, hours of pain to get up and running again.
