Unavailable states for sensors #25

circip · 2023-02-11T14:46:07Z

circip
Feb 11, 2023

Hi, sorry for the probably dumb questions, just new with HA integrations.
I've configured required informations to integrate my Comelit HUB in HA, indeed entities like power , temperature sensors and covers are shown after HA reboot.
However, all these entities report "unavailable" states and other information visible from snapshots below.

Sounds like they are there but not updated (e.g. power is not 2kW but 0,88 kW actually.

Could you kindly help me in understanding what am I wrong with ?

Many thanks in advance.

Answered by circip

Feb 15, 2023

Hi again @gicamm , I think I've found the issue:
problem is due to serial number format. Inside configuration file I wrongly put :

#serial: hsrv-**********

instead of
serial: **********

that was causing malformed topics and therefore the error. I think we can close this discussion.
Perhaps , could you improve wiki with a more clear example in order to avoid this issue again ?

Many thanks for the support, appreciated. :)

View full answer

gicamm · 2023-02-11T18:29:12Z

gicamm
Feb 11, 2023
Maintainer

Hi,
Clicking on the entity, can you enable it?

Cheers
G

0 replies

circip · 2023-02-11T18:48:57Z

circip
Feb 11, 2023
Author

Yes , it's already enabled but also redoing it nothing changes. See below snapshot. Thanks ! P.S: if you prefer we can switch Italian, otherwise fine to keep it this way. Thanks a lot! P.S. hub version is 1.5.2 and connecting it via simple mqtt client seems to work fine too. Il sab 11 feb 2023, 19:29 GC ***@***.***> ha scritto:

…

Hi, Clicking on the entity, can you enable it? [image: image] <https://user-images.githubusercontent.com/1204975/218275006-f5bb98fc-178b-48b5-8ead-192e8edc6204.png> Cheers G — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJP3DQILIYWWF3G6BC4NSQ3WW7LAHANCNFSM6AAAAAAUYXRSSE> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

1 reply

gicamm Feb 11, 2023
Maintainer

Do you have any logs?
Maybe something happened, and the component stopped working.

Cheers
G

circip · 2023-02-11T19:29:30Z

circip
Feb 11, 2023
Author

I've restarted HA , the only relevant error I see is due to error in energy sensor because of unavailable state string that cannot be converted to float. If there is something else I can gather , please guide me and i Will do immediately. Many thanks for your prompt support. All comelit entities are unavailable. Il sab 11 feb 2023, 20:09 GC ***@***.***> ha scritto:

Do you have any logs? Maybe something happened, and the component stopped working. Cheers G — Reply to this email directly, view it on GitHub <#25 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJP3DQOZR2AFI2JSHPAUGJDWW7PXFANCNFSM6AAAAAAUYXRSSE> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

2023-02-11 20:14:06.861 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-02-11 20:14:06.865 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-02-11 20:14:06.870 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration comelit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-02-11 20:14:06.875 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-02-11 20:14:39.224 ERROR (MainThread) [homeassistant.components.automation] Unnamed automation could not be validated and has been disabled: extra keys not allowed @ data['automation']. Got [OrderedDict([('alias', 'MQTT Announce'), ('trigger', [OrderedDict([('event', 'start'), ('platform', 'homeassistant')])]), ('condition', []), ('action', [OrderedDict([('service', 'mqtt.publish'), ('data', OrderedDict([('payload', 'update'), ('topic', 'shellies/command')]))])])])] required key not provided @ data['action']. Got None required key not provided @ data['trigger']. Got None 2023-02-11 20:14:39.318 WARNING (MainThread) [homeassistant.setup] Setup of schedule is taking over 10 seconds. 2023-02-11 20:14:39.322 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds. 2023-02-11 20:14:39.325 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds. 2023-02-11 20:14:39.327 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds. 2023-02-11 20:14:39.329 WARNING (MainThread) [homeassistant.setup] Setup of input_number is taking over 10 seconds. 2023-02-11 20:14:39.332 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds. 2023-02-11 20:14:39.335 WARNING (MainThread) [homeassistant.setup] Setup of counter is taking over 10 seconds. 2023-02-11 20:14:39.339 WARNING (MainThread) [homeassistant.setup] Setup of input_button is taking over 10 seconds. 2023-02-11 20:14:39.342 WARNING (MainThread) [homeassistant.setup] Setup of input_datetime is taking over 10 seconds. 2023-02-11 20:14:39.346 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds. 2023-02-11 20:14:39.350 WARNING (MainThread) [homeassistant.setup] Setup of application_credentials is taking over 10 seconds. 2023-02-11 20:14:39.355 WARNING (MainThread) [homeassistant.setup] Setup of script is taking over 10 seconds. 2023-02-11 20:14:40.082 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.consumo_gorgocity (<class 'homeassistant.components.template.sensor.SensorTemplate'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total', 'total_increasing'; 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+template%22 2023-02-11 20:15:02.263 WARNING (MainThread) [homeassistant.config_entries] Config entry 'shellyplus2pm-0cdc7efa8600' for shelly integration not ready yet: DeviceConnectionError(TimeoutError()); Retrying in background 2023-02-11 20:15:02.394 WARNING (MainThread) [homeassistant.config_entries] Config entry 'shellyplus1-a8032ab9f1a8' for shelly integration not ready yet: DeviceConnectionError(TimeoutError()); Retrying in background 2023-02-11 20:15:22.781 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ states('sensor.comelit_power_cons_gest_carichi')|float * 1 /1000 | round(2) }}") Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1745, in forgiving_float_filter return float(value) ValueError: could not convert string to float: 'unavailable' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 457, in async_render render_result = _render_with_context(self.template, compiled, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1984, in _render_with_context return template.render(**kwargs) File "/usr/local/lib/python3.10/site-packages/jinja2/environment.py", line 1301, in render self.environment.handle_exception() File "/usr/local/lib/python3.10/site-packages/jinja2/environment.py", line 936, in handle_exception raise rewrite_traceback_stack(source=source) File "<template>", line 1, in top-level template code File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1748, in forgiving_float_filter raise_no_default("float", value) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1446, in raise_no_default raise ValueError( ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ states('sensor.comelit_power_cons_gest_carichi')|float * 1 /1000 | round(2) }}' but no default was specified The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 575, in async_render_to_info render_info._result = self.async_render(variables, strict=strict, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 459, in async_render raise TemplateError(err) from err homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ states('sensor.comelit_power_cons_gest_carichi')|float * 1 /1000 | round(2) }}' but no default was specified 2023-02-11 20:15:22.962 ERROR (MainThread) [homeassistant.helpers.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ states('sensor.comelit_power_cons_gest_carichi')|float * 1 /1000 | round(2) }}' but no default was specified') while processing template 'Template("{{ states('sensor.comelit_power_cons_gest_carichi')|float * 1 /1000 | round(2) }}")' for attribute '_attr_native_value' in entity 'sensor.consumo_gorgocity' 2023-02-11 20:20:48.278 ERROR (Thread-8) [pychromecast.socket_client] [Soggiorno(09d593d9-1200-5bce-ab0c-6fdf2629a482.local.):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-09d593d912005bceab0c6fdf2629a482._googlecast._tcp.local.'), retrying in 5.0s 2023-02-11 20:20:48.434 ERROR (Thread-9) [pychromecast.socket_client] [Camera matrimoniale(defaf1dd-61fc-1492-1cc6-63a931218bce.local.):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-Mini-defaf1dd61fc14921cc663a931218bce._googlecast._tcp.local.'), retrying in 5.0s

0 replies

circip · 2023-02-13T10:36:14Z

circip
Feb 13, 2023
Author

Good Morning @gicamm , this morning I decided to remove and add again the integration , via HACS with new 0.9.1 release. Below the steps:

remove all entities from HA
remove previously downloaded comelit integration
comment inside configuration.yaml all references to comelit integration
restart HA and verify everything was removed

After that:

add via HACS the integration
restart HA to have it integrated
uncommented inside configuration.yaml the part for comelit HUB (HUB version is 1.5.2) integration while keeping the VEDO one commented for the time being (see snapshot below) and restarted HA:

However, after restarting HA , entities are not recreated anymore. Any suggestion?

Below the log after restart:

_2023-02-13 11:19:05.134 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-02-13 11:19:05.139 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-02-13 11:19:05.148 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration comelit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-02-13 11:19:05.153 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-02-13 11:19:31.026 ERROR (MainThread) [homeassistant.components.automation] Unnamed automation could not be validated and has been disabled: extra keys not allowed @ data['automation']. Got [OrderedDict([('alias', 'MQTT Announce'), ('trigger', [OrderedDict([('event', 'start'), ('platform', 'homeassistant')])]), ('condition', []), ('action', [OrderedDict([('service', 'mqtt.publish'), ('data', OrderedDict([('payload', 'update'), ('topic', 'shellies/command')]))])])])]
required key not provided @ data['action']. Got None
required key not provided @ data['trigger']. Got None
2023-02-13 11:20:46.266 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform rpi_power is taking over 10 seconds.
2023-02-13 11:20:46.295 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform localtuya is taking over 10 seconds.
2023-02-13 11:21:04.464 ERROR (MainThread) [custom_components.localtuya.common] [052...7bf] Connect to 192.168.1.147 failed
Traceback (most recent call last):
File "/config/custom_components/localtuya/common.py", line 187, in _make_connection
self._interface = await pytuya.connect(
File "/config/custom_components/localtuya/pytuya/init.py", line 1163, in connect
_, protocol = await loop.create_connection(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1064, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 535, in sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.147', 6668)
2023-02-13 11:21:11.089 WARNING (MainThread) [homeassistant.config_entries] Config entry 'shellyplus1-a8032ab9f1a8' for shelly integration not ready yet: DeviceConnectionError(TimeoutError()); Retrying in background
2023-02-13 11:21:11.217 WARNING (MainThread) [homeassistant.config_entries] Config entry 'shellyplus2pm-0cdc7efa8600' for shelly integration not ready yet: DeviceConnectionError(TimeoutError()); Retrying in background

Many thanks.

0 replies

gicamm · 2023-02-13T11:03:29Z

gicamm
Feb 13, 2023
Maintainer

Hi,
if your instance loads the component, you should see something like below
Starting Comelit Hub integration ......
If not, it means the hub integration never started, and maybe something is wrong with the connection. But in this case, you should see an ERROR log.
Please restart home-assistant, grep the 'comelit' keyword to a new file, and attach here.
What is the HUB firmware?

Cheers
G

0 replies

circip · 2023-02-13T11:52:32Z

circip
Feb 13, 2023
Author

Hi @gicamm , here is the log, after enabling logger to debug level for comelit integration (hidden serial number with * marks):

_pi@raspberrypi:/usr/share/hassio/homeassistant $ grep -i comelit home-assistant.log
2023-02-13 12:47:59.224 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration comelit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-02-13 12:48:25.797 INFO (SyncWorker_1) [custom_components.comelit.hub] Starting Comelit Hub integration 192.168.1.100:1883 hsrv-*********
2023-02-13 12:48:25.830 DEBUG (Thread#1) [custom_components.comelit.hub] Comelit Hub status snapshot started
2023-02-13 12:48:25.876 INFO (Thread-3 (thread_main)) [custom_components.comelit.hub] connected to comelit hub
2023-02-13 12:48:25.891 INFO (SyncWorker_1) [custom_components.comelit] Comelit Hub integration started
2023-02-13 12:48:26.960 INFO (SyncWorker_6) [custom_components.comelit.sensor] Comelit Sensor Integration started
2023-02-13 12:48:26.961 INFO (SyncWorker_6) [custom_components.comelit.scene] Comelit Scenario Integration started
2023-02-13 12:48:37.497 INFO (SyncWorker_0) [custom_components.comelit.cover] Comelit Cover Integration started
2023-02-13 12:48:37.512 INFO (SyncWorker_1) [custom_components.comelit.climate] Comelit Climate Integration started
2023-02-13 12:48:38.233 INFO (SyncWorker_0) [custom_components.comelit.light] Comelit Light Integration started
2023-02-13 12:48:38.260 INFO (SyncWorker_1) [custom_components.comelit.switch] Comelit Switch Integration started

however, entities not shown. Shall I configure something else?
Hub firmware is 1.5.2.
Thanks

Update 14:13 : Below a new edition of comelit related logs with whole HA in debug mode.

debug_comelit.log

0 replies

gicamm · 2023-02-13T14:32:25Z

gicamm
Feb 13, 2023
Maintainer

Looking at the logs,
the poller seems to start correctly

2023-02-13 14:11:50.038 INFO (SyncWorker_3) [custom_components.comelit.hub] Starting Comelit Hub integration 192.168.1.100:1883 hsrv-*********
2023-02-13 14:11:50.062 DEBUG (Thread#1) [custom_components.comelit.hub] Comelit Hub status snapshot started
2023-02-13 14:11:50.102 INFO (Thread-3 (_thread_main)) [custom_components.comelit.hub] connected to comelit hub

However, I can't see any snapshot coming from the MQTT client. The issue could be there. Something wrong could happen processing responses or sending requests. These logs are not sufficient. I need a further debugging.

1 reply

circip Feb 13, 2023
Author

Ok, is there something I can check or do to help , here ? Any dependency or software check to do at mqtt side or any subscribe I can test?
Could mqtt broker integration installed on the HA interfere someway with the client sw you are using?

Finally , during the weekend I tried to connect an mqtt client from my mobile to comelit hub and it worked. So I guess it's something at HA side.
Thanks

P.S. if you have time for a debug session together , we can arrange it.

circip · 2023-02-13T18:20:29Z

circip
Feb 13, 2023
Author

One more info, if it may help , I subscribed mqtt server on hub for # , and when comelit integration starts I only see this message:

Cheers

2 replies

gicamm Feb 14, 2023
Maintainer

That's what I suspected.

Please stop your instance
listen to these two topics

mosquitto_sub -v -h $IP -p $PORT -u "hsrv-user" -P "sf1nE9bjPc" -t 'HSrv/$SERIAL/rx/homeassistant'
mosquitto_sub -v -h $IP -p $PORT -u "hsrv-user" -P "sf1nE9bjPc" -t 'HSrv/$SERIAL/tx/homeassistant'

then start your homeassistant

Please hide your sensitive data and attach the logs here.

circip Feb 15, 2023
Author

Good Morning @gicamm , below the output you've requested:

For the rx sub:

pi@raspberrypi:~ $ mosquitto_sub -v -h 192.168.1.100 -p 1883 -u "hsrv-user" -P "sf1nE9bjPc" -t 'HSrv/hsrv-**********/rx/homeassistant'

HSrv/hsrv-************/rx/homeassistant {"req_type": 13, "req_sub_type": -1, "agent_type": 0, "seq_id": 1, "agent_id": 10, "sessiontoken": ""}

For the tx sub , no output:
pi@raspberrypi:~ $ mosquitto_sub -v -h 192.168.1.100 -p 1883 -u "hsrv-user" -P "sf1nE9bjPc" -t 'HSrv/hsrv-**********/tx/homeassistant'

Please let me know what else may I investigate,
Thanks

circip · 2023-02-15T16:32:16Z

circip
Feb 15, 2023
Author

Hi again @gicamm , I think I've found the issue:
problem is due to serial number format. Inside configuration file I wrongly put :

#serial: hsrv-**********

instead of
serial: **********

that was causing malformed topics and therefore the error. I think we can close this discussion.
Perhaps , could you improve wiki with a more clear example in order to avoid this issue again ?

Many thanks for the support, appreciated. :)

0 replies

gicamm · 2023-02-15T16:45:09Z

gicamm
Feb 15, 2023
Maintainer

Please drop me any feedback.

Cheers
G

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unavailable states for sensors #25

{{title}}

Replies: 10 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Unavailable states for sensors #25

circip Feb 11, 2023

Replies: 10 comments · 4 replies

gicamm Feb 11, 2023 Maintainer

circip Feb 11, 2023 Author

gicamm Feb 11, 2023 Maintainer

circip Feb 11, 2023 Author

circip Feb 13, 2023 Author

gicamm Feb 13, 2023 Maintainer

circip Feb 13, 2023 Author

gicamm Feb 13, 2023 Maintainer

circip Feb 13, 2023 Author

circip Feb 13, 2023 Author

gicamm Feb 14, 2023 Maintainer

circip Feb 15, 2023 Author

circip Feb 15, 2023 Author

gicamm Feb 15, 2023 Maintainer

circip
Feb 11, 2023

Replies: 10 comments 4 replies

gicamm
Feb 11, 2023
Maintainer

circip
Feb 11, 2023
Author

gicamm Feb 11, 2023
Maintainer

circip
Feb 11, 2023
Author

circip
Feb 13, 2023
Author

gicamm
Feb 13, 2023
Maintainer

circip
Feb 13, 2023
Author

gicamm
Feb 13, 2023
Maintainer

circip Feb 13, 2023
Author

circip
Feb 13, 2023
Author

gicamm Feb 14, 2023
Maintainer

circip Feb 15, 2023
Author

circip
Feb 15, 2023
Author

gicamm
Feb 15, 2023
Maintainer