The device
This issue is not requesting direct Hubspace support for Myko+ (Tuya-based) devices, but rather to track and document the loss of Home Assistant access caused by the Myko → Myko+ migration.
Specifically:
Once Myko devices migrate to Myko+, they are no longer visible to the Hubspace integration (expected, as Hubspace is Afero-based).
Myko+ bulbs do not appear to behave like standard Tuya bulbs:
after factory reset they blink a few times (e.g. yellow ↔ white for ~3–4 cycles) and then go solid,
they never enter a continuous EZ/AP pairing mode,
they cannot be discovered by Tuya Smart / Smart Life apps.
This makes it unclear whether any alternative HA integration path exists for bulbs after migration.
The intent of this issue is to:
provide a single reference point for users affected by the Myko+ migration,
document current pairing / reset behaviour of bulbs,
and capture any future findings or community workarounds, if they emerge.
Many users will be migrated around January, and devices may disappear from HA without explicit user action.
Features
N/A
Datadump
Not applicable at this stage.
The affected devices are no longer available via the Hubspace/Afero backend once migrated to Myko+, so no meaningful _dump_hs_devices.json can be generated post-migration.
Additional information
Related issues: #213 and #215 (Myko → Myko+ migration discussion), #212 (Myko smart plug context).
This issue is intended as a tracking / documentation issue, not a request for immediate implementation.
After migrating a single test bulb, I observed that additional bulbs appeared to migrate automatically, after which they disappeared from Home Assistant.
Even a documented “no current solution” outcome would be valuable to help set expectations and reduce repeated reports as the migration progresses.
The device
This issue is not requesting direct Hubspace support for Myko+ (Tuya-based) devices, but rather to track and document the loss of Home Assistant access caused by the Myko → Myko+ migration.
Specifically:
Once Myko devices migrate to Myko+, they are no longer visible to the Hubspace integration (expected, as Hubspace is Afero-based).
Myko+ bulbs do not appear to behave like standard Tuya bulbs:
after factory reset they blink a few times (e.g. yellow ↔ white for ~3–4 cycles) and then go solid,
they never enter a continuous EZ/AP pairing mode,
they cannot be discovered by Tuya Smart / Smart Life apps.
This makes it unclear whether any alternative HA integration path exists for bulbs after migration.
The intent of this issue is to:
provide a single reference point for users affected by the Myko+ migration,
document current pairing / reset behaviour of bulbs,
and capture any future findings or community workarounds, if they emerge.
Many users will be migrated around January, and devices may disappear from HA without explicit user action.
Features
N/A
Datadump
Not applicable at this stage.
The affected devices are no longer available via the Hubspace/Afero backend once migrated to Myko+, so no meaningful _dump_hs_devices.json can be generated post-migration.
Additional information
Related issues: #213 and #215 (Myko → Myko+ migration discussion), #212 (Myko smart plug context).
This issue is intended as a tracking / documentation issue, not a request for immediate implementation.
After migrating a single test bulb, I observed that additional bulbs appeared to migrate automatically, after which they disappeared from Home Assistant.
Even a documented “no current solution” outcome would be valuable to help set expectations and reduce repeated reports as the migration progresses.