Integration doesn't work since Home Assistant version 2026.7.0

[iz8mbw]

Hello.
Since Home Assistant version 2027.7.0 the integration does not work correctly.

Thanks.

[kristofbriers]

I have the same problem

[mitzu2250]

Same here with 2 Tapo P110 .

[iz8mbw]

@petretiandrea

[paulraison]

I have the same issue on 1 device, but others working ok!

[Langelus]

Same here with L900's

[Fracap94]

All you need to do is delete the device and reconfigure it

[Danifly80]

All you need to do is delete the device and reconfigure it

This works for me but the entities will maybe change the name.

Thanks

[CorradoBarbero]

Same here

[smallfry42]

All you need to do is delete the device and reconfigure it

Worked here as well - TP-Link changed some entities around (with new Firmware), i guess that messed something up.

[CorradoBarbero]

My plug's firmware did not get any update, worked fine until I upgraded to 2026.7... smallfry42 left a comment (petretiandrea/home-assistant-tapo-p100#977) All you need to do is delete the device and reconfigure it Worked here as well - TP-Link changed some entities around (with new Firmware), i guess that messed something up. — Reply to this email directly, view it on GitHub , or unsubscribe . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android . Download it today! You are receiving this because you commented. Message ID: <petretiandrea/home-assistant-tapo-p100/issues/977/4868825640 @ github . com>

[Xcodo]

From a quick look, it seems that the config entry is updated to version 8 during migrations via

home-assistant-tapo-p100/custom_components/tapo/migrations.py

Line 14 in 7aa9ecb

async def migrate_entry_to_v8(hass: HomeAssistant, config_entry: ConfigEntry):

But the implementation of TapoConfigFlow has the current version set to 5.

home-assistant-tapo-p100/custom_components/tapo/config_flow.py

Line 97 in 7aa9ecb

class TapoConfigFlow(config_entries.ConfigFlow, domain=DOMAIN):

When the migration is triggered then the version check fails I think.

[Xcodo]

This likely surfaced due to this change in HA - home-assistant/core#173184, which validates the configuration version upstream.

[jojkopeter]

Same here with 4 Tapo P110 .

[cherowley]

Anyway to sort this without deleting device as have lots of automations etc on this p110 which will be a pain to redo?

[Langelus]

Anyway to sort this without deleting device as have lots of automations etc on this p110 which will be a pain to redo?

I had to redo 4 devices, all four came back with their previous entity ID's so no automations broken. Just note down the devicenames and rename them if that would not be the case for you