frigate-hass-card: `webrtc-card` provider incorrectly requires `cameraEntity` for engine detection
Checklist:
- I updated to the latest version available
- I cleared the cache of my browser
Release with the issue:
Last working release (if known): 4.x
Browser and Operating System:
Description of problem:
Javascript errors shown in the web inspector (if applicable):
Could not determine suitable engine for camera. Check troubleshooting.
{
"hide": false,
"dependencies": {
"all_cameras": false,
"cameras": []
},
"triggers": {
"motion": false,
"occupancy": true,
"entities": []
},
"engine": "auto",
"frigate": {
"client_id": "frigate"
},
"motioneye": {
"images": {
"directory_pattern": "%Y-%m-%d",
"file_pattern": "%H-%M-%S"
},
"movies": {
"directory_pattern": "%Y-%m-%d",
"file_pattern": "%H-%M-%S"
}
},
"live_provider": "webrtc-card",
"image": {
"refresh_seconds": 1
},
"icon": "mdi:balcony",
"title": "Taras",
"id": "1",
"webrtc_card": {
"entity": "camera.taras_hd"
}
}
Additional information:
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (9 by maintainers)
OK, no worries. I’m going to close this for now for issue hygiene since I suspect this is not actually an issue with the card but something “glitchy” with this specific camera. If you find a way to reproduce this, gather some new clue, or come to the conclusion that it is the card at fault, lets discuss. Thanks!
BTW: Make sure you have the latest webrtc card installed.