Unsure if this is the right place to raise this issue, however, I cam across https://github.com/mjg59/python-broadlink/issues/355 which relates to a similar issue except with IR. Currently, I am trying to get my RM4 Pro to work with the HA and having issues bring able to learn RF (IR learns and sends no problem at all) with both python-broadlink and Home assistant. (I also have an issue with it as a sensor (temperature and humidity) - although not that concerned/interested in this side at the moment)

Current Setup Home Assistant 0.109.3 Broadlink RM4 Pro Added to network using python-broadlink - PASS when I attempt devices[0].host[0] > ‘192.168.1.172’ - PASS devices[0].get_type() > ‘Unknown’ - Cant get the type (so this may be a concern or compatibility issue) devices[0].enter_learning() > AttributeError: device instance has no attribute ‘enter_learning’ _FAIL

Under Home assistant Added to HA as switch - configuration.yaml switch: platform: broadlink host: 192.168.1.172 mac: 24:df:a7:b9:c0:5a type: rm4_pro timeout: 15 retry: 5 switches: tv_samsung_power: friendly_name: "Samsung TV Power" command_on: IRSTRING command_off: IRSTRING When I run broadlink.learn

• Red LED comes on
• I can capture IR without an issue as I did with the Samsung TV Power
• UNABLE TO CAPTURE ANY RF

As far as the sensor is concerned sensor: platform: broadlink host: 192.168.1.172 mac: 24:df:a7:b9:c0:5a type: rm4_pro monitored_conditions: temperature humidity Both Temperature and Humidity just show a value of 0

Do you know if anyone has been successful with the RM4 Pro and RF?

Another point is that I cant get the RM4 Pro to work with e-control (or broadlink manager) so have not been able to get any RF packets to test it broadlink.send command to see if that works.

Hello

I bought "Broadlink RM4c mini" but it doesn't work with python-broadlink

It see it but don't connect.

on broadlink_discovery: Discovering... Error authenticating with device : ('192.168.1.6', 80) on broadlink_cli: Traceback (most recent call last): File "./broadlink_cli", line 95, in <module> mac = bytearray.fromhex(values[2]) ValueError: non-hexadecimal number found in fromhex() arg at position 2

Best regards ArchGalileu

Context

Added new device

Proposed change

Type of change

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [X] New device
• [ ] New product id (the device is already supported with a different id)
• [ ] New feature (which adds functionality to an existing device)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [ ] Code quality improvements to existing code or addition of tests
• [ ] Documentation

Additional information

Here is the implementation hub.py - the sub device ids (did) can be found in the app listed as MAC addresses

>>> import broadlink
>>> device = broadlink.hello('192.168.1.99')
>>> device.auth()
True
>>> device.get_state("00000000000000000000a043b0d0783a")
{'pwr1': 0, 'pwr2': 0, 'plugmode': 0, 'hb_timeout': 180, 'lb_online1': 1}
>>> device.set_state("00000000000000000000a043b0d0783a",1)
{'pwr1': 1, 'pwr2': 0, 'plugmode': 0, 'hb_timeout': 180, 'lb_online1': 1}
>>> device.set_state("00000000000000000000a043b0d0783a",0,1)
{'pwr1': 0, 'pwr2': 1, 'plugmode': 0, 'hb_timeout': 180, 'lb_online1': 1}
>>> device.set_state("00000000000000000000a043b0d0783a",None,1)
{'pwr1': 0, 'pwr2': 1, 'plugmode': 0, 'hb_timeout': 180, 'lb_online1': 1}
>>> device.get_subdevices()
[{'did': '00000000000000000000a043b0d06f11', 'pid': '0000000000000000000000001f650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d0783a', 'pid': '0000000000000000000000001f650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d06afa', 'pid': '00000000000000000000000020650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d06963', 'pid': '00000000000000000000000020650000', 'name': 'simpfc_cli', 'offline': 1}, {'did': '00000000000000000000a043b0d0711f', 'pid': '0000000000000000000000001f650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d06d2a', 'pid': '0000000000000000000000001f650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d06ed8', 'pid': '0000000000000000000000001f650000', 'name': 'simpfc_cli', 'offline': 0}, {'did': '00000000000000000000a043b0d063df', 'pid': '00000000000000000000000020650000', 'name': 'simpfc_cli', 'offline': 1}]

• This PR fixes issue: fixes #647
• This PR is related to:
• Link to documentation pull request:

Checklist

• [X] The code change is tested and works locally.
• [ ] The code has been formatted using Black.
• [ ] The code follows the Zen of Python.
• [ ] I am creating the Pull Request against the correct branch.
• [X] Documentation added/updated.

Seems like it's not supported for Broadlink RM4 pro (0x653C)

Originally posted by @lukeclx in https://github.com/mjg59/python-broadlink/issues/472#issuecomment-731774318

Home Assistant 0.118.3

