[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 ;) |
|
@folfy thanks for sharing. This got me thinking, your findings are aligned with wat we're experiencing. 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. |
|
I've managed to update firmware to 2.4.45 using z2m, here are the steps.
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. |
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. |
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? |
|
@notgood Update on the first plug worked fine. Second one is running right now. |
I found out the same. When I use them without @Rembock's external definition, they show the voltage and power (up to 1000W) correctly. |
@Rembock I probably don't understand enough about this, but... Wouldn't it be possible to read the acPowerDivisor on every power update, and display the right value based on that? |
|
@basvdploeg Well that's funny now. While it was working with and without the external converter before - on the new firmware I still get the "high voltage" regardless if I use the external converter or not. |
My thoughts exactly! Except I also don't know how (yet) |
Had "high voltage" right after firmware update. |
|
Interesting, reading acVoltageDivisor already did the trick. No need for acVoltageMultiplier on my plugs. |
|
just added acPowerDivisor to reporting, this seems to solve the power issue for now |
@Rembock I can confirm that this is working. 🎉 |
@folfy Where did you get it? There is no information online, it's not listed at all, and I don't want to search all stores in Vienna myself. |
Regarding stock, see my comment in the ZHA issue. Below 1000W it reports with .1W resolution, and also is reading from 0.1W already. Checking some .04W load and .2W and .8W of a second INSPELNING in series, it seemed totally fine so far (within rounding error). Power consumption is a bit higher than the amazing Aqara smart plug, but also it's twice the price, and it also has the "IKEA sensors and buttons directly switching the socket on/off, if their zigbee packets are routed through the plug" issue. The physical on/off button on the IKEA plug seems a bit meh, but yeah, overall would still recommend the new IKEA plug, because the additional wasted electricity would take like 10y (@25c/kWh) to offset the higher price of the Aqara, if you'd leave it on 24/7. PS: Since @notgood mentioned it now, yeah, my voltage reading is also quite off (~+5V, didn't meassure precisely yet), but due to the "auto-ranging" problem, I totally missed on checking if it also affects power reading accuracy (at bigger loads you would actually see the 2% difference, but also could be that only the reported voltage is uncalibrated). |
Yup, INSPELNING has a 0.1W resolution at low power values. Did a quick test, Voltcraft energy logger 4000 was used to compare values. Mains voltage is a bit off, -2V or so. INSPELNING itself standby power on is 0.8W, standby power off is too low to be measured by Voltcraft. |
|
Ok, just small update on the off-topic of accuracy: @notgood Regarding the floppy button pcb, I agree that the button is shit and sometimes not reacting (even though it clicked), but in theory the design definitely ain't as bad, like the pcb isn't left unsupported (if you look at the lid that you removed/opened, you'll see). |
Is this with your latest ext def? EDIT: nvm., already found out it is without any ext def. :) Good work! |
Tea kettle was the only high powered single-phase device in the general vicinity, so here goes: I see Z2M supports calibration percentual offsets, probably linear, but better than nothing.
Didn't inspect the top lid, even if there is some kind of support, it didn't help much. Wedging PCB closer to plastic button solved problem for me, 100% of clicks work now. If this issue is widespread, it will probably cost Ikea quite some returns. |
|
With the latest firmware, does the energy report correctly now? (both < 1000W and >= 1000W) If not, we can apply a hack in the converter. |
It works correct if the Cluster: haElectricalMeasurement; Attribute: acPowerDivisor is added with Min. Rep Interval of 1 You have to add it manual. Should be nice if it's added automaticly when adding the device in Z2M |
|
@Koenkk As @folfy mentioned earlier in #23961 (comment), the powerdivisor changes dynamically based on the amount of power. Adding acPowerDivisor to reporting from the device solves the power issue. I've done this form within the UI after the successfull pairing based on the latest version. I've tried to extend the definition with extra reporting (for acPowerDivisor), but that attempt was unsuccessfull. Ideally the reporting of acPowerDivisor would be added when pairing. The Min. Rep interval can also be 5, the 1 was just a guess. I recently tested this and got satisfying results. Last but not least, updating is also a hassle. See #23961 (comment) for details. @QempZor has shared the link for the ota in #23961 (comment) |
@MaxRower I just bought the plug from IKEA Westbahnhof, there were still a few left. |
|
You can use this way to find out if your Ikea has the plug in store. |
I can't get my new inspelnings to update... I must do something wrong. But I have no clue what. Downloaded the OTA and placed it in the root dir. Must be somewhere in my external converter file: Any smart mind an idea? After that changes the devices also show up as unknown/not supported Already did complete restarts/remove-readd devices |
|
@QempZor did you also add the ota override index location to the configuration.yaml? Alternatively, you can also add the ota file location from within the UI. |
Yes, added: Or; theremight be nothing wrong, but i just don't know how to update? It supposed to say that an update is found? Or do I need to do something manualy? |
|
@QempZor You can check for updates via the OTA tab in Z2M. 
|
Wasn't there, but did everything again (for like the 10th time) and used HomeAssistant's MQTT publisher. That worked :) |
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: