-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Innr smart plug sp240 not showing power monitoring #20039
Comments
Whilst digging through the documentation I found the following: https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/innr.ts I've used the SP 234 as a baseline to try and get the energy measurement part working and it seems to be working: Code snippet from the linked innr.ts file: This is my innr.js file: ` const definition = { module.exports = definition; Zigbee2MQTT version1.34.0-1 AdapterSONOFF ZBDongle-E |
I saw the some documentation but could not get it to work. Can confirm that your code works I will follow up if the reporting is correct if so i will change this problem to an add new device request. thx alot! |
Following @jorni2000's comment, I just patched the innr.js file to support the new sp240 plug. I edited the /opt/zigbee2mqtt/node_modules/zigbee-herdsman-converters/devices/innr.js file and copy/pasted the definition for the SP 234 on line 648, and adjusted it - replaced "234" with "240" twice in the first couple of lines. Seems to work just fine, and good enough for me until I (or someone else with more familiarity) have time to patch the typescript file and submit a real patch :). |
Wanted to send a patch today, but it was already done: |
Device is supported now! Changes will be available in the dev branch in a few hours from now. |
The reporting with the custom converter from @jorni2000 is a bit off: getting wrong I tried adjusting the divisors too, with no success. That said, at least the plug turns on/off and reports voltage correctly :-) |
Update: I did a factory reset an re-included the SP240 and now it is reporting properly. |
I just picked up a pair of the SP 240, any idea when the support will be merged into main? |
I have the same Problem. Unfortunately, I'm just a simple user. When will the sp240 be available with a homeassistant starndard installation? Thanks so much |
If you use the dev-Docker image the plug works fine with Home Assistant. |
Also curious, when to expect this in the regular release schedule? |
hello everyone, |
Will be supported in the 1 January release. |
Just to confirm here: removed my custom external converter, upgrading Zigbee2MQTT, restarting, and everything reports correct wattage. Thanks @Koenkk, and happy new year! |
Updated to latest version, works like a charm when pairing. I had to factory reset the unit, and now all values are imported into HA. However getting updates of the attributes is another thing, as @bikeymouse also noticed. I changed the timing for periodically updating to have instant updates for all attributes. The only one that is not updating automatically is the 'currentSumDelivered', when manually 'refreshed' the value is updated accordingly. Also with the default reporting interval this isn't working automatically. Any ideas on how to fix this @Koenkk ? |
Does it work after doing a reconfigure and not touching the rep change for currentSummDelivered? |
After one day I see 2 sockets have updated the currentSummDelivered automatically. One of which I changed to the original reporting setting (for this attribute). The other one has a modified reporting setting. A 3rd socket I factory reset this morning and used for the TV, has no update as the TV has not been used. How to interpret the reporting settings for this attribute? It seems random at this point when the sockets are updating this attribute (currentSummDelivered). |
Is the reset still required? Paired my new Plugs but they seem not to report automatically. I do have to trigger the report manually via the refresh button on Zigbee2Mqtt Edit: sorry, didn't see the discussion above 😃 but yes, I am facing the same issue. No automatic Reporting of Values to HA/Z2MQTT |
It seems that a factory reset is required @stefan1495 , as far as I experienced. But it might be different with your units. As can be seen in the screenshot, the Quooker has multiple times reheated, especially when making diner last night. However the attribute currentSummDelivered has only updated twice. This is with the following reporting configuration: Any ideas @Koenkk ? |
@gewoonivar if I understand correctly, you want to see updates more frequently? Could you provide the data/database.db entry of your device? |
@Koenkk yes. Strange thing, I remote started another plug (4), which has the same reporting config as plug 3. Plug 3 is reporting on short intervals, except for the currentSummDelivered as mentioned. Plug 4 doesn't update at all once switched on. Only on manual 'refreshes' the values of all attributes are updated. Plug 3: Plug 4: |
Can you try to reduce the max rep interval to something like 20? Then it should report every 20 secs. |
That works. Have set it to 60secs for each and reporting is good. Graph line gradually moves upwards with more consumption. Is there a way (in de UI) to copy/paste these set of reporting parameters to multiple devices, instead of configuring them one-by-one? |
That's currently not possible (but it's a one time thing so shouldn't be a lot of work to do it manually) |
I can confirm that I too - after the factory reset - have everything working with the default settings, except for the automatic reporting of the currentSummDelivered. Changing the rep interval of that to a lower value indeed does work. However, does that not actually mean reconfiguring it be polled every 20 seconds, instead of relying on (less resource intensive) use push-updates? For others also good to know: when I unplugged the plug from the mains and plugged it in again, reporting of all attributes was broken again. Had to do a factory reset again to fix that. Might be a firmware bug of the SP240? |
Agreed, that (auto) push updates would be more favourable. On the last remark, that's what I've experienced today to. Unplugging & plugging-in and the auto reporting is not functioning anymore. Very strange. |
@gewoonivar Btw: I did notice in your and my configuration that the currentSummDelivered is the only attribute in the default configuration that has no "minimum reporting change" set. I figured that perhaps that could be the issue so I have set this to "1" (would that be 1 Wh or 1 Kwh?) but that doesn't seem to have an impact, so still relying on the polling. |
Correct, on some plugs I changed that to 1 or 0 for testing, with no desired result. I believe empty was the default value after factory reset. |
Can you try sending to |
I tried this, but I'm not sure if the command is accepted. See no difference in behaviour. also. |
Because internally this is a bigint type, can you provide the debug log when sending this and your data/database.db entry after stopping zigbee2mqtt? |
Ah, Ok thanks for explaining ;-) Here are the relevant parts of the debug log (it actually now did report the energy, together with the other attributes, probably because of changes in those):
So trying to set max report interval to 1800 seconds and reportable change to 0,1 kWh. And this is the part of the database.db
|
With another plug just (again) faced the issue of no auto updates after unplugging & plugging-in the unit. I'm able to switch the plug (on/off), but attribute updates are not pushed, i.e. manual refresh required. Is this something for Innr, or Z2M? |
@bikeymouse could you also provide the herdsman debug log of this? See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. @gewoonivar the Innr firmware is bugged, I already notified someone from Innr and they are looking into it. |
Ok thanks @Koenkk . Any experience with their proces/speed of updates? Can it be distributed via Zigbee, as with other devices? Otherwise I'll return the plugs and find another solution. |
No clue, depends on Innr
Yes (once they send me the OTA) |
Sure! |
I don't see any logging after |
Nothing actually, which surprised mee. So I guessed that the commnand is first processed before echoing back the command. Should I retest?
|
The configuration is not applied because the wrong topic is used, use |
Oh my....you are right! I'm so sorry wasting your time with a dumb copy/paste error! The mqtt-response shows the command was successfull:
Only the "min rep change" field in the GUI remains empty, probably because it can't display the non integer value. I have to wait with some load if it now updates with 0,1 Kwh increments. |
I’m not tech savvy and just installed four SP240 10 days ago. Edit: |
My HA run's on a Raspberry Pi 4b 4G zigbee2mqtt: 1.36.1-1 Core: 2024.4.3 I've got 4 of these plugs and they all work fine. Pairing went well and all the values are reported automatically, except for the currentSumDelivered. When I set the max interval to 20 seconds, it starts polling so that works. However I would like to have push notifications. Is it still the case that doesn't work, and if so, is that because of Innr sp 240 firmware, or on the zigbee2mqtt side? I bought them for energy monitoring, so if that's not working well, I rather buy other ones. |
@Jeruntu I've been running ~10 plugs for a while: my experience has been that they work fine, until there's a hiccup in the coordinator (in my case, due to a reboot), and then I had to reconfigure them all. Some never came back, but I didn't stress it either. I would suggest checking with Innr if there's a way to upgrade their firmware: AFAIK not currently supported by Z2M? |
I contacted Innr support and they mention push notifications for Energy
|
What I did to fix this is to make a helper in homeassist that counts the used energy so that i could put in the energy dashboard and have accurate data. |
I don't understand why you would need a helper for this? Or that you think that energy reporting is not working will if you just polling which works fine. I you set the minimum reporting interval to e.g. 300 and the maximum interval at e.g. 3600 the plug will be polled every hour for an update. You can then just the Energy entity sensor from the device in HomeAssistant to see the value and display in you dashboard. Of course you can set the maximum interval to a lower value if you want faster updates (but why would you?). I'm can not imagine a use case where you would need frequent updates of the energy. For the "power" attribute I do want a more frequent update (e.g. to indicate when my waching machine is finished), but that works fine with push-updates. |
Hi all, I bought 4 innr SP 240 in a box. At one of the four the energy is shown correctly. The other three show sporadic steps of it ( several hours in between) . The firmware of the plugs seem to be all the same an all are connected to ZHA with a skyconnect. I don't know how to fix it. if anybody has an idea… |
I have the same issue with SP240 (and SP120) plugs on ZHA, reported here. @Peter376 I think my plugs did work well out of the box, but after a while (reboot, network change, not sure what triggered it) the Given this issue occurs on both ZHA and zigbee2mqtt, and it doesn't occur on other hardware it seems an innr-specific bug. This seems in line with the answer @Jeruntu received from their helpdesk. The only solutions I see is to
What's strange is that the plug does irregularly report an updated energy value. If we can identify and recreate whatever triggers the update, that might help. |
Any Updates yet from innr? I use ZHA (home assistant) and whenever there is a power outage, the innr SP240: a. Lose sumDelivered, b. Pressing button on/off on device does switch the plug on/off but the switch in HA doesn’t change. PS I am currently testing the new IKEA Inspelning and it looks promising |
What happened?
Innr SP240 isnt a supported device, I followed the manual on the website to add unsupported devices.
Made a innr.JS file with the following code:
Zigbee starts up I'm able to switch the device on and off but the energy readings are "Null"
What did you expect to happen?
What I expected to happen was that I had used the right exposes to add al the things this plug provides.
I hope that someone could help me further and that we can add this device to the supported list.
How to reproduce it (minimal and precise)
Using the code above you can reproduce it. Tried removing the sp240 plug and re-adding it using the same code same effect
Zigbee2MQTT version
1.34.0-1
Adapter firmware version
0x26580700
Adapter
ConBee2/RaspBee2
Debug log
No response
The text was updated successfully, but these errors were encountered: