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

The system is waiting for tasks: velbus_connect_task #116547

Open
Benoit-P opened this issue May 1, 2024 · 2 comments
Open

The system is waiting for tasks: velbus_connect_task #116547

Benoit-P opened this issue May 1, 2024 · 2 comments

Comments

@Benoit-P
Copy link

Benoit-P commented May 1, 2024

The problem

Enregistreur: homeassistant.core
Source: core.py:508
S'est produit pour la première fois: 17:23:50 (1 occurrences)
Dernier enregistrement: 17:23:50

Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: hassio, search, map, energy, bluetooth, onboarding, application_credentials, media_source, frontend, sensor, mobile_app.sensor, usb, netatmo.sensor, wake_word, camera, met, person, update, device_tracker, network, onvif.button, zone, input_datetime, mobile_app.binary_sensor, sonos.switch, netatmo.cover, assist_pipeline, ssdp, tts, switch, lock, trace, file_upload, forecast_solar, media_player, homeassistant.scene, netatmo.camera, logger, netatmo, template.sensor, input_button, sonos.number, timer, sun, webhook, hassio.update, zeroconf, onvif.switch, conversation, upnp.binary_sensor, modbus.sensor, config, device_automation, onvif.sensor, cloud, system_health, switch_as_x.lock, backup, automation, homeassistant_alerts, switch_as_x, history, netatmo.switch, cloud.tts, schedule, sonos.media_player, auth, systemmonitor.sensor, modbus, diagnostics, repairs, logbook, persistent_notification, tag, weather, input_text, sonos.binary_sensor, input_boolean, hacs, systemmonitor.binary_sensor, ffmpeg, netatmo.light, ipp, hacs.sensor, hassio.binary_sensor, recorder, light, analytics, system_log, netatmo.select, select, homeassistant, mobile_app.device_tracker, velbus, onvif, button, my, script, mobile_app.notify, http, blueprint, notify, binary_sensor, hassio.sensor, met.weather, stream, template, number, climate, input_select, onvif.camera, google_translate.tts, websocket_api, upnp, default_config, image_upload, upnp.sensor, forecast_solar.sensor, energy.sensor, stt, sonos.sensor, sonos, radio_browser, sun.sensor, mobile_app, onvif.binary_sensor, dhcp, scene, input_number, counter, hardware, lovelace, api, cover, systemmonitor, netatmo.climate The system is waiting for tasks: {<Task pending name='Task-1578' coro=<velbus_connect_task() running at /usr/src/homeassistant/homeassistant/components/velbus/init.py:49> wait_for=<Task pending name='Task-1852' coro=<Velbus._check_if_modules_are_loaded() running at /usr/local/lib/python3.12/site-packages/velbusaio/controller.py:219> wait_for= cb=[Task.task_wakeup()]> cb=[set.remove(), <7 more>, Task.task_wakeup()]>}

What version of Home Assistant Core has the issue?

core-2024.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Velbus

Link to integration documentation on our website

https://www.home-assistant.io/integrations/velbus/

Diagnostics information

config_entry-velbus-11197709c02f6ae9554639221e0fc5d9 (1).json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

I've tried to connect the Velbus installation via TCP/IP server and had the same issues

Additional information

VMB4LEDPWM-20 issues
VMBLCDWB entities unknown
VMB4AN wrong entities ans datas
VMB7IN real time counters (inputs 1 to 4) are not loaded while the total counters are loaded

@home-assistant
Copy link

home-assistant bot commented May 1, 2024

Hey there @Cereal2nd, @brefra, mind taking a look at this issue as it has been labeled with an integration (velbus) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of velbus can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign velbus Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


velbus documentation
velbus source
(message by IssueLinks)

@Cereal2nd
Copy link
Contributor

Cereal2nd commented May 17, 2024

VMB4LEDPWM-20 issues
what are the issues here? i expect this one to work

VMBLCDWB
This is the first time i see this one in an installation, this module is not supported

VMB4AN
if i read the diagnostics all looks ok, can you give me some specificks?

VMB7IN
This one i'm currently fixing

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

No branches or pull requests

2 participants