I recently got a new Broadlink RM mini 3 from Amazon US, the device type is 0x5F36. With python-broadlink, I am able to "learn" a few IR code, it is working fine. After a few codes learned, the device starts to complain "The device storage is full" error. This problem cannot be resolved by resetting the device, and I am pretty desperate at this point.

On deciding whether I will need to return the device, I realize that: after using enter_learning() function, the device has white indicator on, which means it indeed reads the IR code, but the error only comes when I try to use check_data() function. Further tests indicate that as long as I commented out the check_error() statement, the check_data function can actually correctly reporting IR code.

So I assume the "learning" functionality is actually writing IR codes into the device's memory, which, from what I see, is very much limited. Since there is no "erase" option given, I assume a lot of users are going to encounter the same problem. And, since most users of python-broadlink only need to read out the IR code instead of really using the learning function, I think it would be great if an option for temporarily disabling the error check for full device storage could be given.

Add support for Broadlink RM4C mini (0x6539) https://github.com/mjg59/python-broadlink/pull/411#issuecomment-728289482 https://github.com/home-assistant/core/issues/42983#issuecomment-729802091

Hi all,

thanks for your work so far on this.

I want to use it with a Broadlink based heating controller ("Hysen HY02B05H", photo here: http://peter.windridge.org.uk/playing-with-cheap-iot-devices/20171120_163450.jpg ).

I can .discover() and .auth() the device. The devtype is: 0x4ead.

(1) Has anyone started working on this device? (2) If not, I need to capture packets from the Android app (which calls a libBLNetwork.so binary). I tried wireshark on Ubuntu but setting promiscuous mode on my laptop doesn't seem to work. I had considered install the Android SDK emulator to run the app on my PC but this seems like a lot of faff. Is there any easier way? (Sorry this question is not directly related to python-broadlink so I don't mind being told to take it elsewhere :))

My goals are:

• read room temperature
• put control in manual mode
• change temperature

I have not tried sending the device codes from check_temperature() etc for fear of bricking it...

Peter

Here my steps that made me think about the question in title of the issue...

1. I had my devices added to the official app.
2. I tried to use broadlink_discovery and it was failing the authentication process.
3. I followed some steps that I found somewhere in old closed issues to remove the devices from the app and reset them.
4. I ran debug.py and both devices autheticated successfully.
5. I re-added the devices to the official app and the library stopped working.

My devices are 0x6026 and 0x62be.

So my question is: Do we need to choose between using this library or the official app exclusively?

These devices require a special header in the payload. The rest is the same.

Related issues:

RM 3 Mini (0x5f36) https://github.com/mjg59/python-broadlink/issues/307 https://github.com/mjg59/python-broadlink/issues/308 https://github.com/home-assistant/core/issues/30215 https://github.com/home-assistant/core/issues/23566 https://github.com/lprhodes/homebridge-broadlink-rm/issues/551

RM4 series https://github.com/mjg59/python-broadlink/issues/301 https://github.com/mjg59/python-broadlink/issues/312

Context

The counter comes in bytes 0x28 and 0x29 and is used to identify the packet. If the device receives a packet with the same counter, the command is not executed twice. This can be reproduced with the following code:

d = blk.hello("192.168.0.12")  # Example device
d.auth()
d.send_data(b64decode("sv8kAAUGEwYGDAsGBgYGBgUMCwsLBgUGBgYGBgYGBgsLCwYGCwYGDAAAAAA=="))

# Same counter, this command won't be executed.
d.count -= 1
d.send_data(b64decode("sv8kAAUGEwYGDAsGBgYGBgUMCwsLBgUGBgYGBgYGBgsLCwYGCwYGDAAAAAA=="))

This is the expected behavior. We are already using this. When the timeout is reached, we send the packet again with the same counter without worrying about commands being executed twice.

The problem

When we re-instantiate the controller or restart the application, the counter is lost. So if we try something like this:

d = blk.hello("192.168.0.12")  # Example device
d.auth()
d.send_data(b64decode("sv8kAAUGEwYGDAsGBgYGBgUMCwsLBgUGBgYGBgYGBgsLCwYGCwYGDAAAAAA=="))

# Same device, but we've lost the counter
d = blk.hello("192.168.0.12")
d.auth()
d.send_data(b64decode("sv8kAAUGEwYGDAsGBgYGBgUMCwsLBgUGBgYGBgYGBgsLCwYGCwYGDAAAAAA=="))

The device gets crazy because the counter is wrong and it stops eliminating duplicate packets. So if we send the same packet twice, even with the same counter, the device executes two different commands.

The code we are sending is an easy way to reproduce the issue. It is a blocking RF code with 255 repetitions. The timeout is reached 3 times, 3 packets are sent and 3 different commands are executed. This wouldn't happen if the counter was persistent, so...

The solution

I propose to update the counter when we authenticate to the device, so this information will always be up to date, even if we restart the application.

Fixes https://github.com/home-assistant/core/issues/41957 Fixes https://github.com/home-assistant/core/issues/37000

Breaking change

Create a new SP3S class for these devices. Applications need to use the correct class to support get_energy().

The problem

Some SP2 devices (PID starting with 0x27) support get_energy(), but the firmware is different from SP3S, so we need to create another method.

From: https://github.com/mjg59/python-broadlink/issues/413#issue-693577696 https://github.com/mjg59/python-broadlink/issues/200#issuecomment-409548956

Proposed changes

• Create a new class for SP3S with the current get_energy() method (only works for SP3S).
• Create a new get_energy() method for the SP2 class.

Need help with tests

These smart plugs don't support energy monitoring. They respond to sp3s.get_energy() with CommandNotSupportedError and StorageError. This is the behavior we had in the past, so we were catching the exceptions eg here.

It would be interesting to see how they respond to this new sp2.get_energy() method before the code is merged. So, if anyone has the smart plugs on the list, please help to test this method.

On your PC:

# Create a venv (not mandatory, but recommended)
python3 -m venv venv
source venv/bin/activate

# Install this branch
pip3 install git+https://github.com/felipediel/pytho[email protected] --force-reinstall

## Run Python 3
python3

Now let's see how the device respond to get_energy():

>>> import broadlink as blk
>>> d = blk.hello("192.168.0.16")  # Example device
>>> d.auth()
>>> d.get_energy()

Thanks in advance!

Hi,

How to detect devices on another network? For example: I am in a network 192.168.1.0/24 and I have a broadlink device on 192.168.1.20 and over this network I have another network with 10.0.0.1/24 where there is a broadlink with address 10.0.0.10.

What should the function broadlink.discover look like to find both broadlink devices when I am on the network 192.168.1.0 I will add that I can see all devices from 192.168.1.0 as well as from 10.0.0.1

Hi!

I just installed a SCB1E to power and monitor a small AC unit with HomeAssistant, after powering on (the SCB1E ) i found that the values returned are incorrect (not divided by 1000).

Wrote a simple script to test the switch directly with python-broadlink and the error is also present:

import broadlink

switch = broadlink.switch.sp4(('...', 80), mac=b'...', devtype=42347, timeout=10, name='SCB1E', model='SCB1E', manufacturer='Broadlink', is_locked=False) switch.auth() print(switch.get_state())

For example the reading when the AC unit is off is:

{'pwr': 1, 'indicator': 0, 'maxworktime': 0, 'current': 35, 'volt': 223900, 'power': 750, 'totalconsum': 0, 'overload': 0, 'childlock': 0}

and when it is on:

{'pwr': 1, 'indicator': 0, 'maxworktime': 0, 'current': 3879, 'volt': 218600, 'power': 833360, 'totalconsum': 30, 'overload': 0, 'childlock': 0}

The device is being identified as a SP4 by the discover method:

broadlink.switch.sp4(('...', 80), mac=b'...', devtype=42347, timeout=10, name='SCB1E', model='SCB1E', manufacturer='Broadlink', is_locked=False)

Trying to use the SP4B class returns the following exception:

broadlink.exceptions.StorageError: [Errno -5] The device storage is full

Context

Proposed change

Type of change

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New device
• [ ] New product id (the device is already supported with a different id)
• [ ] New feature (which adds functionality to an existing device)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [ ] Code quality improvements to existing code or addition of tests
• [ ] Documentation

Additional information

• This PR fixes issue: fixes #
• This PR is related to:
• Link to documentation pull request:

Checklist

• [x] The code change is tested and works locally.
• [x] The code has been formatted using Black.
• [x] The code follows the Zen of Python.
• [x] I am creating the Pull Request against the correct branch.
• [x] Documentation added/updated.

Context

Proposed change

Type of change

• [x] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] New device
• [x] New product id (the device is already supported with a different id)
• [x] New feature (which adds functionality to an existing device)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [x] Code quality improvements to existing code or addition of tests
• [ ] Documentation

Additional information

• This PR fixes issue: fixes #
• This PR is related to:
• Link to documentation pull request:

Checklist

• [x] The code change is tested and works locally.
• [ ] The code has been formatted using Black.
• [ ] The code follows the Zen of Python.
• [ ] I am creating the Pull Request against the correct branch.
• [x] Documentation added/updated.

Thank you for creating this project, its been a great help in getting my smart home fully operational.

This PR adds support for the Luceco Smart Home Downloads.

They need to be configured as a broadlink device in fast flashing AP mode but this change makes them controllable.

I have purchased one of these lights https://www.bg-home.uk/castra-floodlight which I believe uses a Broadlink chip..

I have tried using the cli from this repository and it finds the other Broadlink devices on my networks but seems to fail when finding the new device (see image)

I did log the same issue before I tried using the CLI. This gives a bit more details about the chip type.

https://github.com/mjg59/python-broadlink/issues/725

The mac address of the new device also points to being a Broadlink chip as it starts ec:0b:ae:

Is it possible to get support added? I can try and provide as much technical as I can about the device.

Thanks

Rob