Cant detect kasa plugs on network.

[alexsahka]

I was playing with the docker container (https://github.com/cbpowell/SenseLink/blob/master/docker-compose.yml) for the last 3 days. Here is my config file:

sources:
# MQTT
- mqtt:
    host: "10.xx.xx.xx"
    port: 1883
    username: xxxx
    password: xxxxxx
    plugs:
        - Posts_Lights:
            alias: "Posts Lights"
            mac: 53:75:31:f6:4d:00
            max_watts: 80
            state_topic: barrels_light_control/gpio03/state
            on_state_value: "1"
            off_state_value: "0"

Trying to detect this "virtual plug" on the network with NodeRed or Sense but can't find any plugs on my network.
Here is the log from docker:
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}
WARNING:root:Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}

Is this a normal log?

[cbpowell]

That message in itself is not abnormal, so I realize now that using a warning when it arrives is overkill. SenseLink listens for incoming requests with both get_realtime and get_sysinfo, which is what is sent by Sense when it broadcasts to all plugs (assuming that hasn’t changed). But it’s presumably possible for a device to query for just get_sysinfo - maybe some other smart home device like a Google Home?

So that message may not be indicative of problem with SenseLink, but it also won’t respond like a real TP-Link plug would to that specific incoming query (and you get that warning).

Regarding getting it to work, have you tried running the container with the debug log level? FYI setting SENSE_RESPONSE=False will also generate a response but not send it, which can be useful for testing and to avoid spamming your Sense meter.

[lymanepp]

Do you have plans to reduce the noise that this causes? My Home Assistant log is filled with them. I tracked them down with a packet capture and they are coming from my many Google Home speakers.
2021-09-30 16:26:34 INFO (MainThread) [root] Unexpected/unhandled message: {'system': {'get_sysinfo': {}}}

[cbpowell]

Thanks for the reminder! I just pushed version 1.2.7 that kicks that log message down to debug, which should hopefully help with clogging up the logs.

[lymanepp]

Thanks Charles!

Edit: I noticed that you added the source IP address for these messages. Good idea! That would've saved me some time.

[alexsahka]

Thank you for the reply.
Could you suggest how to "sense" Kasa plugs on the network?
Any tool? Need to troubleshoot my network.

[cbpowell]

Ah, are you unable to get any plug, real or virtual, to be detected by your Sense?

Sense sends out a UDP broadcast to port 9999 and expects a response on 9999 as well, so make sure you don’t have broadcasts or that port blocked or firewalled somehow. But a firewall is unlikely to be an issue here since generally, all plugs need to be on the same VLAN and subnet anyway.

In terms of tools the best I know of is Wireshark, but it has a little bit of a learning curve. You can use it to see traffic between devices. SenseLink with a debug log level will also report back when it gets a Sense broadcast, so you can use it to verify the broadcast is hitting your plugs, to some extent.

[cbpowell]

@alexsahka have you had any luck?

Side note, might move this to a Github Discussion as I don't think it's an issue with SenseLink specifically.