-
**Home Assistant release with the issue:**
version: [0.99.2](https://github.com/home-assistant/home-assistant/tree/0.99.2)
**Last working Home Assistant release (if known):**
None
**Operating …
-
I did a fresh install and followed the instructions. When I go to the dashboard It shows me:
`Custom element doesn't exist: grid-layout.` followed by the code in ui-lovelace.yaml
rloo1 updated
5 months ago
-
Browser is asking for microphone permission, but no audio from VTO and unmute button is disabled
```
api:
base_path: "/go2rtc"
streams:
vto:
- rtsp://admin:pass@192.168.124.30/cam/real…
luzik updated
5 months ago
-
## Checklist
- [x] I have updated to the latest available Home Assistant version.
- [x] I have cleared the cache of my browser.
- [x] I have tried a different browser to see if it is related …
-
### The problem
When casting lovelace views, .js from (some?) custom components isn't included. Instead you get an error that the custom element doesn't exist. The same view works correctly from a …
-
I have an automation, it is split into 2x sub-routines (actions), that do the following:
First Action:
```
variables:
target: |
{% set x = trigger.to_state.attributes.source %} {{ state…
-
Custom component version 1.0.0
not possible to use values like 10.0 or 30.0 (they are autoconverted to 10 or 30 in GUI)
-
### PROBLEM DESCRIPTION
I'm seeing the waiting for content message on the Panel and I'm unable to find the configuration issue.
[] I've double checked each step explained in the FAQ:
ht…
-
I'm new on GitHub, and could not find a way to create a pull request, sorry. For my pellet Stove (Nordic Fire, Reeva 7) i have the following customer code: 953712. I ran a packet inspector on my andro…
-
**Checklist:**
- [ x] I updated to the latest version available
- [ x] I cleared the cache of my browser
**Release with the issue:**
13beta4
**Last working release (if known):**
12.1 I think?
**Br…