[New device support]: IKEA INSPELNING smart plug with power monitoring

[QempZor]

Link

US Version: https://www.ikea.com/us/en/p/inspelning-plug-smart-energy-monitor-90569846/ Dutch version: No ikea link yet, but buyable in the stores.. :)

Database entry

{"id":53,"type":"Router","ieeeAddr":"0xecf64cfffef2b718","nwkAddr":27855,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"INSPELNING Smart plug","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":266,"inClusterList":[0,3,4,5,6,8,1794,2820,4096,64636,64645],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"INSPELNING Smart plug","manufacturerName":"IKEA of Sweden","powerSource":1,"zclVersion":8,"appVersion":2,"stackVersion":114,"hwVersion":1,"dateCode":"20240215","swBuildId":"2.4.34"}},"haElectricalMeasurement":{"attributes":{"acPowerDivisor":10,"acPowerMultiplier":1,"acCurrentDivisor":1000,"acCurrentMultiplier":1,"acVoltageDivisor":10,"acVoltageMultiplier":1,"activePower":0,"rmsCurrent":3,"rmsVoltage":236}},"seMetering":{"attributes":{"divisor":1000,"multiplier":1,"currentSummDelivered":[0,77]}},"genLevelCtrl":{"attributes":{"onLevel":255,"currentLevel":254}},"genOnOff":{"attributes":{"onOff":1}}},"binds":[{"cluster":2820,"type":"endpoint","deviceIeeeAddress":"0xb43522fffe12b3b4","endpointID":1},{"cluster":1794,"type":"endpoint","deviceIeeeAddress":"0xb43522fffe12b3b4","endpointID":1}],"configuredReportings":[{"cluster":2820,"attrId":1291,"minRepIntval":10,"maxRepIntval":65000,"repChange":50},{"cluster":2820,"attrId":1288,"minRepIntval":10,"maxRepIntval":65000,"repChange":50},{"cluster":2820,"attrId":1285,"minRepIntval":10,"maxRepIntval":65000,"repChange":50},{"cluster":1794,"attrId":0,"minRepIntval":10,"maxRepIntval":65000,"repChange":[0,100]}],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[33],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":2,"stackVersion":114,"hwVersion":1,"dateCode":"20240215","swBuildId":"2.4.34","zclVersion":8,"interviewCompleted":true,"meta":{"configured":332242049},"lastSeen":1726245436588}

Zigbee2MQTT version

1.40.1

Comments

Just picked this plugs up at the Ikea in Amsterdam. They're quite new, no infopage on the Ikea site (NL) I tried to follow the "How to add support" page, but.. well,.. to complicated for this noob :)

However I want to help so here is al the information I know.

Out of the box, in Z2M, a lot works already quite well. See the results below.

Extra; Some Tweakers forum information (Dutch): https://gathering.tweakers.net/forum/list_message/80105532#80105532

External definition

const {light, electricityMeter} = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['INSPELNING Smart plug'],
    model: 'INSPELNING Smart plug',
    vendor: 'IKEA of Sweden',
    description: 'Automatically generated definition',
    extend: [light(), electricityMeter()],
    meta: {},
};

module.exports = definition;

What does/doesn't work with the external definition?

Out of the box in:

• ON OFF switch works as expected.
• There is an "Effect" thing in HA/Z2M: Dont think it needs to be there for plug
• There is an "Brightness slider" Dont think it needs to be there for plug
• Energy Sensor is a sum of total consumed energy. Don't know if correct. See next point.
• Power monitoring works kinda. When I charge my iPad it reads around 20W wich seems to be good. However if i plug in my toaster (wich is around 2000w) it reports around 209w) So there seems like a decimal error thing?
• Same problem for voltage. It reports 23,3-23,6v (when pluged in to a 230v outlet ofcourse)
• ̶P̶r̶o̶b̶a̶b̶l̶y̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶t̶h̶i̶n̶g̶ ̶f̶o̶r̶ ̶t̶h̶e̶ ̶a̶m̶p̶e̶r̶a̶g̶e̶.̶.̶ ̶D̶i̶d̶n̶t̶ ̶t̶e̶s̶t̶ ̶t̶h̶a̶t̶.̶ UPDATE: After testing the amperage seems to be correct.

