[New device support]: IKEA INSPELNING smart plug with power monitoring #23961
Comments
|
I made this definition: External definitionconst {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?
Also:
|
|
clarifying the voltage and wattage. |
|
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 definitionconst {} = 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: Also don't forget to restart zigbee2mqtt and re-pair your device, otherwise it won't work. |
|
Voltage is correct now. I think the total sum of Energy already was correct EDIT: Total sum of energy looks like it 10 times to high |
|
@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. |
|
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? |
|
@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. |
|
Okay, so I couldn't wait until tomorrow to pair it (thanks @basvdploeg): 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? 🧐 |
|
Made a new definition, this one fixes the issue's with Energy and Power @QempZor External definitionconst {} = 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;
|
|
@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 |
|
This looks very promising! I think I'll need to go out to eat some hotdogs for lunch pretty soon :) |
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) |
|
I am almost certain that this must be a firmware issue, I hope Ikea will come up with an update soon.
Yup, that's @basvdploeg :) |
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. |
|
I bought 3 INSPELNING, one of them reports as TRETAKT (2204). I checked the label on the plug, it really says 2206 (INSPELNING). |
|
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? |
|
@busene do your 3 plugs show different firmware versions? |
|
@itkama nope, all show the same version |
|
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. It also seems like that the latest firmware version is 2.4.45, mine are both 2.4.34. |
This is the same that I experienced with mine. |
|
@Rembock mine are also 2.4.34, is there a way to update them without the ikea hub? |
|
I just bought a Dirigera and indeed there is an update. v2.4.45 is out However the Power problem is still there. Above 1000w is shown as 100,0w 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. |
|
The OTA update for the plug is available here: But I’m not sure how it can be used through Z2M. |
|
Picked one today, comes with 2.4.34 firmware, would welcome any hints on updating it without Ikea hub. 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. |
|
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 zigpy/zha-device-handlers#3374 (comment). I'm currently looking into fixing/expanding the issue/quirk for ZHA, maybe someone here knows how to fix this in Z2M tho ;) |
|
@Knol010 add |
Nice! |
|
Thx guys for the superfast reactions. 
I added the line, dit a restart of Z2M but still the Inspelning is not showing up in the OTA page... |
|
I used your files. Re-added the inspelning plug, restarted z2m. The device isn't showing up in OTA :( When I publish an update true MQTT it says that is does not support OTA updates |
|
@Knol010 try this external definition External definition for updating E2206const { } = 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');
// Uncomment the next line if you want to update with the standard Ikea ota links
// const {addCustomClusterManuSpecificIkeaUnknown, ikeaOta} = require('zigbee-herdsman-converters/lib/ikea');
// Uncomment the next line and comment the line above if you want to update trough with your own ota file
const { addCustomClusterManuSpecificIkeaUnknown } = require('zigbee-herdsman-converters/lib/ikea');
const definition = {
zigbeeModel: ['INSPELNING Smart plug'],
model: 'E2206',
vendor: 'IKEA',
description: 'INSPELNING Smart plug',
// Uncomment the next line if you want to update with the standard Ikea ota links an comment the other lines below
// extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta()],
// Uncomment the next 2 lines and comment the line above if you want to update with your own ota file
ota: ota.zigbeeOTA,
extend: [addCustomClusterManuSpecificIkeaUnknown(), onOff(), identify(), ikeaOta(), electricityMeter()],
meta: {},
};
module.exports = definition; |
|
It's working now. |
|
Awesome, don't forget to add the power divisor manually if you're using electricityMeter trough modern extend (see #23961 (comment)) or else the power will be off above/under 1000W. |
Thx Rembock. I did the last part also. 
The V is not correct. It should be lik 233. |
After update I had the same issue. |
Works on E2224 (Swiss plug version) with firmware 2.4.45. Thanks! FWIW, the standby consumption is 0.2 W with the relay off, 0.7 W with the relay on (measured with a calibrated benchtop power meter). The measurement accuracy of this new inexpensive IKEA smart plug seems to be quite good too, less than 2% off with various loads (5 W LED, 60 W incandescent, 2000 W kettle). |
|
Are OTA updates also possible now with the recent update? |
I just had a look in the OTA webui van z2m and did a check for updates, it did not show the available new version: 
@Rembock Is this expected? |
|
If I remember correctly the location of the OTA files is different than usual? So this would probably need another PR on the zigbee-ota side of things. |
|
I just updated Z2M and I see Inspelning is supported now. I still need to update them with the inspelning.js file.
Do I still need to do this with new plugs, because inspelning is supported now? |
|
@Menthe11 & @TASSDevon no and yes, version 1.40.2 only uses modern extend as seen in #23961 (comment). This means that you also have to add So yes @Knol010, we have to update the plugs the current way for now. If enyone feels free to open an issue or create a new PR for this go ahead, my knowledge barely scratches the surface of z2m to create a working ota for this plug. |
|
Thanks so much, @Rembock. Using these instructions, I could successfully update my device. The external definition from #23961 (comment) could not be loaded, though. I had to remove |
|
Can confirm, could update my device. Thanks @Rembock |
|
My INSPELNING was detected as a TRETAKT Model E2204 with Z2M Version [1.40.2] commit: [e06848d] and also made an OTA update to 2.4.25. Can anyone make sense of this? Am i able to manually OTA update the "inspelning-smart-plug-soc_release_prod_v33816645_02579ff4-6fec-42f6-8957-4048def87def.ota" to my wrongly detected E2204 and make a correct working E2206 out of it ? I tried the configurations here but it does not detect an OTA update to push... I took a second look on the lasered markings on the socket and it is also labeled as E2204/TRETAKT ... Maybe it got switched at production or an idiot switched it on purpose in the store, i´ll change it at IKEA.... |
Yes, it is very possible that someone swapped it in the store. It's so easy to do this since IKEA started using plastic-free packaging for their Zigbee products (so there's no sticky seal on the box anymore). I've been down the same road multiple times. One time there was some cheap AliExpress Zigbee GU10 light in the box instead of the IKEA one. Another time a Trådfri control outlet was literally cut in half, but it wasn't visible from the transparent front side of the box. So I learnt my lesson, and I always open the box to double-check its contents. 😅 |
|
Is it normal it only reports energy in 0.1kWh increments? It gives a wrong individual energy graph in HA. Is it inherent to the plug? 
|
|
Hi, I am a noob in Z2M so sorry if I am missing something obvious.. I added inspelning.js with the definition bellow: ` const { electricityMeter, onOff, identify } = require('zigbee-herdsman-converters/lib/modernExtend'); // Uncomment the next line and comment the line above if you want to update trough with your own ota file const definition = { // Uncomment the next 2 lines and comment the line above if you want to update with your own ota file meta: {}, module.exports = definition; The inspelning-smart-plug-soc_release_prod_v33816645_02579ff4-6fec-42f6-8957-4048def87def.ota and also the inspelning_OTA_index.json with the code:
I also added the link to the configuration.ya: `
(All those files are located in the zigbee2mqtt folder) Then I delete the plug from Z2M restart it and add it back but no update are available.. I hope somebody can spot what might be wrong and help! |
|
@Pierre331 Look at the logs after a restart of Z2M. I suspect the external converter cannot be loaded. It is the problem I mentioned in #23961 (comment) If that is the case, you have to remove |
|
It works! thanks a lot!! |
Hi! |
OTA will be supported out of the box with the next release. |
Thx for the quick reply. |
|
I've installed zigbee2mqtt with sonoff dongle-e. First device I connected is the Ikea INSPELNING / It's running ikea firmware 2.4.34. I would like to perform an OTA update to the latest published firmware (2.4.45?) to ensure the voltage reporting issue (& others) is fixed. When i check for updates, I get no update available. I've also enabled Ikea test server and also got no updates. Thanks. |
|
Just to add that with the 2.4.34 firmware and the latest zigbee2mqtt definitions we get incorrect voltage/power readings like previously reported :( I did some direct readings on the dev section and got this: Applying ~48W load: "rmsVoltage":232,
Applying ~1000W load: "rmsVoltage":228,
!?! Is this definately a vendor problem or is there something else we are missing? |
and others
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:
Configuration page (in HA) shows a Power-on behavior wich works as expected
The text was updated successfully, but these errors were encountered: