Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home Assistant 2025.5 : Becker will stop working #57

Open
funjuju opened this issue Dec 26, 2024 · 9 comments
Open

Home Assistant 2025.5 : Becker will stop working #57

funjuju opened this issue Dec 26, 2024 · 9 comments

Comments

@funjuju
Copy link

funjuju commented Dec 26, 2024

Hello,

I just found in log that message :

`Enregistreur: homeassistant.helpers.frame
Source: helpers/frame.py:324
S'est produit pour la première fois: 09:41:31 (1 occurrences)
Dernier enregistrement: 09:41:31

Detected that custom integration 'becker' accesses hass.helpers.dispatcher, which should be updated to import functions used from dispatcher directly at custom_components/becker/rf_device.py, line 103: hass.helpers.dispatcher.dispatcher_send(f"{DOMAIN}.{RECEIVE_MESSAGE}", packet). This will stop working in Home Assistant 2025.5, please report it to the author of the 'becker' custom integration`

@StartDustTC
Copy link

I have the same issue and can confirm, that after updating core to 2024.12.5 the Becker integration stopped working.

@RainerStaude
Copy link
Owner

RainerStaude commented Dec 29, 2024

Please use latest release v0.3.5

@funjuju
Copy link
Author

funjuju commented Dec 29, 2024

I'm already on last release V0.3.5

I have the same issue and can confirm, that after updating core to 2024.12.5 the Becker integration stopped working.

I'm in 2024.12.5 and the integration works fine at the moment.

@RainerStaude
Copy link
Owner

RainerStaude commented Dec 29, 2024

@funjuju, do you still see any warnings in the log with the latest version?
I updated my setup today and I don't see anything in the log.
The issue you describe above is fixed with release v0.3.5

@funjuju
Copy link
Author

funjuju commented Dec 29, 2024

That's weird, i started my integration fews days ago with the last version and never update it ... i can't see the warning anymore in the logs ..

sorry for the incovenience :/

@funjuju funjuju closed this as completed Dec 29, 2024
@StartDustTC
Copy link

StartDustTC commented Dec 30, 2024

This is strange, as I restarted Homeassistant several times yesterday, without any change.
I don't know why, but I finally re-downloaded the latest release (v0.3.5) today (I checked the installed version before, and it said v0.3.5 already), then restarted Homeassistant again, and now it's working. However, all covers were stated in wrong positions. After sending the command to open to each of them, they properly reset their position, and now it seems to work fine again.
Maybe this will help someone with the same issue.

@funjuju
Copy link
Author

funjuju commented Dec 30, 2024

This is strange, as I restarted Homeassistant several times yesterday, without any change. I don't know why, but I finally re-downloaded the latest release (v0.3.5) today (I checked the installed version before, and it said v0.3.5 already), then restarted Homeassistant again, and now it's working. However, all covers were stated in wrong positions. After sending the command to open to each of them, they properly reset their position, and now it seems to work fine again. Maybe this will help someone with the same issue.

There is no states status on becker so HA ne et really know the states.
If someone use proper remote, HA keep the wrong state.

I'm thinking about something to maintain HA on good state using received command to copy the action sent on proper comment in HA to keep it in good state.

@RainerStaude
Copy link
Owner

RainerStaude commented Dec 30, 2024

In order to track the state of your cover, you need to setup at least two things:

  • Add the travel time to configuration
  • Track the cover commands from Becker remotes
cover:
  - platform: becker
    covers:
      living_room:
        friendly_name: "Living room Cover"
        channel: "2:1"
        # Determine the movement time in seconds for each cover from closed to open position. 
        # To improve the precision, add the movement time from open to closed position as well
        travelling_time_up: 30
        travelling_time_down: 26.5
        # The remote ID consists of the unit_id and the channel separated by a colon
        # Multiple ID's separated by comma are possible
        # In order to determine the remote ID, it es necessary to enable debug log messages 
        remote_id: "12345:2"

Please see README for more details

@funjuju funjuju reopened this Dec 31, 2024
@funjuju
Copy link
Author

funjuju commented Dec 31, 2024

Weird thing again : I can see the same message in newer logs :

Enregistreur: homeassistant.helpers.frame
Source: helpers/frame.py:324
S'est produit pour la première fois: 30 décembre 2024 à 20:17:19 (1 occurrences)
Dernier enregistrement: 30 décembre 2024 à 20:17:19

Detected that custom integration 'becker' accesses hass.helpers.dispatcher, which should be updated to import functions used from dispatcher directly at custom_components/becker/rf_device.py, line 103: hass.helpers.dispatcher.dispatcher_send(f"{DOMAIN}.{RECEIVE_MESSAGE}", packet). This will stop working in Home Assistant 2025.5, please report it to the author of the 'becker' custom integration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants