Broadlink Manager Windows see invalid device, docker version sees nothing?

[ZoltrixGFC]

Hi,

I have an Broadlink RM4 Pro S. Tried both the Windows Broadlink Manager software and the docker version.

The Windows version reports:
Looking for devices...
Found device : Unknown [192.168.0.42]
Writing compatible device not detected!

The docker version finds nothing when doing a scan.

I can confirm the docker version is setup on the same network, so unsure why it isn't picking anything up?

Any advice?

[gui28347]

same problem for me, RM4 PRO and RM4 Mini

[t0mer]

Hi,
I stopped working on the desktop version long ago.
I can try add the supported devices from the docker version but I'm not sure it will work.

[ZoltrixGFC]

@t0mer would be great if you could add them, but why do you think it won't work?

I'm a bit stuck at the moment, as Home Assistant won't scan one of my remotes (scans others ok). I posted the issue, but no response yet: home-assistant/core#63578 (comment)

[rackey12]

I have the same issue
i have an RM4 Mini (RM4C i think)
and an S3 hub but the docker is not picking up anything

[ZoltrixGFC]

Yep still the same issue here.

[pakshuang]

Same. RM4C Mini and nothing shows up on the scan. Home Assistant Broadlink integration works but the docker broadlink manager can't find the remote :(

[ZoltrixGFC]

I think @t0mer is on leave, not sure when he is due back.

[t0mer]

I think @t0mer is on leave, not sure when he is due back.

Hi @ZoltrixGFC
I'm not on leave (:
Working on other projects and also on a big update to the docker version of broadlink manager.
Hopefully I'll get back to the Windows desktop version by mid-April.

[t0mer]

Same. RM4C Mini and nothing shows up on the scan. Home Assistant Broadlink integration works but the docker broadlink manager can't find the remote :(

Hi @pakshuang,
What is the model of your RM Device?

[pakshuang]

Hey @t0mer,
It says RM4C mini on the device, which is 0x62be in your docs.

[LostOnTheLine]

Windows version of Docker (if on WSL2 at least) does not allow net=host without going through a complicated process each time it's run to port forward to a changing on boot IP for the WSL2. That's why it sees nothing.

If there was a way to NOT do the net=host, even if it requires forwarding a bunch of ports, That'd be a big help. Does anyone know which ports it's using? As an application-level tool, that doesn't need to be running except when needed, I wouldn't mind forwarding a bunch of ports since it'll only be using them while I run the tool.

If there's perhaps a way to manually tell it what IP & MAC to look for?

I didn't see a windows version, just the Docker, I know everyone says it doesn't work but where can I find the Windows version?

[ZoltrixGFC]

@LostOnTheLine, @t0mer said he updated the Windows version mid-April, did you get the latest version?