deconz-rest-plugin: `--dev` flag regression past 2.05.77 for `deCONZ`
Describe the bug
deCONZ no longer connects to the raspbee. I’d like to update my deCONZ package due to the age of the package for new features and security reasons.
Steps to reproduce the behavior
Any deCONZ version above 2.05.77 fails to connect to the device over an SSH tunnelled virtual serial device
Expected behavior
No regression from 2.05.78 onward.
Screenshots

Environment
deCONZ/Phoscon versions as per above
- Host system: x86 VM
- Running method: Rpi 0W with a RaspBee II (I also have a RaspBee that I can test with as well)
- Firmware version: 26690700
- deCONZ version:
2.05.77tested on2.11.05-debian-buster-stableand2.12.00-ubuntu-xenial-beta - Device: RaspBee I/RaspBee II
- Do you use an USB extension cable: No
- Is there any other USB or serial devices connected to the host system? If so: Which? No
deCONZ Logs
2.05.77 has:
15:52:21:724 COM: --dev: /home/redm/ttyAMA0 (RaspBee)
Where as any version onward does not have this line.
I am running deCONZ via /usr/bin/deCONZ --dev=/home/redm/ttyAMA0 --upnp=0 on any version I test.
Additional context
While the serial redirect may seem odd, it worked in the past and was the entire reason I wanted a deCONZ set up. The reason for doing it this way is that it makes integration with my VM cluster much easier and deCONZ in its entirety is backed up nightly and I don’t have to worry about the rpi dying or the SD card in the pi dying.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (9 by maintainers)
I just added the feature to Red-M/RedSSH@895be695f037da669d87c84e4270926ab8587f76 which turned
TCP_NODELAYon for the SSH session and the tunnel. Even on ethernet this is way faster than before and the zigbee network is much more responsive than before.