Configuration page (in HA) shows a Power-on behavior wich works as expected

[Rembock]

I made this definition:

External definition

const {electricityMeter, onOff, identify} = require('zigbee-herdsman-converters/lib/modernExtend');
const {addCustomClusterManuSpecificIkeaUnknown, ikeaOta} = require('zigbee-herdsman-converters/lib/ikea')

const definition = {
   zigbeeModel: ['INSPELNING Smart plug'],
   model: 'E2206',
   vendor: 'IKEA',
   description: 'INSPELNING Smart plug',
   extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta(), electricityMeter()],
   meta: {},
};

module.exports = definition;

What does this external definition fix?

• Removes "Effect"
• Removes "Brightness slider"

Also:

• Energy Sensor looks indeed like a sum of total consumed energy, I have another energymeter that does the same
• Power monitoring works like it should, the voltage differs depending of the connected device onto your plug & should never use the full 230v.
• Same applies to voltage and amperage

[QempZor]

clarifying the voltage and wattage. 1500w toaster connected shows this on a 240v outlet:

[Rembock]

You're right, I think I've extended the external definition correctly now. Can you try if this external definition works for you as well?

External definition

const {} = require('zigbee-herdsman-converters/lib/modernExtend');
const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const ota = require('zigbee-herdsman-converters/lib/ota');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;

const {electricityMeter, onOff, identify} = require('zigbee-herdsman-converters/lib/modernExtend');
const {addCustomClusterManuSpecificIkeaUnknown, ikeaOta} = require('zigbee-herdsman-converters/lib/ikea');

const definition = {
   zigbeeModel: ['INSPELNING Smart plug'],
   model: 'E2206',
   vendor: 'IKEA',
   description: 'INSPELNING Smart plug',
   extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta()],      
   fromZigbee: [fz.electrical_measurement, fz.metering],
   toZigbee: [],
   configure: async (device, coordinatorEndpoint, logger) => {
       const endpoint = device.getEndpoint(1);
       await reporting.bind(endpoint, coordinatorEndpoint, ['haElectricalMeasurement', 'seMetering']);
       await reporting.activePower(endpoint);
       await reporting.rmsVoltage(endpoint);
       await reporting.rmsCurrent(endpoint); 
       await reporting.currentSummDelivered(endpoint);               
       endpoint.saveClusterAttributeKeyValue('haElectricalMeasurement', {
           acPowerMultiplier: 1,
           acPowerDivisor: 10,
           acVoltageMultiplier: 1,
           acVoltageDivisor: 1,
           acCurrentMultiplier: 1,
           acCurrentDivisor: 1000,            
       });
       endpoint.saveClusterAttributeKeyValue('seMetering', {divisor: 100, multiplier: 1});        
       device.save();
   },
   exposes: [e.power(), e.voltage(), e.current(), e.energy()],
};

module.exports = definition;

This is my result: I am not sure if the number of kWh is correct yet

Also don't forget to restart zigbee2mqtt and re-pair your device, otherwise it won't work.

[QempZor]

Voltage is correct now. I think the total sum of Energy already was correct Power is still wrong when wattage reach >1000w

EDIT: Total sum of energy looks like it 10 times to high

[ronaldevers]

@Rembock the "effect" actually worked on the light on the plug. I could for example make the light "breathe". The brightness did not appear to do anything. So I don't think the "effect" should be removed.

[itkama]

These are also available in Germany now. Just bought 2. I will take a look if your external controller works for me tomorrow @Rembock. Any clue on how to get these into pairing mode?

[basvdploeg]

@itkama You can put them in pairing mode by pressing and holding the small button next to the power button. You probably need a pointy object to do so.

[itkama]

Okay, so I couldn't wait until tomorrow to pair it (thanks @basvdploeg): Seems to be kind of working out of the box already? Voltage looks about right. On/Off working. Not sure about the power measurement, as this is the first time I'm measuring my vacuum bot.

Tried the other one with a pretty efficient GAN-USB-Charger to charge a powerbank that shows how much is going in. While the plug reported 30 to 31W, while the powerbank was reporting around 25W of input power. So for low power it may be kind of accurate.

What does the external converter really change now though? The power number atleast on low wattages seems to be looking correct? 🧐

[Rembock]

Made a new definition, this one fixes the issue's with Energy and Power @QempZor @ronaldevers i will try to take a look if there's a dimmer functionality hidden somewere,

External definition

const {} = require('zigbee-herdsman-converters/lib/modernExtend');
const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const ota = require('zigbee-herdsman-converters/lib/ota');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;

const {electricityMeter, onOff, identify} = require('zigbee-herdsman-converters/lib/modernExtend');
const {addCustomClusterManuSpecificIkeaUnknown, ikeaOta} = require('zigbee-herdsman-converters/lib/ikea');

const definition = {
   zigbeeModel: ['INSPELNING Smart plug'],
   model: 'E2206',
   vendor: 'IKEA',
   description: 'INSPELNING Smart plug',
   extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta()],      
   fromZigbee: [fz.electrical_measurement, fz.metering],
   toZigbee: [],
   configure: async (device, coordinatorEndpoint, logger) => {
       const endpoint = device.getEndpoint(1);
       await reporting.bind(endpoint, coordinatorEndpoint, ['haElectricalMeasurement', 'seMetering']);
       await reporting.activePower(endpoint);
       await reporting.rmsVoltage(endpoint);
       await reporting.rmsCurrent(endpoint); 
       await reporting.currentSummDelivered(endpoint);               
       endpoint.saveClusterAttributeKeyValue('haElectricalMeasurement', {
           acPowerMultiplier: 1,
           acPowerDivisor: 1,
           acVoltageMultiplier: 1,
           acVoltageDivisor: 1,
           acCurrentMultiplier: 1,
           acCurrentDivisor: 1000,            
       });
       endpoint.saveClusterAttributeKeyValue('seMetering', {divisor: 1000, multiplier: 1});        
       device.save();
   },
   exposes: [
       e.power(), 
       e.voltage(), 
       e.current(), 
       e.energy()
   ],    
};

module.exports = definition;

[Rembock]

@ronaldevers I get Data confirm errors in my log when I add light to the extended definition, so I decided not to configure the effect

[LeoSum8]

This looks very promising! I think I'll need to go out to eat some hotdogs for lunch pretty soon :) Can anyone share how often the values are updated? Thanks!

[QempZor]

Okay, so I couldn't wait until tomorrow to pair it (thanks @basvdploeg): Seems to be kind of working out of the box already? Voltage looks about right. On/Off working. Not sure about the power measurement, as this is the first time I'm measuring my vacuum bot.

Tried the other one with a pretty efficient GAN-USB-Charger to charge a powerbank that shows how much is going in. While the plug reported 30 to 31W, while the powerbank was reporting around 25W of input power. So for low power it may be kind of accurate.

What does the external converter really change now though? The power number atleast on low wattages seems to be looking correct? 🧐

Power readings below 1000w are fine (out of the box), But above 1000W everything is shown as 100,0w (or f.e. 132,4w)

With the ext. def. from Rembock, everything above 1000W seems to be good; but below 1000w is then show 10x too much (7,2w LED bulb reads 72w power... )

Also; I saw someone on Tweakers (dutch tech forum) who bought 2 of these plugs and didn't show any data. He changed them at another Ikea store and then one of them is showing the correct voltage, and one is shown 10times to high voltage, with the same settings/ext.def.) So there might also be a (small) problem within the units itself. (<- Thats just speculation)

[Rembock]

I am almost certain that this must be a firmware issue, I hope Ikea will come up with an update soon.

Also; I saw someone on Tweakers (dutch tech forum) who bought 2 of these plugs and didn't show any data. He changed them at another Ikea store and then one of them is showing the correct voltage, and one is shown 10times to high voltage, with the same settings/ext.def.) So there might also be a (small) problem within the units itself. (<- Thats just speculation)

Yup, that's @basvdploeg :)

[itkama]

@Rembock Firmware versions on both my plugs is 2.4.34 with a Firmware date of 20240215. @QempZor there also is the TRETAKT plug. It looks really similar - but it has no power readings. Costs 2€ less here in Germany. Maybe he just got the wrong plugs? 😅

[basvdploeg]

@Rembock Firmware versions on both my plugs is 2.4.34 with a Firmware date of 20240215. @QempZor there also is the TRETAKT plug. It looks really similar - but it has no power readings. Costs 2€ less here in Germany. Maybe he just got the wrong plugs? 😅

No, they were the INSPELNING. Both showed only 1 (different) reading, and all the other values stayed empty. I tried re-pairing them multiple times, with and without external definition, but the results stayed the same.

When I switched them for two new version (from another IKEA store), I got all the data instantly. So it definitely looked like a problem in the plugs themselves.

[arjansiemons]

I bought 3 INSPELNING, one of them reports as TRETAKT (2204). I checked the label on the plug, it really says 2206 (INSPELNING).

[busene]

I bought 3 yesterday and added them to Zigbee2MQTT using the external definition from @Rembock . Somehow 1 shows all the values x10 (so my outlet is now outputting 2340Volts), but the other 2 show correct values. Anybody that knows whats going on?

[itkama]

@busene do your 3 plugs show different firmware versions?

[busene]

@itkama nope, all show the same version

[Rembock]

Instead of using the power sensor from the E2206, I'm now using a sensor with the template integration as a helper from the UI in Home Assistant.

With this method you can 'tune' each plug to display the correct number of watts until Ikea pushes an firmware update that hopefully fixes the power sensor. I also saw support voor the Tretakt listed here since the 3rd of May, I expect the Inspelning to be listed here soon as well.

It also seems like that the latest firmware version is 2.4.45, mine are both 2.4.34.

[basvdploeg]

I bought 3 yesterday and added them to Zigbee2MQTT using the external definition from @Rembock . Somehow 1 shows all the values x10 (so my outlet is now outputting 2340Volts), but the other 2 show correct values. Anybody that knows whats going on?

This is the same that I experienced with mine.

[busene]

@Rembock mine are also 2.4.34, is there a way to update them without the ikea hub?

[QempZor]

I just bought a Dirigera and indeed there is an update. v2.4.45 is out With this new update; out of the box the voltage and current are shown correctly in Z2M.

However the Power problem is still there. Above 1000w is shown as 100,0w I checked the power in the Ikea Home app and there it's shown correctly. Above 1000w and also below 1000w.

In HomeAssistant with the template from @Rembock there is a big difference between the template measurement and the Z2M readings. This is maybe due to the fact that the Current readings are (quite a bit) off? Or at least; not accurate.

Example below is with an 30w ipad charger. Quick translate: "Ikea_plug_1" is the template sensor "Vermogen" is Power straight out of Z2M

[basvdploeg]

The OTA update for the plug is available here: https://fw.ota.homesmart.ikea.com/check/update/prod

But I’m not sure how it can be used through Z2M.

[notgood]

Picked one today, comes with 2.4.34 firmware, would welcome any hints on updating it without Ikea hub. It seems Zigbee2mqtt only supports the Tradfri OTA feed, not the Dirigera one.

Mine INSPELNING also came with a barely working and unreliable button, only third of keypresses actually did something.

Disassembled it: breakout board with a button and LED is pretty much floating midair, rather unfortunate and sloppy engineering design IMHO.

Used a piece of plastic zip tie as a wedge between breakout board and relay, with a bit of electric tape to calibrate width.

[folfy]

I bought the new INSPELNING plug here in Austria two days ago, and experienced the same issue that power >=1000W is shown as 1/10th of the actual value (on ZHA).

I checked the Measurement Cluster for related attributes, and could figure out that the plug is dynamically adjusting the "ac_power_divisor" between 10 (<1000W) and 1 (>=1000W), which probably is not updated/reflected by ZHA or Z2M in the shown value accordingly:

