IKEA Inspelning : Metering Not polling/Slow polling

[ABEIDO]

The problem

Im having a really strange 2 issues with my IKEA Inspelning via ZHA.

I have 8 of them and the power switch in all 8 is working fine. 3 purchased 6 months ago and 5 purchased 2 weeks back.

Restart No Polling
After HA restart 4 of them stops updating the power usage and doesnt really add to the summation entity.
If i press reconfigure on those 4 they start updating again but slower than the other working 4. If i restart HA again they stop measuring again.

Slow polling
After reconfigure the 4 plugs with problems polls way slow than the working ones.
Then ones working polls every 5-10 secs on average and works on restart
The other ones polls every 15-40 secs on average but only after presseing reconfigure after restart

TS

• All plugs is running latest firmware 2.4.45 / 0x02040045
• 1 plug ha been working fine since 6 months and started having this issue now.
• Ive waited several hours for them to start measuring by themselves but no go.
• Removed plugs from ZHA , unplugged, restart HA, re-add them again still same issues.
• Added via skyconnect directly and standard add doesnt change it.
• Have 2 of them on same physical location, 1 ok 1 have issue.
• Also randomly RSSI/LQI doesnt seem to have any effect. Some got good connection but still fails and som has worse values and still dont show any of the issues.

Im using ZBT-1.

Voltage HA History:

Blue/Red: Plug thats stops measuring on restart but ive pressed reconfigure on it after. Polls slow.
Green/Yellow: Working directly on restart, fast polling.
Pink: Plug that stopped measuring on restart havent pressed on reconfigure.

I used the voltage entity as its always changing, but issues occurs on all eletric measuring on effected plugs.

What version of Home Assistant Core has the issue?

core-2026.2.1

What was the last working version of Home Assistant Core?

i think it worked fine on 2025.12.xx

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

diag.txt

Additional information

No response

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@ABEIDO Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20zha%22%20
To help us troubleshoot, please include the following information in your report:

1. Please enable ZHA debug logging, let it run for 10-15 minutes, and make sure to capture whatever problem you're having in the debug log.
2. Download diagnostics JSON for the ZHA Integration for the specific devices you're having problems with.
3. Any issues whatsoever with Tuya devices or device support requests in general need to be made in the ZHA quirks repo https://github.com/zigpy/zha-device-handlers/issues, not Core's issue tracker.
4. Fill out the issue template and include whether or not you're using a VM/Proxmox with USB passthrough, what addons you have installed, and so on.

ZHA does not have low-level control over your network, the mesh is self-organizing. If you started having network issues in a specific release, the release probably didn't cause the issue. Check your environment for new sources of 2.4GHz interference and make sure you're using an extension cable, not placing the coordinator near SSDs and USB 3.0 ports, etc. Just because things worked in the past with a bad setup doesn't mean they'll keep working in the future.
_{^{(message by IssueContext)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[puddly]

Is the decimal precision the same on all three voltage entities?

[ABEIDO]

If u mean the display precision in the entity gui settings , yes they are

[ABEIDO]

I tested to remove/restart/readd one of the plugs that worked. Now its also got the same issue. Slow polling is one thing but no polling after restart and needing to press reconfigure to get them running is the primary issue. I understand that Ikea plugs is pushing on significant changes but its really strange that some work and some dont.

If i dont press on reconfigure and run read ElectricalMeasurement / rms_voltage manually on the plug in the cluster commands entitiy gets updated when i press it as shown below. But as long as i dont press reconfigure it wont update automatically.

Manually run ElectricalMeasurement / rms_voltage in the middle:

I saw this aswell zigpy/zha#396 but not sure what the conclusion was.

[tobbexiv]

I face the same issue with two new Inspelning plugs. I bought them last Saturday and added the to ZHA the same day (ha core was already on 2026.2.1). Only after a reconfigure, they started sending any data. After a HA restart yesterday evening, nothing was measured anymore today (should have measured multiple washing cycles). I now did a reconfigure and data is being sent again.

Edit: Hardware version is also the newest one. I don't have any legacy inspelning already added which i could compare.

[ABEIDO]

I face the same issue with two new Inspelning plugs. I bought them last Saturday and added the to ZHA the same day (ha core was already on 2026.2.1). Only after a reconfigure, they started sending any data. After a HA restart yesterday evening, nothing was measured anymore today (should have measured multiple washing cycles). I now did a reconfigure and data is being sent again.

Edit: Hardware version is also the newest one. I don't have any legacy inspelning already added which i could compare.

"Nice" to see thats its just isnt me with this. 2 of my friends is also seeing this problem so im guessing its something not local in my config.

[ElectricFern46]

I am facing the same issue with my Home Assistant instance. I recently bought the INSPELNING plugs, but as soon as I added them to ZHA, I noticed that power usage reporting only works if I hit 'reconfigure' after every HA restart.

Furthermore, the summation entity only updates once after a restart, which leads to very strange graphs in the energy dashboard.

I also noticed that the plug is recognized as zigpy.quirks.v2.CustomDeviceV2. I'm not sure if it should show something more specific to IKEA.

Lastly, the power measurement is inaccurate: if a device consumes more than 1000W, the value is displayed divided by 10. For example, a 1500W load is shown as 150W.

[ABEIDO]

@ElectricFern46
I dont have anything that causes that much load so not sure if the 1000 divided by 10 then occurs for me. But what firmware do you have on yours, read somewhere that they hade issues in this area on previous firmware.

Latest firmware: 2.4.45 / 0x02040045

[ElectricFern46]

@ABEIDO

@ElectricFern46 I dont have anything that causes that much load so not sure if the 1000 divided by 10 then occurs for me. But what firmware do you have on yours, read somewhere that they hade issues in this area on previous firmware.

Latest firmware: 2.4.45 / 0x02040045

I also read that. But the firmware seems to be the current one: 0x02040045
OTA Updates are also enabled and working.

[Klaasvdb]

Also having the same issues