Got the same problem, reverted back to 2021.4.6 and for me it's working again.

Good call, manually reverted Android TV to the following pull and it's working again.

https://github.com/home-assistant/core/pull/41893

<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->

Proposed change

This PR adds access to the OpenPlantbook API, and is mostly a preparation for a later PR to the Plant component. The Openplantbook component itself does not do much, except providing a way for Home Assistant to communicate with the OpenPlantbook API and online DB to fetch data. There are two service calls which allows you to search for plant species, and get data for a specific species. https://open.plantbook.io/

This PR is a replacement for PR#42200 where the git history was problematic after a bad rebase.

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. -->

Type of change

<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [X] New integration (thank you!)
• [ ] New feature (which adds functionality to an existing integration)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [ ] Code quality improvements to existing code or addition of tests

Additional information

The component requires the user to get a client id and secret to the OpenPlantbook API. It is configured using a config flow. The Openplantbook API is the exposed to HA as a class where other components (e.g. the Plant component) can fetch data. A PR for the Plant component where it can take advantage of the OpenPlantbook API will be submitted once this component is accepted.

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

• This PR fixes or closes issue: fixes #
• This PR is related to issue: PR#42200
• Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/15445

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

• [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] The code has been formatted using Black (black --fast homeassistant tests)
• [X] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]

If the code communicates with devices, web services, or third-party tools:

