Where do we need to put the issue?
Here: Issues Ā· home-assistant/core Ā· GitHub ?
petro
November 4, 2021, 11:22am
164
If itās linked to the Atomic Calendar Revive custom card, thereās no issue to write up in home assistant. The issue needs to be fixed on the custom card.
Well, Iām not sure if itās linked with the Atomic Calendar Revive custom card yet, but I do have this custom card at the momentā¦
petro
November 4, 2021, 11:25am
166
Please remove it and see if the issue goes away.
pjn77
November 4, 2021, 11:29am
167
Only problem for me is Tuya complaining about authentication. Tried deleting the integration and re-adding - only to be reminded of the complex configuration process that iād blanked from my memory, and the fact that I hadnāt recorded the various keys you need to enter. So iāll have to do that again iām guessing, though right now i cant get into my Tuya dev account, and the password reset tool isnt sending an email. So maybe the whole thing is just some wobble at Tuyaās end and ive made work for no reason.
Anyway, thatās my sad story. Thank you for reading.
1 Like
sdahl40
November 4, 2021, 11:31am
168
I have the same card and removing it solves the problem
1 Like
Oh yes! Me too!
Everything is visible again!
I will open an issue now!
petro
November 4, 2021, 11:35am
170
Please open it against the custom card, not the core. Thanks
petro
November 4, 2021, 11:36am
171
Donāt open one, itās already created.
opened 11:25AM - 04 Nov 21 UTC
closed 12:02PM - 04 Nov 21 UTC
type/bug
### Is there an existing issue for this?
- [X] I have searched the existing issā¦ ues
### Current Behavior
Lovelace tabs with the core HA Media Control Card will not load the card if the Atomic Calendar Revive card has already been loaded in another tab. If you load a tab with a Media Control Card first, then ACR will not load.
The debug window in Firefox 94.0 shows this error:
'Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element'
Removing the ACR card from Lovelace resources fixes the issue.
### Expected behaviour
I would expect both cards to load without issues
### Steps To Reproduce
1. Lovelace dashboards using standard Media Control Card and Atomic Calendar Revive Card
2. Using Firefox 94.0 web browser
3. Load dashboards into web browser
4. Firefox debug window shows this error: 'Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element'
5. Removing the ACR card from Lovelace resources allows the Media Control card to function as normal
### Card Version
6.02b
### Home Assistant Version
2021.11.0
### Configuration
```shell
################################################################################
##============================= LOVELACE TEST ============================##
################################################################################
title: Test
icon: mdi:home-assistant
path: test
cards:
- type: media-control
entity: media_player.sitting_room_universal
```
### Relevant log output
```shell
Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element
```
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Link to girhub issue here:
opened 11:25AM - 04 Nov 21 UTC
type/bug
### Is there an existing issue for this?
- [X] I have searched the existing issā¦ ues
### Current Behavior
Lovelace tabs with the core HA Media Control Card will not load the card if the Atomic Calendar Revive card has already been loaded in another tab. If you load a tab with a Media Control Card first, then ACR will not load.
The debug window in Firefox 94.0 shows this error:
'Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element'
Removing the ACR card from Lovelace resources fixes the issue.
### Expected behaviour
I would expect both cards to load without issues
### Steps To Reproduce
1. Lovelace dashboards using standard Media Control Card and Atomic Calendar Revive Card
2. Using Firefox 94.0 web browser
3. Load dashboards into web browser
4. Firefox debug window shows this error: 'Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element'
5. Removing the ACR card from Lovelace resources allows the Media Control card to function as normal
### Card Version
6.02b
### Home Assistant Version
2021.11.0
### Configuration
```shell
################################################################################
##============================= LOVELACE TEST ============================##
################################################################################
title: Test
icon: mdi:home-assistant
path: test
cards:
- type: media-control
entity: media_player.sitting_room_universal
```
### Relevant log output
```shell
Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element
```
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Screenshot of Firefox debug window if ACR loads first:
Screenshot of Firefox debug window if Media Control loads first:
1 Like
reesion
November 4, 2021, 11:37am
173
If you read the thread you can see there are people experiencing the same issue for 2021.11
Ok, Iāve linked and closed my issue with the one from reste_narquois
VDRainer
November 4, 2021, 11:47am
177
There is nothing worse than frontend updates that break custom cards. It usually takes days/weeks for the custom cards to be adjusted.
petro
November 4, 2021, 11:52am
178
When something is needed for a base card, the base card will change. If custom cards use said base card and donāt update with the changes, that causes problems.
milras
November 4, 2021, 12:05pm
179
Gav_in:
in this release Iām getting a warning every 30 seconds in the logs stating āWARNING (MainThread) [pyefergy] Currency provided does not match device settings. This can affect energy cost statisticsā .
Anyone else seeing anything similar? Both my Efergy Account and HA are setup to use Euro as currency so no obvious conflict there and not too sure where to look for this (particularly as the figures surfaced into HA seem correct)
Same issue as you, did you get it working?
Sp4wN
November 4, 2021, 12:07pm
180
Yes, that is why I wrote āBut it is active in that report again.ā
Fredrik13
November 4, 2021, 12:34pm
181
Happy to see Tuya Cameras working. One of my cameras work fine, the other will not load. And typically the camera I would like to have in HA. Both work in the Tuya app, but only one in HA. Strange.
sdahl40
November 4, 2021, 12:35pm
182
Try to take a look at this issue
opened 03:00PM - 28 Oct 21 UTC
needs-more-information
integration: tuya
### The problem
I have removed the old TuyaV2 from the vendor and upgraded toā¦ the included version in the beta release. The new version with camera support pulls in my camera and the settings entries. However there is no video feed in home assistant when i log into the tuya app i can see the video.
### What version of Home Assistant Core has the issue?
2021.11.0b0
### What was the last working version of Home Assistant Core?
2021.10.6
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Tuya
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/tuya
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
[
{
"code": "basic_indicator",
"value": true
},
{
"code": "basic_flip",
"value": false
},
{
"code": "basic_osd",
"value": true
},
{
"code": "motion_sensitivity",
"value": "0"
},
{
"code": "basic_nightvision",
"value": "0"
},
{
"code": "sd_format",
"value": false
},
{
"code": "motion_timer_setting",
"value": ""
},
{
"code": "motion_switch",
"value": false
},
{
"code": "motion_timer_switch",
"value": false
},
{
"code": "decibel_switch",
"value": false
},
{
"code": "decibel_sensitivity",
"value": "0"
},
{
"code": "record_switch",
"value": true
},
{
"code": "record_mode",
"value": "2"
}
]
thanks for heads up.