TazUk
(Taz Uk)
May 6, 2021, 10:09am
101
No I believe it’s still supported - I just like the idea of centralising my template sensors as I have a lot of them.
However I cannot see friendly_name
detailed under the ‘modern configuration’ section of the integration documents - which will add a multiplier to the time required to shift my configuration around.
To have it decoupled from HA. Like a ZHA docker container instead.
nickrout
(Nick Rout)
May 6, 2021, 10:31am
103
You mean like using zigbee2mqtt?
1 Like
Exactly. Not sure why anybody is confused. I think some are confusing deprecating something with decommissioning something.
Yes but zha is not zigbee2mqtt. I like the way it works with the zwavejsmqtt container which has the option to enable a websocket link to ha instead of mqtt.
petro
(Petro)
Split this topic
May 6, 2021, 3:17pm
106
thermseekr
(Tales Maschio)
May 6, 2021, 11:02am
107
I have not, will do. I have an AVR-X3000.
Ah , i have 4000, it’s the same… Ok, gonna wait then for update… Can you report?
jaalperin
(Jeff Alperin)
May 6, 2021, 11:36am
109
Integration setup times in info panel are very useful. How about sorting by them?
1 Like
thermseekr
(Tales Maschio)
May 6, 2021, 11:38am
110
I’m not sure where to report, and I won’t be able to do it before getting home tonight (it’s 8:37 AM now here). Would you mind doing it?
Thanks a lot.
Tales
TripleJ
(Johnni Jakobsen)
May 6, 2021, 11:49am
112
yes this is really cool. But how to actually achieve this is there a guide on this I have missed.?
On GitHub, create an issue there… i havent updated yet, so I cant
kslb
(KSLBe)
May 6, 2021, 12:26pm
114
Do not update if you have MS SQL database or else you will get in trouble…
arganto:
If I have such cases, as before for fritzbox_callmonitor, iRobot, etc. etc. Where and how to change the settings then afterwards if they change?
Before I opened the config.yaml changed e.g. user, pw, token or whatever other options. After migration to UI, most of the times, there is no chance to change them in UI? What are the thoughts behind this?
Remove and re-add every time I want to change any option
Change this in hidden .storage yaml files
Both are the opposite of UI setup - in my point of view.
Any ideas for me?
E.g. (no changes with this release, done in one of the last releases, but just as an example) callmonitor, before: a lot of options in config.yaml. Now since some time in UI. Changes in documentations here:
committed 10:45AM - 03 Feb 21 UTC
If there are now changes in host, port, id, user, pw, options, … everything could be adjusted in yaml. And How to do it now? There are no options in this integration. And there are no options in most of the ofter integrations I use, which were moved from yamlt to UI. Perhaps the setup is moved now, but how to adjust if needed?
I have the same issue with the Lovelace control cards for Tasmota lights being broken (both for lights configured with MQTT integration and those configured with the Tasmota integration).
The issue was logged in detail as a bug during development:
opened 03:24AM - 05 May 21 UTC
closed 01:46PM - 05 May 21 UTC
integration: tasmota
### The problem
Tasmota Lights no longer change color when using the Color Whee… l. I assume this is because of the new color mode feature. When you select a color the lights just stay white. If you close the light and go back in they are still set to white light.
### What is version of Home Assistant Core has the issue?
2021.5.0b8
### What was the last working version of Home Assistant Core?
2021.4
### What type of installation are you running?
Home Assistant Core
### Integration causing the issue
tasmota
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/tasmota/
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
but then it looks like it was just closed and ignored without being fixed in the PR:
home-assistant:dev
← emontnemery:tasmota_rgbw
opened 11:11AM - 23 Apr 21 UTC
<!--
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.
-->
Tasmota lights no longer supports deprecated white_value, use rgbw_color instead.
## 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 color_mode support to tasmota light.
Flag support for rgbw instead of white_value for lights with red, green, blue and a single white channel
## 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
## 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.
-->
```yaml
# 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.
-->
- [ ] 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`.
- [ ] 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
Further, the reason given for implementing the breaking change:
Tasmota lights no longer supports deprecated white_value, use rgbw_color instead.
does not seem to be mentioned anywhere in the Tasmota changelogs:
# Changelog
All notable changes to this project will be documented in this file.
## [Unreleased] - Development
## [9.4.0.3]
### Added
- Make Telegram command ``TmState`` persistent (#11965)
- Zigbee firmware for Tube's Zigbee coordinator based on EFR32 and ESP32
- Zigbee firmware 6.7.9 for Sonoff ZBBridge
- Defines ``USER_RULE1``, ``USER_RULE2`` and ``USER_RULE3`` to store rules at compile time
- Define ``USER_BACKLOG`` to store commands at compile time to be executed at firmware load or when executing command ``reset``
## [9.4.0.2] 20210430
### Added
- Initial support for optional ``Template`` JSON fieldpair ``"CMND":"<any template related command>|<any template related command>|..."`` (#11788)
- ESP32 pulldown buttons ``Button_d`` and ``Button_id`` and switches ``Switch_d`` (#10814)
- Support for MQTT using Azure IoT Hub by Kevin Saye (#11906)
## [Released]
This file has been truncated. show original
(and I have tested that setting a value for ‘white’ still works fine for Tasmota lights, whether from the Tasmota console or MQTT, including for the latest 9.4.0.3 Tasmota release.)
So there certainly seems to be something odd going on here.
@emontnemery could you please take a look at this, including the bug report issue #50095 (linked above).
3 Likes
TazUk
(Taz Uk)
May 6, 2021, 12:57pm
117
Yeah I’d assumed that after reading the documentation hence the “dumb question” comment in my post, but thanks for confirming - I didn’t want to make a massive set of changes based on my reading comprehension alone.
I should be able to workaround keeping the previous object id (e.g. sensor.wan
in my example) which prevents me redoing some composite sensors, automation references etc. with some judicious titling and tooltipping in Lovelace.
kan84
(Kan84)
May 6, 2021, 1:04pm
119
Were there any breaking changes to zwavejs like zwave_js_value_notification events? I am not getting any events on minimote button press whereas i can see it in the log on zwavejs2mqtt.
denonavr users, i reported the issue :
opened 01:04PM - 06 May 21 UTC
The problem
Hi, since updating to 2021.5.0, i see error below every xx amount of seconds
My system is a AVR-X4000, on cmmunity...
integration: denonavr
2 Likes
Hello ! I’ve got the same error
What do you mean by “rebuild zwavejs2mqtt” ?
Thanks !
bremby
(bremby)
May 6, 2021, 1:16pm
123
HI,
anyone can help me here
21-05-06 13:11:52 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image homeassistant/raspberrypi4-64-homeassistant:landingpage to homeassistant/raspberrypi4-64-homeassistant:2021.5.0
21-05-06 13:11:52 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image homeassistant/raspberrypi4-64-homeassistant with tag 2021.5.0.
21-05-06 13:11:54 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install homeassistant/raspberrypi4-64-homeassistant:2021.5.0 -> 500 Server Error for http+docker://localhost/v1.40/images/homeassistant/raspberrypi4-64-homeassistant:2021.5.0/json: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument").
21-05-06 13:11:54 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant
I started from a fresh imagine, but it doens’t work