# Integracja MQTT, nie działają Sonoff Basic i POW R2

**URL:** <https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788>\
**Category:** konfiguracja\
**Created:** [20 Marzec 2022 06:57 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788 "2022-03-20T06:57:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Autor:** ![Akronaut](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@Akronaut](https://ai-speaker.discourse.group/u/Akronaut)\
**Data wpisu:** [20 Marzec 2022 06:57 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788/1 "2022-03-20T06:57:57Z")

</div>

Sukcesem dla mnie było zintegrowanie tych urządzeń z AiS. Kilka dni temu zauważyłem, że jedno z nich nie działa. Myślałem, że jest uszkodzone. Zrobiłem restart, bez zmian. Sprawdziłem dostęp po wifi - działa. W panelu są widoczne ale parametry nie są podawane i nie można nimi sterować. Awaria dotyczy 5 szt. Zauważyłem też nie działającą integrację z drukarką Brother. Czy jest na to jakiś sposób?

---

<div class="post-metadata">

**Autor:** ![Stravi](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@Stravi](https://ai-speaker.discourse.group/u/Stravi)\
**Data wpisu:** [20 Marzec 2022 08:35 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788/2 "2022-03-20T08:35:29Z")

</div>

O panie jaki misz-masz…  
Przeczytaj proszę na spokojnie co napisałeś i zredaguj tak żebyśmy zrozumieli co tam masz, na jakiej integracji z jakim softem po stronie urządzenia, jak również po stronie bramki też jest to ważne.  
Jeżeli problem dotyczy 5 urządzeń to rozpisz dane dla każdego z nich.  
Co do Brother to ważna będzie informacja jaką masz wersję na bramce.

---

<div class="post-metadata">

**Autor:** ![Akronaut](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@Akronaut](https://ai-speaker.discourse.group/u/Akronaut)\
**Data wpisu:** [20 Marzec 2022 17:57 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788/3 "2022-03-20T17:57:24Z")

</div>

w urządzeniach mam tasmota 8.4.0 (wszystkie 5 szt.)  
wersji oprogramowania na bramce nie mogę sprawdzić  
po sprawdzeniu pojawia się status spawdzanie  
moja wiedza jest w tym temacie bardzo skromna ☹

---

<div class="post-metadata">

**Autor:** ![Sebastian](https://yyz2.discourse-cdn.com/free1/user_avatar/ai-speaker.discourse.group/sebastian/32/11_2.png) [@Sebastian](https://ai-speaker.discourse.group/u/Sebastian)\
**Data wpisu:** [21 Marzec 2022 12:29 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788/4 "2022-03-21T12:29:19Z")

</div>

Wersje tasmota starsze niż 9.4.0 używają w MQTT Discovery opcji `value_template` - która to w Home Assistant’s jest uznana za deprecated (od wersji 2021.7):

> <https://github.com/home-assistant/core/pull/62682>
>
> \<!--
> You are amazing! Thanks for contributing to our project!
> Please, DO N…OT 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.
> \--\>
> MQTT light with basic schema no longer supports \`value\_template\`, \`state\_value\_template\` should be used instead.
> Support was deprecated in Home Assistant Core 2021.7, and will now fail the configuration.
> 
> \## 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.
> \--\>
> Reject MQTT light discovery using unsupported \`value\_template\`
> 
> The background is that MQTT discovery does not reject discovery of entities with unknown configuration keys, with the intention to be forward compatible (#58390).
> We should however reject configuration keys that have been removed.
> 
> \## 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)
> \- \[x\] 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.
> \--\>
> 
> \- \[\] The code change is tested and works locally.
> \- \[\] Local tests pass. \*\*Your PR cannot be merged unless tests pass\*\*
> \- \[\] 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\`.
> \- \[\] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
> \- \[\] 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\]\[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
> 
> \<!--
> 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

Tak więc jeśli np. twoje urządzenia są przestawione na light (SetOption30 1) to jedynym rozwiązaniem jest upgrade do aktualnej wersji 10.0.0.

---

<div class="post-metadata">

**Autor:** ![Akronaut](https://avatars.discourse-cdn.com/v4/letter/a/2acd7d/32.png) [@Akronaut](https://ai-speaker.discourse.group/u/Akronaut)\
**Data wpisu:** [3 Kwiecień 2022 07:30 UTC](https://ai-speaker.discourse.group/t/integracja-mqtt-nie-dzialaja-sonoff-basic-i-pow-r2/2788/5 "2022-04-03T07:30:47Z")

</div>

Dziękuję za podpowiedź. Czy upgrade można zrobić bezprzewodowo czy konieczne jest rozkręcanie urządzeń i podpinanie kabelków?