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

Hue motion sensor. Working but with lots of timeouts in the logs. #2195

Closed
pavon87 opened this issue Oct 23, 2019 · 4 comments
Closed

Hue motion sensor. Working but with lots of timeouts in the logs. #2195

pavon87 opened this issue Oct 23, 2019 · 4 comments
Labels
stale Stale issues

Comments

@pavon87
Copy link

pavon87 commented Oct 23, 2019

Hi,

Situation:
I have a network of 20 devices, basically Xiaomi devices, ikea and hue lights, and two routers, CC2530 and CC2591. As a coordinator I use an official docker container (updated) in a raspberry pi with CC2530 with last firmware. Also I reproduced the same problem with another raspberry, with another container and a CC2531 antenna.

Problem:

I’m trying some Hue Motion sensors, (Philips 9290012607), it sems that works properlly but I’m receiving a timeout error in the logs and some hangs after some hours working.

In summary, in the logs there are several missages like the next, with "attempt" #1, #2, #3:
Th zigbee2mqtt:warn 10/23/2019, 10:20:22 PM Failed to configure hue_sensor (0x0017880104b7a74b) ('Error: SRSP - ZDO - bindReq after 6000ms') (attempt #1)

And lots of other messages like:
zigbee2mqtt:error 10/23/2019, 9:58:35 PM Cannot get the Node Descriptor of the Device: 0x0017880104b7a74b (Error: Timed out after 10000 ms)

I have the same issue with two different Hue Motion sensors. Also I tried changing the QoS level without .

Thanks in advance

Off_topic comment

This is not related with the issue and is not a question, but maybe somebody is in the same situation and found better solution. Trying to obtain a High Availability system of Zigbee2mqtt, I created a “network” where there are two coordinators, one master and one slave (stopped), in two different raspberry’s, each with their antenna and each one running zigbee2mqtt container, where one is up and the other is stopped. With rsync I keep updated the devices list, and with a custom watchdog script, I control witch container is working, and I start one or the other when is needed. It is the only way I have found to make a system with some High Availability. Somebody knows a better option to make redundancy?

@Koenkk
Copy link
Owner

Koenkk commented Oct 24, 2019

Can you try with the latest dev branch? I expect that it fixes these issues.

@pavon87
Copy link
Author

pavon87 commented Oct 24, 2019

Hi,
I just update the container to lastest-dev version, and I getting a new error (periodically every two minutes), only related with the Hue Motion:

zigbee2mqtt:info 2019-10-24T08:00:59: MQTT publish: topic 'pavon/z2m/hue_sensor', payload '{"battery":100,"linkquality":107,"occupancy":false,"illuminance":13048,"temperature":19.62}'
zigbee2mqtt:info 2019-10-24T08:00:59: Configuring 'hue_sensor'
zigbee2mqtt:info 2019-10-24T08:01:08: MQTT publish: topic 'pavon/z2m/hue_sensor', payload '{"battery":100,"linkquality":110,"occupancy":false,"illuminance":13048,"temperature":17.79}'
zigbee2mqtt:error 2019-10-24T08:01:09: Failed to configure 'hue_sensor', attempt 2 (Error: AREQ - ZDO - bindRsp after 10000ms
at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10))

Thanks for your support!

@Koenkk
Copy link
Owner

Koenkk commented Oct 24, 2019

When starting zigbee2mqtt, you need to wake up the sensor (by e.g. triggering movements or pressing to button on it) until you see Successfully configured 'hue_sensor'.

If that doesn't help, try to re-pair the device.

@stale
Copy link

stale bot commented Dec 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issues label Dec 23, 2019
@stale stale bot closed this as completed Dec 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants