Tnx , I Will open a new topic. Last thing;
When I type in the lines you name (cd mnt etc…)
" less homeassistant.log“ doesn’t get a result… doesn’t exist …
maybe you not got to the right folder, forgot to write you should check, … let’s take it in your topic, "Maybe Call your topic “Can’t access HA after core-2023.10.1, thou Supervisor seems to have started”, but errors in core-.log
Anyone else have a problem with user theme? Can’t change it at all. The dropdown fields not even showing seleced value. After refreshing page I can see selected value in all dropdowns apart Language and Dashboard but still can’t change any dropdown value 
Hello,
Pleas Help, what can i do
Bitte um Hilfe
update to 2023.10 and modbus not work for em340
Konfiguration fehlerhaft!
Invalid config for [modbus]: Küche_EM340_W_sys: `count: 2` cannot be combined with `data_type: int32` @ data['modbus'][0]['sensors'][1]. Got {'name': 'Küche_EM340_W_sys', 'unique_id': 'Küche_em340_W_sys', 'unit_of_measurement': 'W', 'state_class': 'measurement', 'device_class': 'power', 'slave': 1, 'address': 40, 'data_type': 'int32', 'input_type': 'input', 'precision': 2, 'count': 2, 'scale': 0.1, 'scan_interval': 5, 'lazy_error_count': 999, 'swap': 'word'}
Das ist meine modbus config.
- name: modbuspi
#unique_id: modbuspi
#delay : 5
#timeout : 5
#message_wait_milliseconds : 1000
type: serial
method: rtu
baudrate: 9600
bytesize: 8
stopbits: 1
parity: N
port: /dev/ttyUSB0
sensors :
# Küche
# SYS
- name: Küche_EM340_test_neg
unique_id: Küche_test_neg
unit_of_measurement: kWh
state_class: total_increasing
device_class: energy
slave: 1
address: 274
data_type: int32
input_type: input
precision: 2
count: 2
scale: 0.1
scan_interval: 15
lazy_error_count : 999
swap : word
What is wrong??
Pleas
Thank you
Okay i found it.
count: 2
that was th problem
Anyone else have a problem with MQTT devices? Since the update to 2023.10 some entities go to not available for a couple of time. Later they come back and other entities are not available.
I use the mosquito add-on.
1 Like
I’m having issues with the Matrix integration. At least one other person is having the same issue. See the below topic.
Was the MQTT issue fixed, is it safe to update while using the MQTT addon?
Can you guys please create a regression for the MQTT Broker add-on?
There is no way to revert to an older version at this time.
MQTT dev’s are NOT even working on this issue, and after speaking with them, it is not a priority to them because they keep saying “you can just use the older version”. Problem is, HA users cannot just revert the version unless they have a backup and only if they know exactly when they upgraded the MQTT broker. Since this MQTT broker version completely breaks MQTT, can’t HA staff just create a new version of the add-on and make it a regression?
No, it’s still broken. Completely broken. My network is still down.
MQTT dev’s aren’t even working on it. I would hope HA dev’s just create a new version of the add-on with regression to the version that worked. This sucks.
Yes, MQTT is completely broken.
MQTT dev’s aren’t even working on it, but they’re aware of it.
I would hope HA dev’s just create a new version of the add-on with regression to the version that worked, because there is no way to revert versions. This sucks.
Is there a GitHub issue you are referencing? No problems with mosquitto broker add-on here.
Same here.
WTH are mqtt devs anyway? Does he mean mosquitto devs, or the mosquitto addon devs, I am confused as hell by @SamJWard 's ref to mqtt devs.
2 Likes
@SamJWard Is this the issue you are experiencing?
Version 2.0.18 released.
Version 2.0.18 of Mosquitto has been released. This is a bugfix release.
Broker: - Fix crash on subscribe under certain unlikely conditions. Closes #2885. Closes #2881.
Clients: - Fix mosquitto_rr not honouring -R. Closes [#2893](mosquitto_rr -R does not ignore stale messages · Issue #2893 · eclipse/mosquitto · GitHub)
1 Like
I am not sure if this is a problem of the mosquitto broker or from the home assistant plugin.
For me the states are received correct in home assistant and the broker. I can see this on payload under mqtt info of the devices. But sometimes the entities will not update and stay “not available”.
Edit: I think this will fix the problem: Fix mqtt sensor or binary_sensor state not saved after expiry by jbouwh · Pull Request #101670 · home-assistant/core · GitHub
HA plugin Mosquitto broker
Current version: 6.3.1
It’s an upstream issue that seems to only affect people with very large numbers of topics:
Actually there is, you can load a backup.
It is not the devs fault that you did not create a backup when upgrading.
In future, create backups before upgrading anything and copy them off your system. There are many ways to do this automatically. See option 5 here: Common tasks - Operating System - Home Assistant
2 Likes
I always laugh at people redacting internal IP addresses.
5 Likes
Hi everyone,
I am using HA core on a Raspberry Pi running on Debian 11. After the upgrade from 2023.8.1 to 2023.10.1 I got this error message
ImportError: libssl.so.3: cannot open shared object file: No such file or directory
It looks like libssl.so.3 is only available in Debian 12 (bookworm) that has recently been released. Likely this version of libssl-dev could be installed on Debian 11 but only with a lot of effort (see HELP: Suddenly ImportError libssl.so.3: cannot open shared object file).
So it looks that the OS has to be upgraded in order to use the latest HA version. In the release notes it is not mentioned that there are dependencies.
I usually do frequent updates of HA, but it is not the first time in the past months that there are dependencies that can’t be fulfilled “out of the box” with an actual OS like Debian 11. I remember having an issue with a required ffmpeg version that wasn’t available from the repo and thus had to be manually compiled.
I think that Debian is one of the common distributions and would appreciate if more effort would be spent to maintain compatibility with actual distros.
Debian 12 was released on June 10th 2023. In the supervised architectural notes it is clearly stated:
Debian Linux Debian 12 aka Bookworm (no derivatives)
and
Only the above-listed version of Debian Linux is supported for running this installation method. When a new major version of Debian is released, the previous major version is dropped, with a deprecation time of 4 months.
So the 4 months has passed, and Debian 11 is not supported anymore.