The exact same thing reported by jlarkin0 happened. I have copied the results from my DOS command box and sent them in. The dump log indicates I am asking permission and then does nothing. Hopefully the log I emailed in will help.
But I think it best that I just return this thing to Amazon.
Would have been nice to have a look at it to see if my issue that I submitted yesterday goes into the right direction.
Maybe it’s better to ignore these threads and wait until Monday…
I reinstalled the Tapo P316M. Not sure if it used the updated driver from yesterday. I just used the same invite from yesterday (i did not see a different invite). The driver installed was 2026-07-27T22:06:19:87747052. I copied the CLI screen and sent the log to the email address build@smartthings.com.
Also, nothing changed. I still only got the one tile for outlet 1.
Hi, @jlarkin0
You need to enter the new link I shared, the driver’s version should show today’s date: 2026-07-28T18:24:45.345069056.
I suggest you go to the Advanced Users page > Hubs and enter the Hub’s details. Scroll down to the section of “Installed Drivers” and search the one called “Matter Switch”. Make sure you only have the version I mentioned above with the ID c8775dfd-48a7-496d-a987-5fd5aa0b7561, if you have others, please delete them to avoid the device getting connected to the wrong driver.
I sent in a dump an hour ago using the new driver; no change.
That said - my RMA has now been picked up, so I need to defer to JLARKIN0 to finish this up.
Make sure to delete my driver before adding the device. They need the logs from the PR channel driver.
CC: @trs80
The logs from my test driver Matter Switch P316M Test v0.2 confirm that SmartThings exposes the complete device structure:
Endpoint inventory: all=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12],
OnOff server=[1, 2, 3, 4, 5, 6],
Electrical Sensor=[7, 8, 9, 10, 11, 12],
default=1
The driver then creates the five missing outlet children:
Requesting child for OnOff EP 2 with profile plug-binary
Requesting child for OnOff EP 3 with profile plug-binary
Requesting child for OnOff EP 4 with profile plug-binary
Requesting child for OnOff EP 5 with profile plug-binary
Requesting child for OnOff EP 6 with profile plug-binary
After the electrical topology is received, all devices are upgraded to the final profile:
Tapo P316M Smart Power Strip 2: Updating device profile to plug-power-energy-powerConsumption
Tapo P316M Smart Power Strip 3: Updating device profile to plug-power-energy-powerConsumption
Tapo P316M Smart Power Strip 4: Updating device profile to plug-power-energy-powerConsumption
Tapo P316M Smart Power Strip 5: Updating device profile to plug-power-energy-powerConsumption
Tapo P316M Smart Power Strip 6: Updating device profile to plug-power-energy-powerConsumption
Finally, separate switch events are emitted for every child:
Tapo P316M Smart Power Strip 2: emitting event ... "value":"on"
Tapo P316M Smart Power Strip 3: emitting event ... "value":"on"
Tapo P316M Smart Power Strip 4: emitting event ... "value":"on"
Tapo P316M Smart Power Strip 5: emitting event ... "value":"on"
Tapo P316M Smart Power Strip 6: emitting event ... "value":"on"
So the test confirms that creating basic On/Off children before electrical profiling completes successfully restores all six outlets. The remaining power/energy reporting problem appears to be a separate issue.
Added a comment to the PR.
The original driver waits for electrical profiling to finish before creating the additional outlet devices. My driver creates the basic On/Off children immediately, prevents duplicate creation requests, and upgrades their profiles once the electrical topology is available.
Original flow
Wait for electrical profiling
↓
Enumerate On/Off endpoints
↓
Create child devices
↓
Assign final power/energy profiles
New flow
Enumerate On/Off endpoints
↓
Create basic On/Off child devices
↓
Complete electrical profiling
↓
Upgrade parent and child profiles
This ensures that valid, independently controllable outlets are not hidden just because electrical profiling is delayed or incomplete.
Ok. I sent the log with the correct driver - ID c8775dfd-48a7-496d-a987-5fd5aa0b7561.was sent. Still only get one outlet configured.
I deleted todays driver and installed Andreas 0.2 version. It worked. I now have 6 outlets installed, with 6 separate tiles. The tiles will turn on and off the correct outlet. However, the power usage data is not there.
The other thing was that for the CLI log the trace stopped after awhile. Whereas the other drivers just kept going and never stopped.
It should show up after a while, because profile switches take some time. If not, the original PR should fix that.
Hi, @jlarkin0
The team made another update to the SmartThings driver. Can you please install the driver from this invite and change your device to it?
The steps would be as follows:
2026-07-29T02:13:25.434076508Hello @nayelyz
I had already deleted the previous configuration and the driver v0.2 from Andreas. The tiles for each outlets never did show the power and energy usage.
So, I enrolled and installed the new device driver - 2026-07-29T02:13:25.434076508 (I confirmed that this is the driver being used). When I added the Tapo P316M Smartthings created 6 tiles, one for each of the outlets, which also include the power and energy usage for the outlet. As far as I can tell as a user everything is working as it should. Since the device was already configured within my Apple Matter Thread, to add the device I shared it from the Apple app and used the generated Matter code to add the power strip to Smartthings.
What is odd, is about 5 minutes after configuring the P316M, within Smartthings I get another popup to add the same power strip. I closed the popup, but if I “Scan nearby” for available devices the power strip shows up again as ready to install. The popup to add the device has not returned now after about 15 minutes, and when I “Scan nearby” again the power strip is no longer showing as ready to add. I assume pairing mode did not turn off immediately on install and that after 15 mins it turned off.
Thanks for everyones help.
Just thought I would let you know. I had a brand new Tapo P316M still in the box.
I went through the process of setting it up and adding it to Smartthings. I went as it should. Everything was very smooth. I correctly exited pairing mode once it was connected.
I have which each of my Tapo P316M back to using the Smartthing released Matter driver and everything is working fine.