Skip to content
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 SP120 configuring error message on boot #3488

Closed
vdbrink opened this issue May 3, 2020 · 4 comments
Closed

Innr SP120 configuring error message on boot #3488

vdbrink opened this issue May 3, 2020 · 4 comments

Comments

@vdbrink
Copy link

vdbrink commented May 3, 2020

Bug Report

What happened

When I start zigbee2mqtt I get the next error messages about my Innr SP120 socket while booting. This is in the 1.13.0 version but also 1.12 but I didn't saw it in a much older version.
The socket itself just works normally as expected.

MQTT publish: topic 'zigbee2mqtt/innrsmartplug1', payload '{"state":"OFF","linkquality":57,"power":0,"voltage":231,"current":0}'
zigbee npm[3915]: zigbee2mqtt:info   Configuring 'innrsmartplug1'
zigbee npm[3915]: zigbee2mqtt:error  Failed to configure 'innrsmartplug1', attempt 2 (Error: Read 0x00158d000342b933/1 haElectricalMeasurement(["acVoltageMultiplier","acVoltageDivisor","acCurrentMultiplier"], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'UNSUPPORTED_ATTRIBUTE')
at Endpoint.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:182:23)
at Generator.next (<anonymous>)
at fulfilled (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))

What did you expect to happen

No error at boot time for the configuration of the Innr sp120.

How to reproduce it (minimal and precise)

Just start zigbee2mqtt with a innr SP120 in the list of devices.

Debug Info

Zigbee2mqtt version: 1.13.0 (also 1.12.x)
Adapter hardware: CC2531
Adapter firmware version: 20190608

Impact

Very low

@Koenkk
Copy link
Owner

Koenkk commented May 4, 2020

Fix will be available in the latest dev branch in a few hours. Thanks for reporting.

@macmeck
Copy link

macmeck commented May 20, 2020

@Koenkk , can you tell into which release this fix will find its way?

@Koenkk
Copy link
Owner

Koenkk commented May 21, 2020

@macmeck 1.13.1 (released yesterday)

@macmeck
Copy link

macmeck commented May 23, 2020

@Koenkk , great work, thanks! seems to be working for me after the upgrade to 1.13.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants