Raspbee II under Windows (11)

[PatcherMustermann]

Does the issue really belong here?

• [x] I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• [X] I have searched the existing issues and there is none for the bug at hand

Describe the bug

I would like to use the Raspbee II on Windows (11). However, I am not able to integrate it as a device in deConz.

I have tried the following parameters (x replaced by number): 01 - deconz -d COMx 02 - deconz -d "COMx" 03 - deconz -d \\.\COMx 04 - deconz -d "\\.\COMx" 05 - deconz --dev=COMx 06 - deconz --dev="COMx" 07 - deconz --dev=\\.\COMx 08 - deconz --dev="\\.\COMx" 09 - deconz --device=COMx 10 - deconz --device="COMx" 11 - deconz --device=\\.\COMx 12 - deconz --device="\\.\COMx"

I have run COM-Port monitoring and deConz does not even try to open the COM-Port. On Zigbee2MQTT (Windows), however, the Raspbee II works perfectly.

With the GCFFlasher_Win_V4_03_00 (Windows) I can establish a connection with the parameter "-d" (GCFFlasher.exe -d COMx -f xxx.bin.gcf). With the list function "-l", however, the Raspbee II is not displayed either.

Steps to reproduce the behavior

/

Expected behavior

/

Screenshots

No response

Environment

• Host system: PC (Windows 11)
• Device: RaspBee II

deCONZ Logs

No response

Additional context

No response

[manup]

Indeed the --dev parameter currently just works on Linux, so right know the best approach is to use the --auto-connect=1 (which is the default) and let deCONZ figure out the COM port. Note on Windows there is no RaspBee, do you mean ConBee?

[PatcherMustermann]

I mean realy the Raspbee II. I have successfully connect the Raspbee II to deconz on Windows with a trick, but for this I need a Conbee on the USB port. Why does the device parameter only work in Linux and not in Windows? I think for dresden elektronik is this not a big deal to change the source code for the deconz Windows version.

[manup]

Yeah I think adapting the code to also support --dev on Windows doesn't require much. I put it on schedule for v2.26.0-beta. Note however that you might also need to set the --baudrate=38400 to connect to RaspBee.

[PatcherMustermann]

That sounds good. Thank you very much!

Would the call of deconz with parameters look like this?: \path...\deconz.exe --dev=COMx --baudrate=38400

Edit: I have seen that the beta versions are not compiled. Would it be possible to get them compiled for Windows after integrating the Raspbee II?

[manup]

Yeah I guess the call looks right if it is connected to a USB serial converter.

All versions are also released for Windows like the latest beta v2.25.2. However build instructions needs to be updated for Windows since the stock Qt5 libraries need to be used, unfortunately the msys2 Qt5 libraries generate bogus virus warnings.

[PatcherMustermann]

I tried the releases v2.26.0-beta from yesterday and my problem is not fixed yet. Is this correct?

[Mimiix]

I tried the releases v2.26.0-beta from yesterday and my problem is not fixed yet. Is this correct?

Yes. Otherwise this issue would have been closed.

[PatcherMustermann]

Thanks for this information. Then I'll have to be patient a little longer.

[PatcherMustermann]

I tested version 2.26.1 beta today and the parameter —dev=COMx worked fine. One thing that could be improved is to change the displayed name ConBee to Rasbee. Otherwise very good job - thank you!

[github-actions[bot]]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[manup]

Close as completed for now, the RaspBee device name needs some more additions in the firmware later on.