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

TS011F_plug_3 not reporting power in the last versions (issue started in the version 1.39.1) #23887

Closed
MiguelCosta opened this issue Sep 7, 2024 · 10 comments
Labels
problem Something isn't working

Comments

@MiguelCosta
Copy link

MiguelCosta commented Sep 7, 2024

What happened?

My Blitzwolf BW-SHP13 socket has power measurement, but in the latest versions it has stopped working. It's always the last value that has been reported or if I re-pair, the value changes to null.
The kwh sensor is working, but the current energy (w) is not reported.

The issue started after upgrade to 1.39.1 version.

image

image

image

What did you expect to happen?

The sensors Current, Power and Voltage should be reported.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.40.1

Adapter firmware version

20210708

Adapter

Sonoff ZBDongle-P

Setup

Docker

Debug log

No response

@MiguelCosta MiguelCosta added the problem Something isn't working label Sep 7, 2024
@MiguelCosta MiguelCosta changed the title TS011F_plug_3 not reporting power in the last versions (issue started in the version since 1.39.1) TS011F_plug_3 not reporting power in the last versions (issue started in the version 1.39.1) Sep 7, 2024
@MiguelCosta
Copy link
Author

More users with the same issue: #22673 (comment)

@Koenkk
Copy link
Owner

Koenkk commented Sep 8, 2024

  • Could you provide a screenshot of the device about page?
  • Could you provide the debug log when starting z2m + 5 mins?
    See this on how to enable debug logging.

@MiguelCosta
Copy link
Author

@Koenkk the logs have this error, I think it is related:

[2024-09-09 21:52:28] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-09-09 21:52:28] debug: 	zhc:utils: Polling 'measurement' for '0x84ba20fffe71029d' at an interval of 10
[2024-09-09 21:52:28] debug: 	zhc:utils: Polling 'measurement' for '0x540f57fffe8ebd91' at an interval of 60
[2024-09-09 21:52:28] debug: 	zhc:utils: Polling 'measurement' for '0x540f57fffe8eb862' at an interval of 10
[2024-09-09 21:52:28] error: 	z2m: Failed to call 'OnEvent' 'start' (Error: 'measurement_poll_interval' is not a number, got string ()
    at toNumber (/app/node_modules/zigbee-herdsman-converters/src/lib/utils.ts:634:15)
    at Object.onEventPoll (/app/node_modules/zigbee-herdsman-converters/src/lib/utils.ts:45:25)
    at Object.onEventMeasurementPoll (/app/node_modules/zigbee-herdsman-converters/src/lib/tuya.ts:186:11)
    at Object.onEvent (/app/node_modules/zigbee-herdsman-converters/src/devices/tuya.ts:5105:56)
    at OnEvent.callOnEvent (/app/lib/extension/onEvent.ts:48:37)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at OnEvent.start (/app/lib/extension/onEvent.ts:12:13)
    at Controller.callExtensions (/app/lib/controller.ts:377:17)
    at Controller.start (/app/lib/controller.ts:196:9)
    at start (/app/index.js:154:5))

All the logs here:
log.log

Could you provide a screenshot of the device about page?

image

@MiguelCosta
Copy link
Author

@Koenkk in the in the version 1.39.1, the zigbee-herdsman-converters lib was upgraded from 19.62.0 to 19.72.0 version and maybe the bug started with this change: Koenkk/zigbee-herdsman-converters@6f5707b

can you help?

@MiguelCosta
Copy link
Author

Mitigated 💪

This field was empty, I added a value value here to work and now it is working 🙏

image

@MiguelCosta
Copy link
Author

@Koenkk I think this issue occurs because the UI is creating a configuration with a empty string

image

@Koenkk
Copy link
Owner

Koenkk commented Sep 10, 2024

@MiguelCosta it also creates an empty value when saving it again in the frontend (when e.g. 60 is filled in)?

@MiguelCosta
Copy link
Author

MiguelCosta commented Sep 10, 2024

@MiguelCosta it also creates an empty value when saving it again in the frontend (when e.g. 60 is filled in)?

@Koenkk, the frontend just fills an empty value if I don't put any numbers, if I change it to 60 or 10 is already filled in the latest version (1.40.1), it seems to me that in the previous version the UI would change nothing.

@hotbirdx
Copy link

@Koenkk I can confirm that the issue is the same for the TS0121 / BlitzWolf BW-SHP13 device. If I change in the GUI to a value eg. 60 it works.

@Koenkk
Copy link
Owner

Koenkk commented Sep 12, 2024

Fixed the issue, when set to "", the default poll interval will be used now.

Changes will be available in the dev branch in a few hours from now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants