The CLI discovers the device on my local network as follows:
$ broadlink_discovery
Discovering...
###########################################
Unknown
# broadlink_cli --type 0x4e2a --host 172.16.10.178 --mac c8f7425fe477
Device file data (to be used with --device @filename in broadlink_cli) :
0x4e2a 172.16.10.178 c8f7425fe477
Running any further commands leads to nowhere:
$ broadlink_cli --type 0x4e2a --host 172.16.10.178 --mac c8f7425fe477 --learn
Traceback (most recent call last):
File "/usr/bin/broadlink_cli", line 131, in <module>
dev.enter_learning()
AttributeError: 'device' object has no attribute 'enter_learning'
Home assistant reports the device as unsupported:
2021-07-31 18:40:46 ERROR (MainThread) [homeassistant.components.broadlink.config_flow] Unsupported device: 0x4e2a. If it worked before, please open an issue at https://github.com/home-assistant/core/issues
This device is not strictly a broadlink device, but it does use their protocol.
I found that out because it is doing DNS queries to my pihole instance with the following FQDNs:
All of the below testing was done in a docker container that was set up like this:
The CLI discovers the device on my local network as follows:
Running any further commands leads to nowhere:
Home assistant reports the device as unsupported: