Closed tiagofreire-pt closed 4 years ago
probot-home-assistant[bot]
commented
4 years ago Hey there @danielhiversen, @felipediel, mind taking a look at this issue as its been labeled with a integration (broadlink) you are listed as a codeowner for? Thanks!
tiagofreire-pt
commented
4 years ago Somehow, this RC4C mini seems to be kind of compatible with Broadlink Manager (https://sourceforge.net/projects/broadlink-manager/)
Looking for devices...
Found device : Unknown [192.168.10.83]
Writing compatible device not detected!
springstan
commented
4 years ago This is a duplicate of #25943, therefore please close this issue and follow the discussion to this issue there. @tiagofreire-pt thank you for understanding :)
tiagofreire-pt
commented
4 years ago @springstan, I understand but there are no references regarding the technical issue about the rm4c mini specifically.
This is about the support for a new device (RM4C mini) and not for an existing one, as the RM3 on that github issue.
springstan
commented
4 years ago @tiagofreire-pt okay thanks for the clarification. Still this is an issue tracker for bugs and not for feature requests e.g. the support of a new device. Therefore, please close this issue and create a feature request in the community. Thanks!
snakuzzo
commented
4 years ago 
tt-github-1962
commented
4 years ago Is this new version will be compatible with this Broadlink RM4 PRO ? https://www.ibroadlink.com/products/ir+rf Thanks in advance
tiagofreire-pt
commented
4 years ago @tt-github-1962, it's supposed to. I'm suggesting the PR #33240 to allow better support, in parallel with other PRs merged already from other contributors.
zchumager
commented
4 years ago Home Assistant release with the issue: 0.102
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Integration: Broadlink
Description of problem: No support for the RM4C Mini devices.
Problem-relevant
configuration.yamlentries and (fill out even if it seems unimportant): switch:
- platform: broadlink host: AAA.BBB.CCC.DDD mac: 12:34:56:78:90:AB type: rm4c_mini friendly_name: 'Broadlink RM4C Mini'
Traceback (if applicable):
2019-12-08 10:46:49 ERROR (MainThread) [homeassistant.components.broadlink] Failed to connect to deviceAdditional information:
$ sudo nmap -O 192.168.10.83 Starting Nmap 7.80 ( https://nmap.org ) at 2019-12-08 09:28 WET Nmap scan report for RM4-XX-YY-ZZ.local (192.168.10.83) Host is up (0.0046s latency). All 1000 scanned ports on RM4-XX-YY-ZZ.local (192.168.10.83) are closed MAC Address: 12:34:56:78:90:AB (Hangzhou BroadLink Technology) Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port Device type: specialized|general purpose Running: DTE embedded, lwIP 1.4.X, Enlogic embedded, Ocean Signal embedded, Philips embedded OS CPE: cpe:/a:lwip_project:lwip cpe:/h:philips:hue_bridge cpe:/a:lwip_project:lwip:1.4 OS details: DTE Energy Bridge (lwIP stack), Enlogic PDU (FreeRTOS/lwIP), Ocean Signal E101V emergency beacon (FreeRTOS/lwIP), Philips Hue Bridge (lwIP stack v1.4.0) Network Distance: 1 hop OS detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 4.24 seconds
I create a Python CLI tool to prepare RM Mini 4 to be compatible with Home Assistant https://github.com/zchumager/RM-Configurator/blob/master/README.md
Home Assistant release with the issue: 0.102
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
Integration: Broadlink
Description of problem: No support for the RM4C Mini devices.
Problem-relevant
configuration.yamlentries and (fill out even if it seems unimportant): switch:Traceback (if applicable):
Additional information: