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 is not reachable #5366

Closed
marithpl opened this issue Oct 12, 2021 · 1 comment
Closed

Hue Motion Sensor is not reachable #5366

marithpl opened this issue Oct 12, 2021 · 1 comment

Comments

@marithpl
Copy link

Describe the bug

I've updated do 13.0.1 and am not able to pair Hue Motion Sensor.
After adding a device to Deconz via Phoscon it's Not reachable for all the times but it have good route connection.

Steps to reproduce the behavior

Expected behavior

Screenshots

image

image

Environment

  • Host system: NAS Synology
  • Running method: Marthoc Docker container
  • Firmware version: (latest)
  • deCONZ version: (2.13.1)
  • Device: ConBee II
  • Do you use an USB extension cable: yes
  • Is there any other USB or serial devices connected to the host system? If so: Which?

deCONZ Logs

21:06:25:212 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0001
--
21:06:24:773 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0402
21:06:22:128 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0400
21:06:20:564 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0406
21:06:18:714 [1] get node descriptor for 0x00178801032b8c3b
21:06:18:518 0x00178801032B8C3B error APSDE-DATA.confirm: 0xE1 on task
21:06:18:155 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0000
21:06:17:847 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0402
21:06:17:845 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0400
21:06:17:842 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0406
21:06:17:842 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0001
21:06:17:841 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0000
21:06:17:838 device announce 0x00178801032B8C3B (0x7045) mac capabilities 0x80
21:06:17:838                       ...     (0x00178801032B8C3B / 0x7045)
21:06:17:838 FP indication 0x0000 / 0x0013 (0x00178801032B8C3B / 0x7045)
21:06:17:838 set fast probe address to 0x00178801032B8C3B (0x7045)
21:06:17:837 device announce 0x00178801032B8C3B (0x7045) mac capabilities 0x80
21:06:17:835 DeviceAnnce of SensorNode: 0x00178801032B8C3B [1]
21:06:17:833 DeviceAnnce of SensorNode: 0x00178801032B8C3B [1]
21:06:17:830 DeviceAnnce of SensorNode: 0x00178801032B8C3B [1]
20:50:47:440 DEV found DDF for 0x00178801032B8C3B, path: /usr/share/deCONZ/devices/philips/sml001_motion_sensor.json
20:50:44:667 SensorNode 75 set node 0x00178801032b8c3b
20:50:44:666 SensorNode 74 set node 0x00178801032b8c3b
20:50:44:665 SensorNode 73 set node 0x00178801032b8c3b

Additional context

@Mimiix
Copy link
Collaborator

Mimiix commented Oct 12, 2021

As this is not a bug report as described in #5113, I am closing this issue.

Please use the forum for this question.

Kind regards

@Mimiix Mimiix closed this as completed Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants