You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I definitively want to report a bug within deCONZ or its REST-API
Is there already an existing issue for this?
I have searched the existing issues and there is none for the bug at hand
Describe the bug
When teaching in the Bosch thermostat, I have so far sent the Zigbee EUI via Node red and the installation code via the REST API. This was possible with the Conbee 2 stick without any problems. This is no longer possible with the Conbee 3
Steps to reproduce the behavior
Set the Bosch thermostat to connection mode
Phoscon on pairing devices
Send the installation code via Node Red
Expected behavior
That the thermostat is integrated as with the Conbee 2
Screenshots
No response
Environment
Host system: Raspberry Pi 4b
Running method: Raspbian
Firmware version: (26530900)
deCONZ version: (2.28.1)
Device: ConBee III
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? If so: 64GB SSD
deCONZ Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Yes, around 40 different devises work without any problems. After pairing the Bosch thermostats with the Conbee 2, they also work without problems with the Conbee 3
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
When teaching in the Bosch thermostat, I have so far sent the Zigbee EUI via Node red and the installation code via the REST API. This was possible with the Conbee 2 stick without any problems. This is no longer possible with the Conbee 3
Steps to reproduce the behavior
Set the Bosch thermostat to connection mode
Phoscon on pairing devices
Send the installation code via Node Red
Expected behavior
That the thermostat is integrated as with the Conbee 2
Screenshots
No response
Environment
deCONZ Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: