-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RTCGQ01LM / WSDCGQ11LM - No battery info #1801
Comments
This is because during pairing the device did not answer all requests. Note that the battery percentage itself can take some time to pop-up (max 24 hours). |
@Koenkk Yes it is. Now I get (after 20h) data, but if I also see that there are always interruptions of data delivery. It looks like data is not always delivered. Is that the case with the Zigbee devices or something is wrong with my configuration ? MiJia temperature & humidity sensor Xiaomi WSDCGQ11LM - RTCGQ01LM |
You will see this when sensor become unavailable, did you restart zigbee2mqtt or the pc? |
zigbee2mqtt, USB Stick CC2531 coordinator is installed on a Raspberry 3+ and runs 24/7. One possibility would be that the Raspberry has a timeout problem with the port: / dev / ttyACM0 But it could also be on the router, I do not know why, but this sometimes goes offline. Whenever I restart the coordinator, then I have to manually reconnect the router, because this does not connect automatically.
But when restarting the coordinator I see in the log that all data is supplied by the devices: {
"occupancy" : false,
"linkquality" : 0,
"last_seen" : "2019-08-01T10:02:11.882Z",
"battery" : 100,
"voltage" : 3075,
"device" : {
"ieeeAddr" : "0x00158d000358e8cd",
"friendlyName" : "bewegungsmelder1",
"type" : "EndDevice",
"nwkAddr" : 36520,
"manufId" : 4151,
"manufName" : "LUMI",
"powerSource" : "Battery",
"modelId" : "lumi.sensor_motion",
"hwVersion" : "unknown",
"swBuildId" : "unknown",
"dateCode" : "unknown",
"status" : "online"
}
}
{
"temperature" : 24.36,
"linkquality" : 39,
"last_seen" : "2019-08-01T11:09:24.588Z",
"humidity" : 57.35,
"pressure" : 968,
"battery" : 100,
"voltage" : 3025,
"device" : {
"ieeeAddr" : "0x00158d00036b7ae0",
"friendlyName" : "temperatursensor2",
"type" : "EndDevice",
"nwkAddr" : 58446,
"manufId" : 4151,
"manufName" : "LUMI",
"powerSource" : "Battery",
"modelId" : "lumi.weather",
"hwVersion" : 30,
"swBuildId" : "3000-0001",
"dateCode" : "20161129",
"status" : "online"
}
}
{
"battery" : 100,
"voltage" : 3045,
"linkquality" : 42,
"last_seen" : "2019-08-01T11:46:09.563Z",
"device" : {
"ieeeAddr" : "0x00158d00028079c1",
"friendlyName" : "wassersensor1",
"type" : "EndDevice",
"nwkAddr" : 24962,
"manufId" : 4151,
"manufName" : "LUMI",
"powerSource" : "Battery",
"modelId" : "lumi.sensor_wleak.aq1",
"hwVersion" : 2,
"swBuildId" : "3000-0001",
"dateCode" : "20170721",
"status" : "online"
}
}
`` |
Unfortunately I do not have the log file anymore. I have re-set the environment, but I can not figure out where the mistake is. I have replaced the router with 2 Osram Smart + Plugs and all devices in one room (distance up to 2m).
Why do not the OSRAM Smart + Plugs (routers) reconnect when the coordinator is restarted? Same problem I had with the CC2531 router. Log see: https://pastebin.com/kupv3BeT configuration homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://mqttserver:1883'
user: mqttUserName
password: thisIsNotPublic
reject_unauthorized: false
client_id: rb3zigbee2mqtt
include_device_information: true
serial:
port: /dev/ttyACM0
disable_led: true
advanced:
channel: 14
cache_state: false
baudrate: 115200
rtscts: true
last_seen: ISO_8601
elapsed: true
log_directory: /var/log/zigbee2mqtt/
log_level: debug
report: true
homeassistant_discovery_topic: homeassistant
devices:
'0x00158d00028208ae':
friendly_name: '0x00158d00028208ae'
retain: false
'0x00158d00028079c1':
friendly_name: 'wassersensor1'
retain: false
'0x00158d00028079c0':
friendly_name: 'wassersensor0'
retain: false
'0x00158d00036b7ae0':
friendly_name: 'wassersensor2'
retain: false
'0x00158d00036b56d1':
friendly_name: 'temperatursensor1'
retain: false
'0x00158d000358e8cd':
friendly_name: 'bewegungsmelder1'
retain: false
'0x7cb03eaa0a00ebba':
friendly_name: 'smartplug1'
retain: false
'0x7cb03eaa0a0145d9':
friendly_name: 'smartplug2'
retain: false Log see: https://pastebin.com/kupv3BeT CC2531 ZigBee USB-Sick: https://www.ebay.at/itm/CC2531-ZigBee-USB-Sick-zigbee2mqtt-ioBroker-FHEM-SMA-8dbi-Antenne-Firmware/113384283158?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649 |
I'm not sure, but I think I found the explanation. Whenever the "linkquality" of a sensor drops, not all data is delivered at state_topic: - platform: "mqtt"
name: "Motion Bad Battery Status"
state_topic: "zigbee2mqtt / motion1"
availability_topic: "zigbee2mqtt / bridge / state"
unit_of_measurement: "%"
device_class: "battery"
value_template: "{{value_json.battery}}"
- platform: "mqtt"
name: "Motion Bad Signal Status"
state_topic: "zigbee2mqtt / motion1"
availability_topic: "zigbee2mqtt / bridge / state"
unit_of_measurement: "dbm"
value_template: "{{value_json.linkquality}}" Therefore, the data can not be read out for all attributes in the graphics for this time. But if the link quality increases, then all the data is delivered. This affects only the devices "RTCGQ01LM, WSDCGQ11LM, SJCGQ11LM", but this effect does not occur with the OSRAM AB3257001NJ.
Is there a solution for this ? Log see: https://pastebin.com/t9RcCPtg |
Can you post your configuration.yaml? |
Yes, this is the what i use: homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://IPADDESS:1883'
user: mqttUserName
password: thisIsNotPublic
reject_unauthorized: false
client_id: rb3zigbee2mqtt
include_device_information: true
serial:
port: /dev/ttyACM0
disable_led: true
advanced:
channel: 14
cache_state: false
baudrate: 115200
rtscts: true
last_seen: ISO_8601_local
elapsed: true
log_directory: /var/log/zigbee2mqtt/
log_level: debug
report: true
homeassistant_discovery_topic: homeassistant
devices:
'0x00158d00028208ae':
friendly_name: 'wassersensor2'
retain: false
'0x00158d00028079c1':
friendly_name: 'wassersensor1'
retain: false
'0x00158d00028079c0':
friendly_name: 'wassersensor0'
retain: false
'0x00158d00036b7ae0':
friendly_name: 'temperatursensor2'
retain: false
'0x00158d00036b56d1':
friendly_name: 'temperatursensor1'
retain: false
'0x00158d000358e8cd':
friendly_name: 'bewegungsmelder1'
retain: false
'0x7cb03eaa0a00ebba':
friendly_name: 'smartplug1'
retain: false
'0x7cb03eaa0a0145d9':
friendly_name: 'smartplug2'
retain: false |
You use
With
When Home Assistant doesn't receive complete payloads it's is expected you will see these gaps. You should also see a warning when starting zigbee2mqtt that the home assistant integration won't work properly. Closing as this is expected behaviour. |
Thanks, so i will set "cache_state: true". Is there a solution for the Osram Smart? see: |
That offline/online status is not reliable (will be fixed after zigbee-herdsman refactor: Koenkk/zigbee-herdsman#13). |
Thanks for the support, great job 👍 |
xiaomi human body movement sensor - RTCGQ01LM (2019.01)
configuration.yaml
Why can not I get any information about the battery status, voltage from this device.
Do I do something wrong with the configuration?
Debug Info
Same problem I have with the Xiaomi WSDCGQ11LM - temperature & humidity sensor
Even with this device I miss the information about the battery status
The text was updated successfully, but these errors were encountered: