Fatal error in Matter Switch driver (2025-08-04) involving Matter plugs

Devices & Integrations
1

Critical error for users with Matter (1.3?) smart plugs, including Eve Energy and Tapo P110M!

I’ve been able to replicate a fatal error that crashes the matter-switch driver and might be related to this issue reported by a Tapo P110M user and this issue here with Matter devices, that renders the plug and every other Matter light, switch or plug unusable. Mind the P110M got a Matter 1.3 update few days ago for energy monitoring that might be related, same happens with Eve Energy, both using Matter 1.3 energy reporting.

I can replicate it by switching back from another driver (in this case my Matter Playground driver), but the user says he didn’t use my driver so it’s just a SmartThings stock drivers bug triggered by yesterday’s update.

I don’t experience the issue if my Matter 1.3 plugs like the P110M or Eve Energy use my driver instead of stock so must be related to plug specific features since some Matter lights using the stock driver work fine. As soon as one of the plugs uses the stock driver, the stock driver crashes.

2025-08-05T10:14:12.543415737Z FATAL Matter Switch  runtime error: [string "cosock.lua"]:252: Unable to serialize datastore value: deserialize error: invalid type: integer `2`, expected a string key
stack traceback:
        [C]: in field 'st_json_encode'
        [string "json"]:25: in function <[string "json"]:25>
        [C]: in function 'pcall'
        [string "third_party.coxpcall.coxpcall"]:50: in global 'pcall'
        [string "datastore.lua"]:112: in upvalue 'do_save'
        [string "datastore.lua"]:120: in function <[string "datastore.lua"]:117>

stack traceback:
        [C]: in function 'error'
        [string "datastore.lua"]:130: in upvalue 'do_save'
        [string "datastore.lua"]:120: in function <[string "datastore.lua"]:117>
stack traceback:
        [C]: in function 'error'
        [string "cosock.lua"]:252: in upvalue 'step_thread'
        [string "cosock.lua"]:360: in field 'run'
        [string "st/driver.lua"]:1143: in method 'run'
        [string "init.lua"]:1751: in main chunk

I’ve dumped the logs so you can look at it, assuming it’s the same issue experienced by others. In the logs you can see “Enchufe Tapo” working fine with my driver, then switching and the matter-switch driver crashing.

Tagging @Itati and @nayelyz

As a workaround for users with Matter 1.3 smart plugs like Eve Energy or Tapo P110M units, I would recommend switching them all to my driver, at least until the stock drivers are fixed. Otherwise the stock driver will keep restarting, affecting all the other Matter lights / switches / plugs.

1 Like
2

They are working on it reverting changes to energy profiling

3 Likes
3

I’m also seeing the same issue with the matter driver from 4th August that my TP Link P110M devices are not responding to command however they are working fine with Apple Home Kit via Matter.

1 Like
4

Hi everyone,

Our team is currently reviewing the issue and working on a fix. As soon as we have any updates, we will notify you here.

2 Likes
5

I hope he gets a V4 hub for finding this bug.

1 Like
6

The hotfix has been pushed to both beta and production so it’s a matter of time the matter-switch driver updates and devices work again.

1 Like
7

Hi everyone,

The issue should now be resolved. You should see the fix automatically within the next 12 hours.
If you’d like to get the update sooner, performing a hub reboot will apply the fix immediately.

1 Like
8

Is anybody still facing similiar issues like this? I suspect that at least I am…

I am using the standard Aeotec V3 hub. Apart from the hub, my SmartThings system consists of the following Matter-based components:

  • 3 Eve Energy plugs (Matter-over-Thread)
  • 3 Shelly Gen4 switches (Matter-over-WiFi)
  • 7 Sense by MACO contact sensors (Matter-over-Thread)

In addition, I have integrations with Sonos and Tapo running.

For the last couple of weeks, I have experienced some strange problems with my SmartThings system, sometimes showing all (!) sensors offline, while the smart plugs are not displayed as offline - yet still, not working. Controlling of any of these smart plugs failed - if I tried to switch it on or off through the app, nothing happened - but their state did not change to offline.

After rebooting the SmartThings hub, all components returned back to the system again - with everything again running stable for sometimes a couple of days, sometimes only a couple of hours. I have experienced this issue now at least 4 or 5 times, with the last time happening just yesterday? I doubt that this has anything to do with the range of the Eve Energy plugs - and even if it had, they should be consequently shown as offline if they were not able to communicate with the system?