The off-value for the voltage seems to be fixed for some with the new firmware, see https://github.com/zigpy/zha-device-handlers/issues/3374#issuecomment-2365316168.

I'm currently looking into fixing/expanding the issue/quirk for ZHA, maybe someone here knows how to fix this in Z2M tho ;)

[Rembock]

@folfy thanks for sharing. This got me thinking, your findings are aligned with wat we're experiencing. After some reading this weekend, I also realised that my template sensor is measuring VA (for DC) and not VAR (for AC). To measure VAR I need to know the power factor. Sadly, a power factor cannot be read from the E2206, and after that, I was out of ideas. But with your findings I have another idea. With the latest firmware update we now know that only the power is off above 1000W. So I'm thinking of creating some sort of conditional statement that changes the power factor based on the power level.

Finally we also need to update the ota file. I'm not sure, but I think I saw an update file override function somewhere in the settings of z2m that can be used as a workaround for now.

If I'm lucky, I will have some time left tonight to take a shot at this. Will share something if everything works correctly.

[notgood]

I've managed to update firmware to 2.4.45 using z2m, here are the steps.

1. Download https://fw.ota.homesmart.ikea.com/files/inspelning-smart-plug-soc_release_prod_v33816645_02579ff4-6fec-42f6-8957-4048def87def.ota
2. Create inspelning_OTA_index.json with the following contents

[
    {
        "url": "inspelning-smart-plug-soc_release_prod_v33816645_02579ff4-6fec-42f6-8957-4048def87def.ota"
    }
]

3. Create external definition file inspelning.js, contents in above post by @Rembock. Temporary comment out lines referencing ikeaOta and add zigbeeOta instead.

...
// const {addCustomClusterManuSpecificIkeaUnknown, ikeaOta} = require('zigbee-herdsman-converters/lib/ikea');
...
// extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta()],
....
ota: ota.zigbeeOTA,
....

4. Add references to external definition and OTA override to configuration.yaml

external_converters:
    - inspelning.js
ota:
  zigbee_ota_override_index_location: inspelning_OTA_index.json

All files must be located in the same directory as configuration.yaml. Restart z2m, you now should be able to update INSPELNING firmware.

After successful update, rollback OTA related changes in your external definition file and restart z2m again.

[folfy]

@folfy thanks for sharing. This got me thinking, your findings are aligned with wat we're experiencing. After some reading this weekend, I also realised that my template sensor is measuring VA (for DC) and not VAR (for AC). To measure VAR I need to know the power factor. Sadly, a power factor cannot be read from the E2206, and after that, I was out of ideas. But with your findings I have another idea. With the latest firmware update we now know that only the power is off above 1000W. So I'm thinking of creating some sort of conditional statement that changes the power factor based on the power level.

Yeah, I forgot to remark on the issue of your previous approach, but you noticed anyway. Still, any conditional check based just on the power or current is gonna be a guess at best. You can't 100% certainly determin if the ~100.0-200.0W that you're reading are actually 1000-2000W or just 100-200W with a really bad power factor. The latter shouldn't really happen normally, having such high reactive load with barely any true power being used, but we all know there will be that one guy with a rly bad, old device that shouldn't even rly exist.

It might be a quick and dirty hack to fix it temporarily, but I'd say the only appropiate solution to be pushed upstream should be an actual check/consideration of the scalar/divisor attribute.

[Rembock]

You can't 100% certainly determin if the ~100.0-200.0W that you're reading are actually 1000-2000W or just 100-200W with a really bad power factor. The latter shouldn't really happen normally, having such high reactive load with barely any true power being used, but we all know there will be that one guy with a rly bad, old device that shouldn't even rly exist.

It might be a quick and dirty hack to fix it temporarily, but I'd say the only appropiate solution to be pushed upstream should be an actual check/consideration of the scalar/divisor attribute.

I hadn't thought about that, with that knowledge I went to see what else could be done to solve it. What I did notice is that after reading acPowerDivisor from the Dev console, the power does show correctly. Maybe refreshing the power divisor more often could be a solution?