Hi Barny,
That’s a weird one, from what I can tell the BG Electrical BG1 has its own device code that shouldn’t ever have worked. (The python-broadlink library that I frequently and shamelessly copy from has unique codes for a couple of BG Electrical products, and it treats them as special compared to the Broadlink devices they must be based off…)
Anyway, I’ve gone and added a lot of new codes based on that library, that should improve compatibility, but I can’t say for sure that it will fix your case, because I think your device must be reporting as some other device code which happened to just work before.
More interestingly for the wider Broadlink audience, the binding is edging closer to getting into the openHAB 3.1 codebase, and the latest release that I’ve just published (3.1.M5.2) has a new feature suggested by @matt1 that you might like.
By implementing the DynamicCommandDescriptionProvider interface and watching the .map file you have configured for your Broadlink remote thing (e.g. RM2, RM3, RM4) you can now trigger remote codes to be sent from the openHAB web GUI, and updating the .map file will update the GUI instantly.
Navigate to Things → [Your Broadlink remote Thing] → Channels → Command:
Click the Item you should see there that represents the command channel of the Thing:
Now you’ll see the name of the last command you sent down this channel. It’s not super-obvious, but if you click this text, you’ll get a pop-up appear with all of the available commands - click one and it will be sent by the Broadlink device!
If you add/modify/remove anything from broadlink.map (or whatever you’ve called it) this pop-up list will update to stay in sync.
Cheers,
John