The integration does not detect the switch on the local network

[ksanya48]

The integration does not detect the switch on the local network
PS308G

[ksanya48]

2024-11-15 13:21:59.296 DEBUG (SyncWorker_7) [custom_components.sscpoe] SSCPOE_local_send: {'cmd': 'calludp', 'syn': '3AHwGLnH', 'data': {'callcmd': 'search'}}
2024-11-15 13:22:01.319 DEBUG (SyncWorker_7) [custom_components.sscpoe] SSCPOE_local_recv: Timeout
2024-11-15 13:22:03.090 INFO (MainThread) [habluetooth.scanner] hci0 (68:4E:05:4C:E2:70): Bluetooth scanner has gone quiet for 90s, restarting
2024-11-15 13:22:03.322 DEBUG (SyncWorker_7) [custom_components.sscpoe] SSCPOE_local_recv: Timeout

[slydiman]

Try to cancel and select Add SSCPOE device again. The integration may detect the local device on the 2nd or 3rd try.

Download Windows desktop config app and check that it detects PS308G locally.

Note the protocol uses multicast UDP. If your HA server has 2 or more external IPs (multiple network interfaces) it may be reason of this issue.

I see the device version 6.0.240630. I have tested PS308G and GPS204 with the firmware version 6.0.231024. Probably the developer changed something. First confirm that Windows desktop config app works. Then I need Wireshark traffic records during the searching procedure from Windows desktop config app to investigate what has been changed in the protocol.

[ksanya48]

I have tried to update the device many times (15-20 times). Today I will not be able to connect through the Windows application (there is no way)...Previously, I used local integration, but I needed to reinstall it... and after that, I can't set it up... I deleted it in hacs, reinstalled different versions, but there is no result

[slydiman]

Try to reboot the POE switch (power off/on).
If you cannot connect locally to the device using SSC Windows app, it means something is wrong with the device. Try reset it to factory settings via the smartphone app.

[alexander-saratovcev]

In case you are using iptables of ufw you need to allow multicast.
For example:

sudo ufw allow proto udp to 224.0.0.0/4

[Megachip]

Try to cancel and select Add SSCPOE device again. The integration may detect the local device on the 2nd or 3rd try.

Same here. Web interface is reachable. Any chance to enter IP manually? (Tested on unprovisioned, provisioned and cloud connected)

[slydiman]

Same here. Web interface is reachable.

Web interface of what? SSC devices with firmware v6.x have no any web interface.
If your SSC device is older, most probably it uses different local protocol.
Currently SSC devices use multicast UDP for local communications. Multicast UDP works only in the same subnet.

[Megachip]

Web interface of what? SSC devices with firmware v6.x have no any web interface.

That's not correct.

[slydiman]

That's not correct.

Ok, it seems

• SSC POE managed switches v2.0 have web UI.
• SSC POE managed switches v6.0.231024 have no web UI.
• SSC POE managed switches v6.0.2406xx have web UI again.

[Megachip]

@slydiman how can we help to fix the not detecting issue?

Installation method
Home Assistant OS
Core
2025.6.0
Supervisor
2025.05.5
Operating System
15.2
Frontend
20250531.2

[slydiman]

how can we help to fix the not detecting issue?

Did you try Windows app sscpoe? Can it detect the switch locally in the same network?

[Megachip]

how can we help to fix the not detecting issue?

Did you try Windows app sscpoe? Can it detect the switch locally in the same network?

Only the mobile ones, which working fine.

[slydiman]

Try the Windows sscpoe app first. If it does not work, then something is wrong with your network.
If the Windows app works, we can try to investigate the optimal TTL or other multicast UDP parameters.

All mobile apps work via the cloud.