Closed paulschmeida closed 8 months ago
Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
mqtt documentation mqtt source (message by IssueLinks)
I temporarily reverted to core-2024.2.1 via docker compose and it started working immediately.
It seems something went wrong with your program files cache. https://stackoverflow.com/questions/30861493/how-to-fix-python-valueerrorbad-marshal-data. So it might just work if you try the update again.
Same for me. I still could not resolve.
So this issue is with a specific container version, and reverting the container to 2024.2.1 fixes the issue?
Oh sorry I think my problem is little deferent. After update MQTT Discovery does not work anymore for my devices. For eg. MEW-01 and milight hub. Even I set up clean supervised from scratch. Tasmota devices is discovered but under Tasmota integration. Also had unhealthy system after clean installation, but managed it after few docker service restart. There is no log errors except I cant to go to host log page: accesing to http://my_ha:8123/config/logs?provider=host giving me error 500
I temporarily reverted to core-2024.2.1 via docker compose and it started working immediately.
Right, try the new image for 2024.2.3 as soon as it gets published.
There is no log errors except I cant to go to host log page: accesing to http://my_ha:8123/config/logs?provider=host giving me error 500
May be an issue with the supervisor. I'd restart the host, that should solve the issue.
It seems something went wrong with your program files cache. https://stackoverflow.com/questions/30861493/how-to-fix-python-valueerrorbad-marshal-data. So it might just work if you try the update again.
I've tried to pull the latest image again and spin that up, no change. Will wait for the 2024.2.3 as you suggested.
Hi! I have a problem with auto-discovery MQTT integration. I use two dedicated HA servers with their own MQTT servers connected with the MQTT bridge. For some moment I found that a new device connected to one server could not be found on the other server. Although I see the device in MQTT Explorer and may manually configure it in the other HA. The problem exists independent of the server. HA installation: container. HA version: 2024.2.2 MQTT version: 2.0.18 OS: Debian 12
Hi! I have a problem with auto-discovery MQTT integration. I use two dedicated HA servers with their own MQTT servers connected with the MQTT bridge. For some moment I found that a new device connected to one server could not be found on the other server. Although I see the device in MQTT Explorer and may manually configure it in the other HA. The problem exists independent of the server. HA installation: container. HA version: 2024.2.2 MQTT version: 2.0.18 OS: Debian 12
Hi, if you do not have the exact same issue, it it is an issue with HA, please open a new one including logs and explanation. Other wise share us some logs.
@paulschmeida any luck on 2024.2.3 ?
2024.2.3
Updated to 2024.3.0.dev20240225 and it is working again.
2024.2.3
Updated to 2024.3.0.dev20240225 and it is working again.
Okay and 2024.2.3, the official release?
It's not released yet on docker hub, I've updated to the latest available, which was the dev version.
On Mon, 26 Feb 2024, 17:56 Jan Bouwhuis, @.***> wrote:
2024.2.3
Updated to 2024.3.0.dev20240225 and it is working again.
Okay and 2024.2.3, the official release?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/110829#issuecomment-1964770163, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADHLLUKJEGQONA7JCXRHX5LYVTEFBAVCNFSM6AAAAABDNXBEMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUG43TAMJWGM . You are receiving this because you were mentioned.Message ID: @.***>
@paulschmeida just curious to know if the release for 2023.3.0 has arrived yet, and, of course, is it working?
@paulschmeida just curious to know if the release for 2023.3.0 has arrived yet, and, of course, is it working?
@jbouwh I can confirm MQTT broker is working fine now, after updating to Core 2024.3.0 and Supervisor 24.03.0. Thank you.
Thnx for confirming, closing this issue.
I can also confirm 2024.3.0 works. Thank you.
The problem
After updating to the latest docker image yesterday, MQTT connection to Mosquitto broker stopped working and can't be reconfigured. Mosquitto is running on a docker network separate from my LAN so I had it configured from the UI with just
mosquitto
as the hostname and1883
for port, nothing else configured.I have tried to reconfigure it from the UI but I get "unknown error occurred" when clicking next.
What version of Home Assistant Core has the issue?
core-2024.2.2
What was the last working version of Home Assistant Core?
core-2024.2.1
What type of installation are you running?
Home Assistant Container
Integration causing the issue
MQTT
Link to integration documentation on our website
https://www.home-assistant.io/integrations/sensor.mqtt
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response