You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I add the card to my dashboard it works fineshowing on browser, but it not show when casting to Google Hub Max using the lovelace view service, it just shows me the yaml text instead and get the following error message on top of the card
"Cannot read properties of null (reading 'other')"
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Seeing the card also on my Google Hub Max
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Garbage Collection Card version: [e.g. 1.15.1]
Browser: [e.g. chrome, safari]
Browser language: [e.g. Swedish]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I'm not familiar with the Nest Hub Max, therefore I don't know what aspect might go wrong.
From the error message it looks like some Javascript related error. It would help a lot in the invetigation if there were some console log possibility that showed the error with the line number (similar to the browser console log).
Describe the bug
If I add the card to my dashboard it works fineshowing on browser, but it not show when casting to Google Hub Max using the lovelace view service, it just shows me the yaml text instead and get the following error message on top of the card
"Cannot read properties of null (reading 'other')"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Seeing the card also on my Google Hub Max
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: