Tank
Février 7, 2025, 5:56
1
Bonjour à toutes et à tous,
Comme chaque début de mois, une nouvelle version de Home Assistant Core est publiée.
Celle-ci a été traduite par nos équipes, pour votre plaisir. Bonne lecture !!!
Cette mise à jour va faire plaisir aux détracteurs des sauvegardes automatique mise en place le mois précédent. Vous pourrez noter que Nabu Casa, et la communauté de développeur a écouté de très nombreux cris de la communauté Home-Assistant, en apportant de très nombreuses modifications. De grande félicitation à eux.
Comme toujours, nous préconisons d’attendre la version xx.1 voir xx.2 avant de mettre à jour votre installation en production.
15 « J'aime »
Merci beaucoup pour ce travail très utile à la communauté.
La dernière mise a jours règle les problèmes pour ceux qui utilise en autre une awtrix en MQTT :
ouvert 09:45AM - 06 Feb 25 UTC
fermé 08:11PM - 06 Feb 25 UTC
integration: mqtt
### The problem
**EDIT:** As @JosephRDawson found out, this seems more a proble… m of empty payloads, see below. Changing title.
I run an AWTRIX 0.98 display (Ulanzi clock) which is supposed to feed back a screenshot of the display every 10 seconds into my dashboard (content changes every 10s). This suddenly stopped working after the HA Core 2025.2.0 upgrade.
My AWTRIX has a MQTT base topic of `awtrix1`. You are supposed to send an empty payload to `awtrix1/sendscreen`, upon which the clock sends back the current screen content as a JSON payload in the `awtrix1/screen` topic.
I use this method to feed an MQTT sensor for the HACS [AWTRIX Light Display Card](https://github.com/RDG88/lovelace-awtrix-light-display-card), defined in `configuration.yaml`:
```yaml
mqtt:
sensor:
- name: "Awtrix1 Screenshot"
unique_id: "awtrix1_screenshot"
state_topic: "awtrix1/screen"
value_template: "1"
json_attributes_topic: "awtrix1/screen"
json_attributes_template: "{\"screen\": \"{{ value_json }}\"}"
```
Now here is the interesting part: When I use the MQTT Configuration tools to_manually_ publish an empty payload to `awtrix1/sendscreen` and watch the `awtrix1/screen` topic, I get back the screen content immediately, and the dashboard updates just fine.
**But when I run my automation (triggers every 10s), _nothing is updated_—which worked fine before the HA Core 2025.2.0 update:**
```yaml
alias: Awtrix screenshot
description: Gets a screenshot from Awtrix every 10s.
triggers:
- seconds: /10
trigger: time_pattern
conditions: []
actions:
- data:
topic: awtrix1/sendscreen
action: mqtt.publish
mode: single
```
**What has changed? Do we now have some kind of rate limiting or just a bug?**
Since nothing else has changed apart from me doing the HA Core 2025.2.0 upgrade, I think we can exclude:
- my HA setup
- the custom lovelace card
- the AWTRIX 0.98 (Ulanzi) display
- my automation code
as the reasons for the sudden malfunction between the latest HA Core 2025.1 and HA Core 2025.2.0.
My HA runs on Proxmox, and I use the official Mosquitto MQTT Broker Add-On v6.5.0.
Home Assistant "About" shows the following:
- Core 2025.2.0
- Supervisor 2025.02.0
- Operating System 14.2
- Frontend 20250205.0
### What version of Home Assistant Core has the issue?
2025.2.0
### What was the last working version of Home Assistant Core?
2025.1.?
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
_No response_
home-assistant:dev ← home-assistant:mqtt-publish-service-payload
ouvert 07:16PM - 06 Feb 25 UTC
## Proposed change
Allow to omit the `payload` attribute for the MQTT publish… action to allow an empty payload to be set. In de UI an empty payload is hard to set when the attribute is marked as required. Users would need to switcth to YAML mode to allow to set an empty string. Instead `payload` is made optional (again).
In earlier releases users could either supply `payload` or `payload_template`. The latter attribute was removed with HA Core 2025.2.0 and `payload` was made required.
This PR will revert the change where `payload` was made required. As this was never considered to be a breaking change in the first place, changing back to optional could be considered a bug fix.
A docs PR will be linked.
## Type of change
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #137532
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/37338
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
Bonjour à tous.
Attention de ne pas vous faire avoir comme moi, après la mise à jour, impossible de recharger home assistant dans le navigateur ni sur l’application, je pensais que la mise à jour avait planter mais au bout d’un certain moment ou je n’arrivais pas a recharger home assistant, je me suis connecté en local sur l’IP de home assistant et la cela fonctionnait, le problème venait de l’accès distant par l’url fournit par Nabu Casa. J’ai juste eu a me reconnecter et tout était de nouveau fonctionnel.
