Apologies if this is hijacking the thread - I am using lots of Innr SP 242 plugs in my house in the (UK version). Would this update also be applied for this plug too?
Currently using this driver by @user3101
Apologies if this is hijacking the thread - I am using lots of Innr SP 242 plugs in my house in the (UK version). Would this update also be applied for this plug too?
Currently using this driver by @user3101
You might provide the fingerprint and driver data section screenshot for the INNR-SP242, as Mike requested above for the INNR-SP244. Then wait for his reply. But note that the above discussion was about getting the Built-in Generic Zigbee driver to reflect the correct plug numbers.
Just a few observations having run a couple of these plugs long enough to see some interesting behavior.
Side button on plug, I've noticed the reaction to pressing this on/off button doesn't always react to turning "ON" as one might expect. Sometimes it takes a depression or three, then other times it's like bam...ON, one press.
(This might have nothing to do with the outlet and more to do with some momentary mesh problem). Have a Rule that trustingly sends one OFF command to the outlet and moves on with other actions assuming that state was achieved. Today for the first time I noted the outlet did NOT go off.
Shame on me for not putting in double OFF instructions and a check & handling of the case if it did not turn off. The log shows it was told to, but it never responded that it did so...and physically it was ON when it should have gone off.
Donno if it didn't hear the HE radio or what.
EDIT ADD: I will note that I recently placed a MHCOZY relay in a box about 18" away from this outlet. So far that relay has functioned perfectly ...but might it be causing some issues if it repeats AND the outlet repeats?
Anyway, now there's two OFF commands in the Rule, second one delayed 3 seconds, and then a Conditional check to see if the outlet is indeed OFF before the rule proceeds.
Writing this up in case others observe moments of "radio deafness" or otherwise command disobedience with this INNR outlet.
Hi all, our support engineer asked me to provide some feedback in this thread on 2 questions: 1) does the SP 244 function as a repeater? and 2) what is the tx power of the SP 244? My answers are below. If you need more information please be as specific as possible about what you need.
Yes the SP 244 functions as a "repeater", i.e. it is a Zigbee router that participates in routing according to the Zigbee specification. Analyzing the routing in a mesh can be complex, especially if the tools have some known problems. A post in this forum about "zigbee-instability" provides general knowledge that might be of help.
The maximum output power of the chip used in the SP 244 is 10 dBm, which is equal to 10 mW. Some background:
In Europe, there are two restrictions on output power, namely max output power and max power spectral density. The former is 20 dBm (100 mW), but the latter effectively limits the former to a bit above 10 dBm. For more info google on 1308_HFE_eustandards.pdf, or on maximum-allowed-power-for-zigbee-applications-under-etsi-en-300-328.
In the US, the limit on max output power is 30 dBm (1 W), and I believe there is a limit on power spectral density but it doesn't further limit the max output power.
Most current Zigbee chipsets offer 10 dBm or just below it, but there are some that offer up to 20 dBm.
Hope this helps a bit.
Gerry - Innr Lighting.
Hi @PunchCardPgmr , the measuring chip in the SP 244 (BL0937) alternately measures voltage and current on 1 pin, and measures power on a separate pin. Power is not equal to voltage * current if the power factor < 1, which is the case for almost all devices nowadays. Software counts the power ticks and derives power in W and power consumption in kWh.
The SP 244 provides correct values for attributes 0x0505 (RMSVoltage), 0x0508 (RMSCurrent), and 0x050b (ActivePower) in cluster 0x0b04, and attribute 0x0000 (CurrentSummationDelivered) in cluster 0x0702. The "formatters" for those attributes are the "Multiplier" and "Divisor" attributes 0x0600 to 0x0605 of cluster 0x0b04, and the "SummationFormatting" attribute 0x0303 of cluster 0x0702.
Hope this helps fix the bug in Hubitat / driver / ...
Gerry - Innr Lighting.
I know I can speak for ALL the folks in this Community when I say THANK YOU VERY MUCH for respecting the Hubitat platform enough to step in and clarify things like this.
Over time this kind of vendor-to-vendor, vendor-to-customer communication to "get things right" will increase the endearment folks will have for your company and your device offerings.
Thanks.
cc.
@mike.maxwell at Hubitat
Hi Gerry, thank you very much for responding here. I had been communicating with one of your tech support folks on this (Florian) and I suggested that Innr post the information here in this thread for everyone to see. Really appreciate you taking the time so the community can all benefit from your answers.
Having an issue getting the ability to monitor the power with my smart plug. I had just updated my SP224 smart plugs to the latest firmware about an hour ago.
The firmware was sitting at:
But with the new firmware, it's now at:
I noticed that the details page for these smart plugs doesn't show any power monitoring, unlike others I've seen. I'm using the Generic Zigbee Outlet model. Is this feature supported?
Here's a full page screenshot of what the smart plug page looks like:
Please note that toggling ON the switch does not change the power value.
Hi, the SP 224 does not have power monitoring.
I saw your post yesterday, but I totally mis-read it as "244"... But Gerry's right -- the 224 has no power reporting -- just the (now older) 234 and (latest model) 244 models have it.
I have a bunch of 224s and a couple 234s -- I use the "Generic Zigbee Outlet" driver for all them, and it works great.
All of my 224s have that same latest firmware you posted, and the Current States section looks the same too (all show "power: 0").
Thank you for the information! I also had some confusion about the monitoring.
Last night, I noticed that about 10 hours after updating all the smart plugs to the latest firmware, they turned on as scheduled but did not turn off at their designated time.
Also, @Gerry-Innr thanks for your response too.
That's odd - my 224s (and 234s) have all always been rock-solid performers, both in terms of performance reliability and being strong repeaters.
Did the rule/automation work consistently prior to the update? Perhaps just going into it and hitting "Done" might help align it again.
Yes; rock solid before the firmware update. I won't know until tonight if they don't turn off again when they should.
I’ve been testing the latest firmware updates on my Innr plugs over the past few days. Since the update, the plugs have only executed automations successfully around 60% of the time, compared to 100% reliability prior to the update.
After reviewing the logs, I noticed that during the 40% failure rate, there are no entries indicating that the automations were triggered at the scheduled times, suggesting the issue might stem from the automation triggers themselves not firing, rather than the plugs failing to respond. But I find it interesting that this just started happening with all the devices having been updated to the latest firmware.