I think there is an issue with swap devices. When I look at the logs for the old device(sengled E1C-NB7 which uses generic outlet driver), it has the driver name of the new device (Tuya metering plug) in its logs.
I’m also fairly certain I’ve seen the “Device Data” also get corrupted when doing swap device, at least once. I swapped a Ledvance Zigbee A19 out, replaced with an Inovelli A19 bulb and the Inovelli had the device data from the Ledvance, but worked fine otherwise. I already deleted the devices, so no examples.
I haven’t used Swap in a long time - I can’t recall if I ran into some kind of issue at some point with it, or it just started to make me skittish risk-wise.
As tedious as it can sometimes be, I always just do a manual swap (using a temporary virtual device placeholder when necessary) – but at least that has never failed me, and I know for certain everything was covered.
Swap Device works by essentially swapping the device IDs at the database level (for supported devices). Logs are also identified by device ID. Therefore, when you swap an "old" and "new" device, you will indeed see logs from a previous life ... or at least I don't think it digs into the log files (which are not part of the database) to retroactively change anything. I think that's all you're seeing in the first screenshots, but correct me if I'm missing something.
There were some reported problems with this, maybe a couple years ago, that I believe were fixed at the time. I'm guessing your examples are newer than that, but I haven't seen anything recently. (I swear I saw something a couple builds ago where too little got swapped, but then I realized I was doing my favorite thing of reading "bedroom" instead of "bathroom" or something in the device name, so I started over from a backup, and all was good...only recent testing I've done. ) If you do find some examples, I'm sure they'd be welcome to pinpoint the issue!
) If you do find some examples, I'm sure they'd be welcome to pinpoint the issue!