Issues in latest dev branch

[AnhDuc85]

Hi, just pulled the latest dev image and it seems there are some issues.

Some examples:

• Xiaomi Temp Sensor (should report battery and voltage) {"battery":"NaN","voltage":"!","linkquality":57,"temperature":21.76,"humidity":67.92}

• Xiaomi Zigbee plug (should be ON & reporting consumption values){"state":"OFF","power":null,"voltage":null,"consumption":null,"temperature":null,"linkquality":102}

When I switch back to the latest images, these sensors reporting normal values.

[tb-killa]

Please provide full log via debug and do some samples. I think i know the reason But need some input debug stuff first..

[AnhDuc85]

example with device WSDCGQ01LM debug log with latest-dev: https://pastebin.com/raw/YpS6FNh2 debug log with latest: https://pastebin.com/raw/RDa5qF7U

[tb-killa]

Recieved zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":"\u0001!�\u000b\u0004!�\u0013\u0005!\u0006\u0000\u0006$\u0000\u0000\u0000\u0000\u0000d)�\be!�\u0015\n!\u0000\u0000"}}' of device 'lumi.sens' (0x00158d0001c2cf7e)

The structure isnt parse correct.

[Koenkk]

This is due to https://github.com/Koenkk/zigbee-shepherd-converters/pull/63

@evildad @lolorc did you ever experience this?

[evildad]

Just grepped in my logs for the pattern voltage":"!" and found zero entries. So the answer is no, never had that issue... Edit: I don't understand why the Xiaomi Plug has this issue, too. We didn't change this Model

[azuwis]

I have the same problem on WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor, debug log:

9/17/2018, 4:02:35 PM - debug: Recieved zigbee message of type 'attReport' with data '{"cid":"genBasic","data":{"65281":"\u0001!�\u000b\u0004!�\u0013\u0005!\u001c\u0000\u0006$\u0002\u0000\u0000\u0000\u0000d)�\ne!�\u001e\n!\u0000\u0000"}}' of device 'lumi.sens' (0x00158d0001e81c40)
9/17/2018, 4:02:35 PM - info: MQTT publish, topic: 'zigbee2mqtt/ht_bedroom', payload: '{"battery":"NaN","voltage":"!","linkquality":26,"temperature":26.98,"humidity":82.43}'
9/17/2018, 4:02:35 PM - debug: Recieved zigbee message of type 'devChange' with data '{"cid":"genBasic","data":{"65281":"\u0001!�\u000b\u0004!�\u0013\u0005!\u001c\u0000\u0006$\u0002\u0000\u0000\u0000\u0000d)�\ne!�\u001e\n!\u0000\u0000"}}' of device 'lumi.sens' (0x00158d0001e81c40)

Zigbee2mqtt git revision 6ede5a3

[Koenkk]

Can you try if this issue also happens in issue_373.

Note: do a rm -rf node_modules && npm install after checking out this branch.

[azuwis]

I can confirm that the problem does not happen on branch issue_373.

[tb-killa]

We should check if this is correct?? var deviceId = zclId.device(260, 10).key; Maybe there comes faulty result.?

[dzungpv]

@tb-killa You are right, this PR will solve the problem https://github.com/Koenkk/zcl-packet/pull/6

[hdo]

I can confirm that battery values are not read correctly with 'latest-dev':

'zigbee2mqtt/0x00158d00022c9005', payload: '{"temperature":23.21,"linkquality":92,"humidity":46.08,"pressure":1002,"battery":"NaN","voltage":"!"}' 'zigbee2mqtt/0x00158d0001f535eb', payload: '{"temperature":25.1,"linkquality":21,"humidity":45.19,"pressure":1002,"battery":"NaN","voltage":"!"}' 'zigbee2mqtt/0x00158d0001e50c7c', payload: '{"illuminance":110,"linkquality":13,"occupancy":false,"battery":"NaN","voltage":"!"}'

[Koenkk]

Can you check if this has been fixed in the latest dev branch?

[hdo]

Can you check if this has been fixed in the latest dev branch?

Running Docker latest-dev (commit #8376b7c). Still issues with battery reading but some values seem to be correct. Maybe it's an issue with retained values.

I'll keep an eye on that.

'{"temperature":13.38,"linkquality":0,"humidity":38.24,"pressure":1002,"battery":"NaN","voltage":"!"}' '{"temperature":13.38,"linkquality":0,"humidity":32.16,"pressure":1002,"battery":"NaN","voltage":"!"}' '{"temperature":27.55,"linkquality":63,"humidity":35.98,"pressure":1002,"battery":"98.33","voltage":2995}' '{"temperature":27.6,"linkquality":63,"humidity":39.43,"pressure":1002.37,"battery":"98.33","voltage":2995}'

[hdo]

I can confirm that battery voltage is read correctly again with latest-dev. Thank you.

[AnhDuc85]

can also confirm, will close the issue

[lolorc]

@Koenkk yes I experiencing this issue at the moment. :-) probably because you reverted @dzungpv PR.

[Koenkk]

Fixed again!