Tapo P316M energy monitoring power strip support

[TheLinuxGuy]

I purchased a Tapo P316M and it looks like it cannot be discovered or used with this library, my other smart plugs work fine but not this one.

Took the discovery example and using my credentials, it failed to work with http://192.168.66.240:80/app which is the P316M

Firmware version: 1.0.5 Build 250306 Rel.151943
Hardware version: v1.6

Output of discovery with removed successful entries for the P115s that work fine.

:~/plugp100# uv run plugp100/discovery.py 
ERROR:root:Failed to update 192.168.66.240 SMART.TAPOPLUG
Traceback (most recent call last):
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 71, in send_request
    if response := await self._send_request(request, retry):
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 84, in _send_request
    self._klap_session = await self.perform_handshake()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 122, in perform_handshake
    if seeds := await self.perform_handshake1():
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 207, in perform_handshake1
    raise Exception(
Exception: Server response doesn't match our challenge on url http://192.168.66.240:80/app

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 71, in send_request
    if response := await self._send_request(request, retry):
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 84, in _send_request
    self._klap_session = await self.perform_handshake()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 122, in perform_handshake
    if seeds := await self.perform_handshake1():
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 207, in perform_handshake1
    raise Exception(
Exception: Server response doesn't match our challenge on url http://192.168.66.240:80/app

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 71, in send_request
    if response := await self._send_request(request, retry):
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 84, in _send_request
    self._klap_session = await self.perform_handshake()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 122, in perform_handshake
    if seeds := await self.perform_handshake1():
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 207, in perform_handshake1
    raise Exception(
Exception: Server response doesn't match our challenge on url http://192.168.66.240:80/app

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/plugp100/plugp100/discovery.py", line 11, in example_discovery
    await device.update()
  File "/root/plugp100/plugp100/plugp100/new/tapodevice.py", line 60, in update
    components = await self._negotiate_components()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/new/tapodevice.py", line 182, in _negotiate_components
    return (await self.client.get_component_negotiation()).get_or_raise()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/common/functional/tri.py", line 159, in get_or_raise
    raise self.value
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 71, in send_request
    if response := await self._send_request(request, retry):
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 84, in _send_request
    self._klap_session = await self.perform_handshake()
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 122, in perform_handshake
    if seeds := await self.perform_handshake1():
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/plugp100/plugp100/plugp100/protocol/klap/klap_protocol.py", line 207, in perform_handshake1
    raise Exception(
Exception: Server response doesn't match our challenge on url http://192.168.66.240:80/app

[mihai-dinculescu]

@TheLinuxGuy, the code you shared appears to be from a different library: https://github.com/petretiandrea/plugp100.

Have you tested the tapo library from this repository? It might be worth experimenting with the P304M code path to check if that works.

[TheLinuxGuy]

Apologies @mihai-dinculescu - how about the below? I have not used rust before but I believe I gotten it installed and followed the instructions properly.

The protocol error it complains about is similar to the issue I am seeing in other python libraries for this device, so I wonder if TP-Link/Tapo changed their source ocde and how their device works.

What do you see from this error? The credentials are fine because I use the same environment variables for P115 at bottom.

root@kasapi:~/tapo# export IP_ADDRESS="192.168.66.240"
root@kasapi:~/tapo# cargo run --example tapo_p300
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.43s
     Running `target/debug/examples/tapo_p300`
 2025-07-22T15:00:10.767Z WARN  tapo::api::protocol::klap_protocol > Local hash does not match server hash
Error: Tapo(InvalidCredentials)

P115 success

 2025-07-22T15:04:45.128Z WARN  tapo::api::protocol::klap_protocol > Local hash does not match server hash
Error: Tapo(InvalidCredentials)
root@kasapi:~/tapo# export IP_ADDRESS="192.168.66.241"
root@kasapi:~/tapo# cargo run --example tapo_p110
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/examples/tapo_p110`
 2025-07-22T15:05:01.730Z INFO  tapo_p110 > Turning device on...
 2025-07-22T15:05:01.755Z INFO  tapo_p110 > Waiting 2 seconds...
 2025-07-22T15:05:03.755Z INFO  tapo_p110 > Turning device off...
 2025-07-22T15:05:03.974Z INFO  tapo_p110 > Device info: DeviceInfoPlugEnergyMonitoringResult { device_id: "x", type: "SMART.TAPOPLUG", model: "P115", hw_id: "x", hw_ver: "1.0", fw_id: "00000000000000000000000000000000", fw_ver: "1.1.3 Build 240523 Rel.175054", oem_id: "x", mac: "xyz", ip: "192.168.66.241", ssid: "Gspot", signal_level: 3, rssi: -43, specs: "US", lang: "en_US", device_on: false, on_time: 0, nickname: "Topo4 FW", avatar: "plug", has_set_location_info: false, region: Some("America/New_York"), latitude: Some(-1879048193), longitude: Some(-1879048193), time_diff: Some(-300), default_states: DefaultPlugState { type: LastStates, state: PlugState { on: None } }, overcurrent_status: Normal, overheat_status: Some(Normal), power_protection_status: Normal, charging_status: Normal }
 2025-07-22T15:05:04.075Z INFO  tapo_p110 > Device usage: DeviceUsageEnergyMonitoringResult { time_usage: UsageByPeriodResult { today: Some(665), past7: Some(2606), past30: Some(32230) }, power_usage: UsageByPeriodResult { today: Some(0), past7: Some(0), past30: Some(5370) }, saved_power: UsageByPeriodResult { today: Some(665), past7: Some(2606), past30: Some(26860) } }
 2025-07-22T15:05:04.088Z INFO  tapo_p110 > Current power: CurrentPowerResult { current_power: 0 }
 2025-07-22T15:05:04.136Z INFO  tapo_p110 > Energy usage: EnergyUsageResult { local_time: 2025-07-22T11:05:03, current_power: 0, today_runtime: 665, today_energy: 0, month_runtime: 20710, month_energy: 3256 }
 2025-07-22T15:05:04.161Z INFO  tapo_p110 > Energy data (hourly): EnergyDataResult { local_time: 2025-07-22T11:05:03, data: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], start_timestamp: 1753156800, end_timestamp: 1753243199, interval: 60 }
 2025-07-22T15:05:04.202Z INFO  tapo_p110 > Energy data (daily): EnergyDataResult { local_time: 2025-07-22T11:05:03, data: [267, 266, 267, 267, 267, 264, 265, 268, 271, 257, 192, 256, 149, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], start_timestamp: 1751342400, end_timestamp: 1751342400, interval: 1440 }
 2025-07-22T15:05:04.305Z INFO  tapo_p110 > Energy data (monthly): EnergyDataResult { local_time: 2025-07-22T11:05:03, data: [0, 0, 459, 100, 5097, 6703, 3256, 0, 0, 0, 0, 0], start_timestamp: 1735707600, end_timestamp: 1735707600, interval: 43200 }
root@kasapi:~/tapo# 

[mihai-dinculescu]

It appears that P316M is using a different authentication method, unfortunately.

Can you also please try this library? AFAIK, it supports a few more auth methods.

[rytilahti]

With the python-kasa tool, you can add --debug to show the raw responses (kasa --debug discover`). It would be useful to know the discovery response as it contains the encryption parameters.

[TheLinuxGuy]

@rytilahti ok here is python-kasa library.

root@kasapi:~/python-kasa# uv run kasa --debug --username xx --password "xx" --host 192.168.66.240 discover
Discovering device 192.168.66.240 for 10 seconds
DEBUG:kasa.discover:[DISCOVERY] 192.168.66.240 >> {'system': {'get_sysinfo': {}}}
DEBUG:kasa.discover:Waiting a total of 10 seconds for responses...
DEBUG:kasa.device_factory:Using SmartDevice for SMART.TAPOPLUG
DEBUG:kasa.device_factory:Finding protocol for 192.168.66.240
DEBUG:kasa.device_factory:Finding protocol for DeviceFamily.SmartTapoPlug
DEBUG:kasa.device_factory:Finding transport for SMART.KLAP
DEBUG:kasa.transports.klaptransport:Created KLAP transport for 192.168.66.240
DEBUG:kasa.discover:[DISCOVERY] 192.168.66.240 << {'error_code': 0,
 'result': {'device_id': 'REDACTED_7660474ec87754b192de851',
            'device_model': 'P316M(US)',
            'device_type': 'SMART.TAPOPLUG',
            'factory_default': False,
            'ip': '192.168.66.240',
            'is_support_iot_cloud': True,
            'mac': 'A8-29-48-00-00-00',
            'mgt_encrypt_schm': {'encrypt_type': 'KLAP',
                                 'http_port': 80,
                                 'is_support_https': False,
                                 'lv': 2},
            'obd_src': 'tss',
            'owner': 'REDACTED_9B39D2FAC3B5C9FCBA4CA81',
            'protocol_version': 1}}
DEBUG:kasa.device:Initializing 192.168.66.240 of type <class 'kasa.smart.smartdevice.SmartDevice'>
DEBUG:kasa.protocols.smartprotocol:192.168.66.240 multi-request-batch-1-of-1 >> '{"method":"multipleRequest","request_time_milis":1753295863088,"terminal_uuid":"rqCpBJQIFKS1/FYwZRAjng==","params":{"requests":[{"method":"component_nego"},{"method":"get_device_info"},{"method":"get_connect_cloud_state"}]}}'
DEBUG:kasa.transports.klaptransport:Starting handshake with 192.168.66.240
DEBUG:kasa.httpclient:Posting to http://192.168.66.240/app/handshake1
DEBUG:kasa.transports.klaptransport:Handshake1 posted at 2025-07-23 14:37:43.119547. Host is 192.168.66.240, Response status is 200, Request was 20708b23c4238cf0ce6da978d69f6e6e
DEBUG:kasa.transports.klaptransport:Handshake1 success at 2025-07-23 14:37:43.119597. Host is 192.168.66.240, Server remote_seed is: fff7df5db632df5ff316dd5f5734dd5e, server hash is: 06a480a245ab224d4875bc8fdcd75a68dc0ebf1a61818f5e194bcb5adc5eb3b0
DEBUG:kasa.transports.klaptransport:Device response did not match our challenge on ip 192.168.66.240, check that your e-mail and password (both case-sensitive) are correct. 
DEBUG:kasa.protocols.smartprotocol:Unable to authenticate with 192.168.66.240, not retrying: Device response did not match our challenge on ip 192.168.66.240, check that your e-mail and password (both case-sensitive) are correct. 
== Authentication failed for device ==
	== Discovery Result ==
	Device Type:        SMART.TAPOPLUG
	Device Model:       P316M(US)
	IP:                 192.168.66.240
	MAC:                A8-29-48-1C-EB-5D
	Device Id (hash):   d95ba05ca7660474ec87754b192de851
	Owner (hash):       xx
	Supports IOT Cloud: True
	OBD Src:            tss
	Encrypt Type:       KLAP
	HTTP Port:          80
	Login version:      2


root@kasapi:~/python-kasa# 

[rytilahti]

This device should be supported. The problem is the way it has been bound to your WiFi (odb source tss). I don't think any of the known open source libraries have reversed this one.

It is some sort of provisioning protocol, where existing tplink devices are used to do the binding, and that's why the credentials hash does not match your inputted credentials. https://www.home-assistant.io/integrations/tplink#troubleshooting has a bullet point explaining how you can try to fix it.

Hope that helps, if you manage to get it working, please do contribute a fixture file to python-kasa as per their docs :-)

[TheLinuxGuy]

@rytilahti thanks a bunch for the pointers and calling out that OBD Src: tss is an indicator of the issue. I have been able to get further but still not able to pull emeter or power consumption info from it. Any ideas?

How I got here?

I have removed all the TP-link devices from the wifi, factory reset the P316M. Then set it up again (app asked for wiif password).

root@kasapi:~/python-kasa# uv run kasa --username xx --password "xy" discover
Discovering devices on 255.255.255.255 for 10 seconds
== None - P316M ==
Host: 192.168.66.240
Port: 80
Device state: False
Time:         2025-07-23 17:54:19-04:00 (tz: America/New_York)
Hardware:     1.6 (US)
Firmware:     1.0.5 Build 250306 Rel.151943
MAC (rssi):   A8:29:48:1C:EB:5D (-47)

== Primary features ==

== Information ==
Signal Level (signal_level): 3
Cloud connection (cloud_connection): True
Update available (update_available): None
Check latest firmware (check_latest_firmware): <Action>

== Configuration ==
Auto update enabled (auto_update_enabled): True
LED (led): True

== Debug ==
Device ID (device_id): xyz
RSSI (rssi): -47 dBm
SSID (ssid): Gspot
Reboot (reboot): <Action>
Device time (device_time): 2025-07-23 17:54:19-04:00
Current firmware version (current_firmware_version): 1.0.5 Build 250306 Rel.151943
Available firmware version (available_firmware_version): None
Matter setup code (matter_setup_code): xx
Matter setup payload (matter_setup_payload): MT:xx

== Children ==

	== Smart Plug 1 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 0.0 W
	Voltage (voltage): 120.7 V
	Current (current): 0.0 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.0 kWh
	This month's consumption (consumption_this_month): 0.0 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>

	== Smart Plug 2 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 0.0 W
	Voltage (voltage): 120.6 V
	Current (current): 0.0 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.0 kWh
	This month's consumption (consumption_this_month): 0.0 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>

	== Smart Plug 3 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 37.6 W
	Voltage (voltage): 119.8 V
	Current (current): 0.33 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.007 kWh
	This month's consumption (consumption_this_month): 0.007 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>

	== Smart Plug 4 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 2.1 W
	Voltage (voltage): 120.3 V
	Current (current): 0.09 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.0 kWh
	This month's consumption (consumption_this_month): 0.0 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>

	== Smart Plug 5 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 0.0 W
	Voltage (voltage): 120.4 V
	Current (current): 0.0 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.0 kWh
	This month's consumption (consumption_this_month): 0.0 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>

	== Smart Plug 6 (P316M) ==

	== Primary features ==
	State (state): True
	Current consumption (current_consumption): 0.0 W
	Voltage (voltage): 120.3 V
	Current (current): 0.0 A

	== Information ==
	Auto off at (auto_off_at): None
	Today's consumption (consumption_today): 0.0 kWh
	This month's consumption (consumption_this_month): 0.0 kWh
	Overloaded (overloaded): False

	== Configuration ==
	Auto off enabled (auto_off_enabled): False
	Auto off in (auto_off_minutes): 120 min (range: 0-65536)
	Unable to read value (power_protection_threshold): 'enabled'

	== Debug ==
	Device ID (device_id): xyz
	On since (on_since): 2025-07-23 17:42:08-04:00
	Reboot (reboot): <Action>


Found 1 devices

Interestingly though this script which uses the same python-kasa library=0.10.2 doesn't seem to be finding the power metrics? I wonder if you may have any pointers.

kasa-collector  | 2025-07-23T21:52:46.489580000Z 2025-07-23 17:52:46 [INFO] KasaAPI Discovered 1 devices
kasa-collector  | 2025-07-23T21:52:46.497589000Z 2025-07-23 17:52:46 [INFO] KasaCollector Discovered 1 devices.
kasa-collector  | 2025-07-23T21:52:46.497628000Z 2025-07-23 17:52:46 [DEBUG] KasaCollector Device discovery completed in 5.02 seconds.
kasa-collector  | 2025-07-23T21:52:46.497675000Z 2025-07-23 17:52:46 [DEBUG] KasaCollector Next device discovery will run at 2025-07-23 17:57:46.
kasa-collector  | 2025-07-23T21:52:56.636171000Z 2025-07-23 17:52:56 [DEBUG] KasaCollector Starting emeter data fetch for 0 devices.
kasa-collector  | 2025-07-23T21:52:56.636533000Z 2025-07-23 17:52:56 [DEBUG] KasaCollector Emeter data fetch completed for 0 devices in 0.00 seconds.
kasa-collector  | 2025-07-23T21:52:56.636753000Z 2025-07-23 17:52:56 [DEBUG] KasaCollector Next emeter data fetch will run at 2025-07-23 17:53:11.
kasa-collector  | 2025-07-23T21:53:11.662066000Z 2025-07-23 17:53:11 [DEBUG] KasaCollector Starting emeter data fetch for 0 devices.
kasa-collector  | 2025-07-23T21:53:11.662315000Z 2025-07-23 17:53:11 [DEBUG] KasaCollector Emeter data fetch completed for 0 devices in 0.00 seconds.

[TheLinuxGuy]

OK, maybe we will just move this discussion to python-kasa python-kasa/python-kasa#1558 (comment)

Thanks @mihai-dinculescu

[TheLinuxGuy]

I fixed the TSS provisioning issue that @rytilahti schooled me about, so now that device auth is working we can see what else is not working.

This library also sees similar issues to the problems I am seeing on python-kasa - the API responses are different than expected, leading to issues like:

root@kasapi:~/tapo# cargo run --example tapo_p300
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/examples/tapo_p300`
 2025-07-24T17:18:11.172Z INFO  tapo_p300 > Device info: DeviceInfoPowerStripResult { device_id: "REDACTED", type: "SMART.TAPOPLUG", model: "P316M", hw_id: "2379878FD20427DA56CDE7809167A79E", hw_ver: "1.6", fw_id: "00000000000000000000000000000000", fw_ver: "1.0.5 Build 250306 Rel.151943", oem_id: "REDACTED", mac: "REDACTED", ip: "192.168.66.240", ssid: "Gspot", signal_level: 3, rssi: -46, specs: "US", lang: "en_US", avatar: "", has_set_location_info: false, region: Some("America/New_York"), latitude: Some(-x), longitude: Some(x), time_diff: Some(-300) }
 2025-07-24T17:18:11.172Z INFO  tapo_p300 > Getting child devices...
Error: Serde(Error("missing field `overheat_status`", line: 1, column: 900))

I did do a data dump and PR for python-kasa which I think includes a data dump .json from this new device. Maybe that helps fix the issue for mihai-dinculescu/tapo library? Feel free to take a look at: https://github.com/python-kasa/python-kasa/pull/1561/files#diff-e8b35588354a73dd0b19bee5dbf970d3805ef4ea87b07cc1b3c3394a7a93163b

[mihai-dinculescu]

Thank you for the info about TSS, @rytilahti .

Thank you for the fixture, @TheLinuxGuy .

Version v0.8.3 now includes basic support for the P316M. Energy usage isn’t available yet, but I plan to add it once I've made more headway on current WIP items.

I’d also love to hear what additional functionality you're hoping for!

[TheLinuxGuy]

I can confirm that basic on/off power support works on P316M. Notes below... local self-hosted energy monitoring telemetry data retrieval is the primary goal I am trying to do, as the power strip intends to measure the electricity consumed by my homelab network devices.

 24 files changed, 188 insertions(+), 72 deletions(-)
root@kasapi:~/tapo# cargo run --example tapo_p300
   Compiling tapo v0.8.3 (/root/tapo/tapo)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 12.98s
     Running `target/debug/examples/tapo_p300`
 2025-07-25T19:21:45.922Z INFO  tapo_p300 > Device info: DeviceInfoPowerStripResult { device_id: "x", type: "SMART.TAPOPLUG", model: "P316M", hw_id: "x", hw_ver: "1.6", fw_id: "00000000000000000000000000000000", fw_ver: "1.0.5 Build 250306 Rel.151943", oem_id: "x", mac: "A8-29-48-1C-EB-5D", ip: "192.168.66.240", ssid: "Gspot", signal_level: 3, rssi: -46, specs: "US", lang: "en_US", avatar: "", has_set_location_info: false, region: Some("America/New_York"), latitude: Some(-xx), longitude: Some(-xx), time_diff: Some(-300) }
 2025-07-25T19:21:45.922Z INFO  tapo_p300 > Getting child devices...
 2025-07-25T19:21:45.995Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 1, id: REDACTED900, state: true.
 2025-07-25T19:21:46.076Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:21:46.090Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:48.090Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:21:48.186Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:50.186Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 2, id: REDACTED901, state: true.
 2025-07-25T19:21:50.265Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:21:50.276Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:52.276Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:21:52.374Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:54.374Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 3, id: REDACTED902, state: true.
 2025-07-25T19:21:54.446Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:21:54.462Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:56.462Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:21:56.557Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:21:58.557Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 4, id: REDACTED903, state: true.
 2025-07-25T19:21:58.637Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:21:58.652Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:22:00.652Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:22:00.740Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:22:02.740Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 5, id: REDACTED904, state: true.
 2025-07-25T19:22:02.826Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:22:02.848Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:22:04.848Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:22:04.944Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:22:06.944Z INFO  tapo_p300 > Found plug with nickname: Smart Plug 6, id: REDACTED905, state: true.
 2025-07-25T19:22:07.062Z INFO  tapo_p300 > Turning device on...
 2025-07-25T19:22:07.073Z INFO  tapo_p300 > Waiting 2 seconds...
 2025-07-25T19:22:09.074Z INFO  tapo_p300 > Turning device off...
 2025-07-25T19:22:09.179Z INFO  tapo_p300 > Waiting 2 seconds...