• [X] The [manifest file][manifest-docs] has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• [X] New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• [ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->

• [ ] No score or internal
• [ ] 🥈 Silver
• [ ] 🥇 Gold
• [ ] 🏆 Platinum

<!-- This project is very active and we have a high turnover of pull requests.

Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!

By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.

When picking a pull request to review, try to choose one that hasn't yet been reviewed.

Thanks for helping out! -->

To help with the load of incoming pull requests:

• [ ] I have reviewed two other open pull requests in this repository.

<!-- Thank you for contributing <3

Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

This contribution doesn't fit the Home Assistant model. We represent states, not encyclopedia data.

synology_dsm documentation synology_dsm source _{^{(message by IssueLinks)}}

The problem

The Synology DSM integration sensor binary_sensor.ds_security_status reports an unsafe security status due to the attribute Update being in an OutOfDate state.

However, this is not true when checking the DSM interface:

What is version of Home Assistant Core has the issue?

core-2021.5.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Synology DSM

Link to integration documentation on our website

https://www.home-assistant.io/integrations/synology_dsm/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

The problem

The Signal Messenger stop working on core-2021.5.0. The log shown that it sent the message but the receiver never received the message. I tried to re-register the number again or use different sender or receiptients but still not working but when I reverted back to core-2021.4.6 and start working again. I cannot find any logs related to the error. Thanks

What is version of Home Assistant Core has the issue?

core-2021.5.0

What was the last working version of Home Assistant Core?

core-2021.4.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Signal Messenger

Link to integration documentation on our website

https://github.com/haberda/hassio_addons

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Added the extra attributes: wind_gust_speed and thunder_probability that were already implemented in the underlaying library (joysoftware/pypi_smhi).

Also for the existing extra attribute "cloudiness", it is now added if "is not None" instead of just "if self.cloudiness" which would make it False (and therefore not available) if cloudiness = 0, which I think was a bug. Therefore i don't consider it to be a breaking change? I found this because thunder probability is often 0... and I first wrote the attribute code exactly as the old one.

<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. --> Adds wind gust speed and thunder probability as extra attributes. These were already implemented in the underlaying library.

I am sorry, but I am not sure how to run the required tests according to the lists below. I just made the changes in notepad++, uploaded to custom_components folder and it seems to work without any error logs.

Variables/attributes are added, but as I think they are self explaining, and the existing ones are not documented either, I have not proposed any changes to home-assistant.io.

Type of change

<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New integration (thank you!)
• [x] New feature (which adds functionality to an existing integration)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [ ] Code quality improvements to existing code or addition of tests

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

• [x] The code change is tested and works locally.
• [ ] Local tests pass. Your PR cannot be merged unless tests pass
• [x] There is no commented out code in this PR.
• [ ] I have followed the [development checklist][dev-checklist]
• [ ] The code has been formatted using Black (black --fast homeassistant tests)
• [ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• [ ] 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.
• [ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->

• [ ] No score or internal
• [ ] 🥈 Silver
• [ ] 🥇 Gold
• [ ] 🏆 Platinum

<!-- This project is very active and we have a high turnover of pull requests.

Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!

By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.

When picking a pull request to review, try to choose one that hasn't yet been reviewed.

Thanks for helping out! -->

To help with the load of incoming pull requests:

• [ ] I have reviewed two other open pull requests in this repository.

<!-- Thank you for contributing <3

Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

From an architectural perspective, I'm not really sure if this should even be an integration level. In general, the functionality offered by this integration (and the Circadian Lighting / Flux integrations as well) are really useful and used by the community in all kinds of forms.

I might even dare to say, that functionality like this should be more embedded in Home Assistant Core itself.

Besides the comments from @bdraco and @elupus (I agree with both of them); We currently do not allow for integrations, that don't connect to a device or service, to use a config flow. (Which reminds to finish up the writeup of the architectural discussion for that). It is the same reason you see things like: Sun, Moon, Season not being available via the UI at this point.

Unlocked the PR conversation as it blocks the author for joining the conversation.

⚠️ If you are planning to respond on this PR at this point

Please be sure your comment attributes to the review of the code or any architectural contents of the code. In this PR.

We are trying to avoid this becoming a forum or issue tracker.

Thanks! ❤️

<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->

Breaking change

<!-- If your PR contains a breaking change for existing users, it is important to tell them what breaks, how to make it work again and why we did this. This piece of text is published with the release notes, so it helps if you write it towards our users, not us. Note: Remove this section if this PR is NOT a breaking change. -->

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. --> Add targets and selectors to services (A)

Type of change

<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New integration (thank you!)
• [ ] New feature (which adds functionality to an existing integration)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [x] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

<!-- Supplying a configuration snippet, makes it easier for a maintainer to test your PR. Furthermore, for new integrations, it gives an impression of how the configuration would look like. Note: Remove this section if this PR does not have an example entry. -->

# Example configuration.yaml

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

• [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] The code has been formatted using Black (black --fast homeassistant tests)
• [ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• [ ] 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.
• [ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->

• [ ] No score or internal
• [ ] 🥈 Silver
• [ ] 🥇 Gold
• [ ] 🏆 Platinum

<!-- This project is very active and we have a high turnover of pull requests.

Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!

By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.

When picking a pull request to review, try to choose one that hasn't yet been reviewed.

Thanks for helping out! -->

To help with the load of incoming pull requests:

• [ ] I have reviewed two other open pull requests in this repository.

<!-- Thank you for contributing <3

Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

Nothing in the linked architectural issue applies to this here.

Prometheus documentation is very clear about recommended base units,

Agreed. They are very clear on it being "recommended" and not mandatory.

Could you please clarify what you mean by a "massive" breaking change?

Anyone relying on the current namings anywhere in their usage/chain (of whatever they do with it) has to adjust to this change. The odd something having any of those renamed keys, is about 99% of the users of this integration.

Since you are a hass maintaner who is in a position to either merge or reject this change, should I treat your comments as blocking?

🤷 I'm just leaving a comment with my opinion on that we should do this.

Thank you!

regarding the flap and update problems, both are fixed (afaik) in the "beta" version of the integration, see here https://community.home-assistant.io/t/sureflap-connect-pet-door/41488/452?u=benleb

(will port this to home assistant eventually)

<!-- READ THIS FIRST:

• If you need additional help with this template, please refer to https://www.home-assistant.io/help/reporting_issues/
• Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/core/releases
• Do not report issues for integrations if you are using custom components or integrations.
• Provide as many details as possible. Paste logs, configuration samples and code into the backticks. DO NOT DELETE ANY TEXT from this template! Otherwise, your issue may be closed without comment. -->

The problem

<!-- Describe the issue you are experiencing here to communicate to the maintainers. Tell us what you were trying to do and what happened. --> I have a media library containing 9371 albums. When i use the "Browse Media - Albums" function embedded in the "Media Control" Card, the populated list contains only the first 1000 albums, alphabetically sorted. There is no way to browse the rest of the library.

Environment

<!-- Provide details about the versions you are using, which helps us to reproduce and find the issue quicker. Version information is found in the Home Assistant frontend: Configuration -> Info. --> HA Core v 0.117.1

• Home Assistant Core release with the issue:
• Last working Home Assistant Core release (if known):
• Operating environment (OS/Container/Supervised/Core): Container
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

<!-- An example configuration that caused the problem for you. Fill this out even if it seems unimportant to you. Please be sure to remove personal information like passwords, private URLs and other credentials. -->

Traceback/Error logs

<!-- If you come across any trace or error logs, please provide them. -->

Additional information

that looks like two cats?!

regarding the flap and update problems, both are fixed (afaik) in the "beta" version of the integration, see here https://community.home-assistant.io/t/sureflap-connect-pet-door/41488/452?u=benleb

Hey there @home-assistant/core, mind taking a look at this issue as its been labeled with an integration (blueprint) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

Add the ability to disable the event_monitor for older Amcrest cameras

<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->

Breaking change

<!-- If your PR contains a breaking change for existing users, it is important to tell them what breaks, how to make it work again and why we did this. This piece of text is published with the release notes, so it helps if you write it towards our users, not us. Note: Remove this section if this PR is NOT a breaking change. -->

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. -->

Type of change

<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->

• [ ] Dependency upgrade
• [x] Bugfix (non-breaking change which fixes an issue)
• [ ] New integration (thank you!)
• [ ] New feature (which adds functionality to an existing integration)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [ ] Code quality improvements to existing code or addition of tests

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

• This PR fixes or closes issue: fixes #50264
• This PR is related to issue:
• Link to documentation pull request:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

• [x] The code change is tested and works locally.
• [ ] Local tests pass. Your PR cannot be merged unless tests pass
• [x] There is no commented out code in this PR.
• [ ] I have followed the [development checklist][dev-checklist]
• [ ] The code has been formatted using Black (black --fast homeassistant tests)
• [ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• [ ] 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.
• [ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->

• [ ] No score or internal
• [ ] 🥈 Silver
• [ ] 🥇 Gold
• [ ] 🏆 Platinum

<!-- This project is very active and we have a high turnover of pull requests.

Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!

By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.

When picking a pull request to review, try to choose one that hasn't yet been reviewed.

Thanks for helping out! -->

To help with the load of incoming pull requests:

• [ ] I have reviewed two other open pull requests in this repository.

<!-- Thank you for contributing <3

Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

For integrations that connect to devices or services, we no longer accept new YAML configuration or changes.

This integration needs to be refactored first to use a configuration flow and config entries first.

More information about this can be found in Architecture Decision Record:

• ADR-0010: https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision

See our developer documentation on how to get started creating a configuration flow for this integration:

https://developers.home-assistant.io/docs/config_entries_config_flow_handler

As these changes often involve a bit of work and some significant shift in the current code, we will close this PR for now.

We (and our community!) would really appreciate it if you could start on the refactoring of this integration in a new PR.

Thanks already! :+1:

The problem

I have one NUKI lock and with the actual Beta it shows multiple discoveries. I don't know why...

As well it does not show the "ignore" button:

Here is the configured one:

What is version of Home Assistant Core has the issue?

core-2021.5.0b8

What was the last working version of Home Assistant Core?

core-2021.4.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

NUKI

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nuki/

Example YAML snippet

The integration is configured via UI.
I did not find any references in the configuration.yaml or sensors.yaml that might causing the issue

Anything in the logs that might be useful for us?

2021-05-05 10:54:18 ERROR (MainThread) [homeassistant.components.nuki.config_flow] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 135, in async_step_validate
info = await validate_input(self.hass, user_input)
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 37, in validate_input
data[CONF_HOST],
KeyError: 'host'
2021-05-05 10:54:18 ERROR (MainThread) [homeassistant.components.nuki.config_flow] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 135, in async_step_validate
info = await validate_input(self.hass, user_input)
File "/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py", line 37, in validate_input
data[CONF_HOST],
KeyError: 'host'

Tell me, if something else is needed...

Additional information

No response

Fixed with 2021.5.1

This appears to be apart of a problem regarding setting any settings from home assistant until the device is turned on. With the code as it is in this integration you have to turn on a light before you can apply parameters to it.

Doing some research it appears that there is a special flag required "ignore_default" to allow setting parameters from a turned off state because otherwise it will turn on to the default state even if parameters are supplied.

A "manual-only" update mode would be an ideal solution for most tinkerers, as we would be able to configure things to our liking. Using something like the workday integration (https://www.home-assistant.io/integrations/workday/) we would be able to trigger updates on work days only, and only during our relevant travel windows. Assuming a 1.5-hour travel window at each end of the day, and a generic 22 "work" days a month (792 api calls per month at 5-minute intervals during each 90-minute window), the free credit would be sufficient to track a number of members of the family and have extra calls left over for weekend activities (how long to get to the mountain-bike track on Saturday mornings?). This would increase the usability of this integration 100-fold.

Such an implementation would also allow us to differentiate school/work transits from other transits such as after-school sports or 2nd/3rd jobs. Just the act of limiting the integration polling to relevant times of the day will generally make this integration much more usable for those of us attempting to avoid paid components.

The current implementation of a fixed 5-minute interval across all 24-hours of the day does not reflect the usage pattern of such an integration, and severely limits the usability by restricting "free" usage to only one family member each way, or two family members one way.

blueprint documentation blueprint source _{^{(message by IssueLinks)}}

automation documentation automation source _{^{(message by IssueLinks)}}

There is a strange | on one of the logged messages (line 25607):

2021-05-08 15:34:21 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on tele/Wemos/SENSOR: |b'{"Time":"2021-05-08T15:34:21","ENERGY":{"TotalStartTime":"2021-05-02T01:42:29","Total":34.903,"Yesterday":5.372,"Today":1.061,"Period":1,"Power":408,"ApparentPower":582,"ReactivePower":415,"Factor":0.70,"Frequency":50,"Voltage":244,"Current":2.386}}'

What MQTT broker are you using? How is this machine connected to the network? Does it only happen with Tasmota 9.4 firmware? is it solved if you revert back to 9.3?

I have installed the MQTT broker from supervised and from integration (version 5.1.1 on supervised - don't know version of integration) PC hosting Home Assistant is connected with lan gigabit port I have tried to downgrade firmware to 9.3.1 but same issue If I config the sensors by myself in configuration.yaml I can read without problem, so I suppose the problem is not mqtt

  - platform: mqtt
    name: "Ampere"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Current}}"
    unit_of_measurement: 'Ampere'

  - platform: mqtt
    name: "Power"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Power}}"
    unit_of_measurement: 'Watt'

  - platform: mqtt
    name: "ApparentPower"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].ApparentPower}}"
    unit_of_measurement: 'VA'

  - platform: mqtt
    name: "ReactivePower"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].ReactivePower}}"
    unit_of_measurement: 'VAr'

  - platform: mqtt
    name: "Volt"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Voltage}}"
    unit_of_measurement: 'Volt'

  - platform: mqtt
    name: "Factor"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Factor}}"
    unit_of_measurement: ''

  - platform: mqtt
    name: "Frequency"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Frequency}}"
    unit_of_measurement: 'Hz'

  - platform: mqtt
    name: "Energia Oggi"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Today}}"
    unit_of_measurement: 'kWh'

  - platform: mqtt
    name: "Energia Ieri"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Yesterday}}"
    unit_of_measurement: 'kWh'

  - platform: mqtt
    name: "Energia Totale"
    state_topic: "tele/Wemos/SENSOR"
    value_template: "{{ value_json['ENERGY'].Total}}"
    unit_of_measurement: 'kWh'