Hubitat Kasa integration and single apostrophes in device names

📢 Feedback
1

The Kasa newly built-in integration does not know how to treat Kasa device names w/ single apostrophes properly.

e.g., "Peter's Device"

The integration and eventual device name replaces the single apostrophe w/ character graphics.

See the attached graphic:

Screen Shot 2022-09-24 at 7.06.42 PM
Screen Shot 2022-09-24 at 7.06.42 PM2032×1524 206 KB

2

Noted. When fixed, it will still replace the fancy character with the single apostrophe, but that will not be so visually jarring.

1 Like
3

one other possible item. I installed on my C-5 master hub, migrated, and checked that the devices were child devices (they were). About a day later, I went to add a device and noticed all the devices were open for installation and there are no children. In other words, I have 20 + orphaned Kasa devices. I will be checking this again today on my Test (C-7) Hub.

Updated: temporary recovery is to restore the backup prior to the time you migrated the Kasa Devices.

PS: I did this. Now, I will take a manual backup then try the migration again to verify (to me) it was not a transient case. Dave

4

Just verified that the Kasa Devices are orphaned. Steps:

  • Went back to earlier database version with custom integration.
  • Open built-in Kasa Integration and did a complete a Migrate
  • Closed then reopened the built-in Kasa Integration and verified the children were present.
  • Deleted custom app and drivers.
  • Six hour later, Open built-in and verified children were still present.
  • Did a reboot
  • Opened built-in and the Kasa devices were no longer listed (were orphaned).

C5 Hub running 2.3.3.122

5

Interesting...I have the same issue. C4, 2.3.3.122.

My virtual devices are still installed and working and have a 'system' type. So, they are the same virtual devices that I migrated from my previous installation of the custom integration.

I scanned for and located my Kasa devices in "Add" section of the built-in integration, but I didn't complete the install because I would worried that they would end up duplicated.

Maybe we should branch this "orphaned devices" discussion into a separate bug thread?

6

Possibly. But I suggest you go to a backup prior to the installation of 2.3.3.122. that will go back to the community integration. Then, wait a while until the staff resolves the issue.

7

On it.

2 Likes
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.