Problem with Core of HA

Configuration
1

Hello everyone ,

So i work on a small project and i went for home assistant as a platform .

didn’t have problem till two days ago .
Everything worked before I wanted to update my platform dockers and core as home assistant . ( I updated every docker first that I use , as ssh and web and mqtt etc . ) till here everything worked fine but after updating the core to the latest version my platform started small restarts and my enteties had unavailable status . as the picture down
Untitled

Then I decide to do partial back up the core of HA .

That also didn’t help any ideas how i can fix this issue ?

  • Also restarting the platform before and after everything didn’t help at all .

  • At the moment i am running 2023.4.2

  • And i was trying to upgrade to 2023.11.1

:slight_smile:

Here is the log file .

File “/usr/src/homeassistant/homeassistant/components/mqtt/models.py”, line 305, in process_write_state_requests
entity.async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 743, in async_write_ha_state
self._async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 843, in _async_write_ha_state
state, attr = self._async_generate_attributes()

Thats it

2

What integrations are those problem devices using?

What’s in HA’s (Core) log file?

1 Like
4

Added the logs :slight_smile:

5

Well, you added a tiny snippet from the logs. Are you sure that’s the only things relating to your entities going unavailable?

And you still didn’t answer the first question

6

I use MQTT version 6.3.1

2023-11-15 11:45:40.828 WARNING (MainThread) [homeassistant.components.sensor] Sensor sensor.node_node00_v2_11111111111111 has device class None, state class None and unit V thus indicating it has a numeric value; however, it has the non-numeric value: nan (<class ‘str’>); Please update your configuration if your entity is manually configured, otherwise create a bug report at Issues · home-assistant/core · GitHub

Is it myb this error that can cause unavailable problem ? And if so how can i fix it ? Do i need to change my code or i need to change smtg on the platform

Or also can be the one of those ?

2023-11-15 11:05:07.151 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration nodered 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-11-15 11:05:07.155 WARNING (SyncWorker_2) [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

And the node red its a addon from HA so yea any ideas ?

7

Integrations don’t have a version number, what does that version number relate to?

That looks like it’s related to your problem. Are you using manually created MQTT entities, or something like Zigbee2MQTT that publishes MQTT Discovery payloads (and if so, exactly what are you using, including the version number)

9

We use manually created mqtt connection with Mosquitto broker, the version I provided you is the version of the Mosquitto.

10

Mosquitto is only at 2.0.18.

And what about the entity? The sensor? How is that created?

11

I have a Arduino , and from there i sub on the MQTT broker , after the sub i publish the results from the sensor and then close the connection .

About MQTT , its says that its 6.3.1

mqtt

12

Well, either that’s not Mosquitto, or somebody’s modified it to report something else.

See for yourself

13

It’s the Mosquitto add-on for HA. The most current version is 6.4.0 (which is mosquitto 2.0.18)

His version is 6.3.1 which is based on Mosquitto 2.0.17

1 Like