[Device support request] innr SP220 smart plug

[SwoopX]

Basic cluster

Level Control

Power

[SwoopX]

Manufacturer specific cluster FC82

ZigBee Cluster Library Frame, Mfr: INNR Lighting BV (0x1166), Command: Discover Attributes Response, Seq: 208
    Frame Control Field: Profile-wide (0x1c)
    Manufacturer Code: INNR Lighting BV (0x1166)
    Sequence Number: 208
    Command: Discover Attributes Response (0x0d)
    Attribute Status Record
        Attribute: 0x0006
        Data Type: Character String (0x42)
    Attribute Status Record
        Attribute: 0x0010
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x0011
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x0012
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x0013
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x0014
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x0015
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0xfffd
        Data Type: 16-Bit Unsigned Integer (0x21)

Caught 2 further manufacturer specific attributes in the standard clusters

Basic cluster (0x4001 and 0x4002)

[ebaauw]

So indeed Zigbee 3.0 as expected and no Simple Metering nor Electrical Measurement as expected/feared. What's the Image Type (in the OTAU panel)? The 0xFC82 cluster is new. Do the values change, as load increases? I do have an unused innr bridge lying around, if you want to sniff how it interacts with the SP 220. However, last time I checked, it was really unsophisticated.

The device should already be exposed by the REST API plugin (as not-so-smart plug). Only thing to check is the whitelisting in bindings.cpp for the attribute reporting. Best change modelId.startsWith(QLatin1String("SP 120")) to modelId.startsWith(QLatin1String("SP ")) (only in that file).

BTW how do you do to send the Discover Attributes? deconz-cli-plugin? What's the byte code?

[kasteleman]

The SP 220 does Indeed not support Simple Metering nor Electrical Measurement as confirmed by INNR itself! So no need to snif because it only does on/off Op za 11 apr. 2020 om 22:09 schreef Erik Baauw <notifications@github.com>

…

So indeed Zigbee 3.0 as expected and no *Simple Metering* nor *Electrical Measurement* as expected/feared. What's the *Image Type* (in the OTAU panel)? The 0xFC82 cluster is new. Do the values change, as load increases? I do have an unused innr bridge lying around, if you want to sniff how it interacts with the SP 220. However, last time I checked, it was really unsophisticated. The device should already be exposed by the REST API plugin (as not-so-smart plug). Only thing to check is the whitelisting in bindings.cpp for the attribute reporting. Best change modelId.startsWith(QLatin1String("SP 120")) to modelId.startsWith(QLatin1String("SP ")) (only in that file). BTW how do you do to send the *Discover Attributes*? deconz-cli-plugin? What's the byte code? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2678 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGEKEVPPDC4BGDDEQPLDLRMDE7TANCNFSM4MGDT2NA> .

[SwoopX]

@ebaauw

What's the Image Type (in the OTAU panel)?

Image type is 0x0310

Do the values change, as load increases?

No, none of the values changes a bloody bit, even after 1h of my Sonos plaing stuff. Looks pretty useless.

BTW how do you do to send the Discover Attributes? deconz-cli-plugin?

Indeed. Pretty handy, at least for mains powered devices.

zclattrmanu 0xcaca 1 0xfc82 0x1166 0C00001D
               |   |    |      |    |   | |------- # of attributes to read (1D)
               |   |    |      |    |   |--------- # Attribute to start with (0000)
               |   |    |      |    |------------- Command (Discover Attributes)
               |   |    |      |------------------ Manufacturer code
               |   |    |------------------------- Manufacturer specific cluster
               |   |------------------------------ Endpoint
               |---------------------------------- Device

[ebaauw]

Holy crap, while documenting the GUI's keyboard shortcuts, I discovered that you can also send this request from the GUI. Select a cluster, select the node, press 9. Updated the "deCONZ for Dummies" Wiki. It doesn't set the Manufacturer Code though, so useless for clusters with that code.

[SwoopX]

Gee, where did you get that from, trying?

[ebaauw]

While editing the "deCONZ for Dummies" Wiki, I was double-checking the keys with the sniffer running. I did try all digit keys, but not all the letters, there could be another hidden gem (I was hoping for a Read Attributes of the Basic cluster).

[SwoopX]

Nice one.

[ualex73]

No measurements is a "downgrade" from SP120, because I bought the SP120 for that ;-) So I can skip the SP220 completely.

[kasteleman]

I mentioned that to INNR also. But the main customers use the HUE bridge for example and then there is no measurement available even with the SP120. Therefore they did not implement it in the SP220 and thereby reduced the costs for the new plug.

…

On 21 Apr 2020, at 09:35, Alexander ***@***.***> wrote: No measurements is a "downgrade" from SP120, because I bought the SP120 for that ;-) So I can skip the SP220 completely. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2678 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGEKFZWOS2OBGXTY5UCQLRNVEEPANCNFSM4MGDT2NA>.

[ualex73]

I understand the business logic behind it, but they just lost me as a customer for plugs ;-)

[kasteleman]

And again, did mention that to them. 1 of the + of the SP120 and reason some people use that plug. Would have been a nice upgrade because of ZigBee 3.0 and attribute reporting…...

…

On 21 Apr 2020, at 09:43, Alexander ***@***.***> wrote: I understand the business logic behind it, but they just lost me as a customer for plugs ;-) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2678 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGEKFXBQN4HTS2LHFG2XLRNVFAVANCNFSM4MGDT2NA>.

[SwoopX]

Indeed. From my perspective, power measurement was more a unique selling proposition. Since it's not in anymore, I'm out. Really enjoyed the SP 120.

The SP 220 are more expensive btw ;)

[Mimiix]

It seems this issue is resolved or otherwise inactive. If it is not, please re-open!