-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
No valid unit for entity #115659
Comments
Hey there @Cereal2nd, @brefra, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) velbus documentation |
FYI: turned back to the snapshot of my virtual machine (before update) |
from what version did you upgrade? as i thought i fixed this a couple of months ago |
When I remove the velbus entity and add it again it works. When I reboot HA it stops working. I can see in the diagnostics file that something as changed. So somewhere it removes the "unit" line |
@Cereal2nd Is there something i'm doing wrong? I can't figure out why the unit config keeps disappearing... |
i need to investigate ... but that will be half may at the earliest |
Oke, thanks in advance!
…On Fri, 3 May 2024 at 08:15, Maikel Punie ***@***.***> wrote:
i need to investigate ...
but that will be half may at the earliest
—
Reply to this email directly, view it on GitHub
<#115659 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIFV7UGZPTQT6PACF73SJ7LZAMTPXAVCNFSM6AAAAABGH6QRZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSGM3TCOJYGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Opening the topic again. Just updated Home Assistant again with the following values: Again same notification in error log: |
Also still have issues with VMB7IN. Still not showing power output.. Logfile: Detected blocking call to open inside the event loop by integration 'velbus' at homeassistant/components/velbus/init.py, line 74: controller = Velbus( (offender: /usr/local/lib/python3.12/site-packages/velbusaio/handler.py, line 40: with open(), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+velbus%22 Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 447, in async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 449, in create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/velbus/init.py", line 74, in async_setup_entry controller = Velbus( I think it is still missing the option enabled : true I checked on version 2024.4.1 and there you can see the following in the debug file: Core |
@Cereal2nd Can you please take a look at this again? |
not the coming weeks. the earliest will be by the end of the month |
@Cereal2nd Okido. Also I found out that if I delete the hub and then add it again it all works again until I restart HomeAssistant.. After adding it again: |
Reverted my snapshot back to waiting for a solution: |
this was added to make the counters work again ... so i doubt this will fix everything |
You are right. For some reason it just worked one time after a reload of velbus... |
i think we will need to do something similar as this for the enabled param. |
Oke I did some testing with the changed code. First I removed velbus from HA and then added it again. Then everything works(but that was also before the change) Then I restarted HA and then it stops working again Then I tried to reload the velbus integration and then strange things happen I have 2 VMB7IN modules(both with counters added to them) and after the reload 1 of the 2 works. When I reload again sometimes the other works again but the first ons stops working... And sometimes both off them stop working... This is the error in the system log: Detected blocking call to open inside the event loop by integration 'velbus' at homeassistant/components/velbus/init.py, line 74: controller = Velbus( (offender: /usr/local/lib/python3.12/site-packages/velbusaio/handler.py, line 40: with open(), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+velbus%22 Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 447, in async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 449, in create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/velbus/init.py", line 74, in async_setup_entry controller = Velbus( |
The problem
Receiving the following errors: 2024-04-15 21:21:49.908 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.so1_afname (<class 'homeassistant.components.velbus.sensor.VelbusSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+velbus%22
After recent update.
What version of Home Assistant Core has the issue?
2024.4.3
What was the last working version of Home Assistant Core?
core_2024.3.0
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/#:~:text=Example%20automation-,The%20Velbus%20integration,a%20device%20or%20a%20service.
Diagnostics information
See error above
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: