That's a pretty unfortunate way to look at it.
There is some troubleshooting and setup discussion in this other thread: Hubitat and Broadlink RM Pro + WIFI + IR + RF Remote Controller - #54 by rob121
Setup is not too bad if you are using one of the platforms that builds are pre-supplied for. I recommend Raspberry Pi personally, because it was easier to setup a startup service using the supplied systemd service file.
-
Grab the appropriate files from the latest release: Releases 路 rob121/broadlinkgo 路 GitHub
-
Transfer files to your Raspberry Pi and extract everything. Set file permissions to be executable if necessary, and then make sure you can invoke the main service from the command line. Just use default options (i.e. ./broadlinkgo)
-
Verify everything works on the server side by browsing to http://(IP of Raspberry Pi):8000/ . Test drive some of the functionality described in the readme, including capturing commands from remotes (you'll need this to try anything out with Hubitat): broadlinkgo/README.md at master 路 rob121/broadlinkgo 路 GitHub
-
If everything works in the web portal, try it with Hubitat. Install this driver code (or similar), and create a virtual device of that type. Then enter the onURI and offURI options to match the URL format for commands described in the broadlinkgo readme. HubitatPublic/examples/drivers/httpGetSwitch.groovy at master 路 hubitat/HubitatPublic 路 GitHub
-
If all of that works, you can use the supplied broadlinkgo.service file to get things running automatically at startup. Be sure to edit the .service file if you changed any options and to reflect where the main broadlinkgo program is stored on your Raspberry Pi. Here's a useful systemd intro if needed: systemd/Services - Debian Wiki