All sensors/cameras become unavailable after restart
See original GitHub issueDescribe the bug When restarting either the addon or the integration or HassOS after an upgrade all my detection sensors and cameras became unavailable. I know that happened before but they eventually came back after I restarted the addon and the integration. But this time they remain unavailable no matter what. It worked fine with the same config until I restarted after the latest HassOS update.
Version of frigate Frigate NVR Beta version 1.2
Config file Include your full config file wrapped in triple back ticks.
coral:
type: edgetpu
device: 'usb:0'
mqtt:
host: *mqtt server hostname*
ffmpeg: {}
cameras:
garden:
ffmpeg:
inputs:
- path: *path to my camera*
roles:
- detect
- rtmp
width: 1920
height: 1080
objects:
track:
- person
- dog
- cat
- bird
- car
- motorcycle
- bus
- truck
- bicycle
Issue Analytics
- State:
- Created 3 years ago
- Comments:12
Top Results From Across the Web
Zigbee sensors sometimes show as unavailable after server ...
Give it a few minutes, and they should become available. This sometimes happens to me on restarts because the sensors only report so...
Read more >HA sensors gone unavailable #2134 - blakeblackshear/frigate
Restart of Home Assistant following 0.94 update over last day or so, and now all the camera sensors and binary sensors are unavailable....
Read more >Kinect sensors occasionally not detected after computer restart
I'm experiencing an issue where connected devices are not discovered after computer restart. When it happens there's an error message in the ...
Read more >Unavailable / Unknown Entity Monitoring - Template Sensor
This template sensor will iterate the states object and return a count and list of entities that have a state of unknown, unavailable....
Read more >Sensors Off | Android Open Source Project
If an app is using the camera when Sensors off is enabled, an error is sent to the onError callback method and CameraDevice...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You’ve pointed me to the right direction. I had to specifically enter the username and password for the MQTT connection. Although I did use the default ones from the Frigate config example which I did locally add to the MQTT config as well to allow connecting, it would not use it unless when I put them explicitly into the config. It now seems to work (also with the mosquitto mqtt server), thanks!
https://github.com/blakeblackshear/frigate/blob/444fa45a2c2bd45aa8efa971a72b0a4203d323d5/frigate/app.py#L122 is where it would be addressed if it was an mqtt issue:
From your log above I frigate.mqtt INFO : MQTT connected
So i would then assume that according to that it should be working.
But your mqtt log does report: 1610378957: Socket error on client frigate, disconnecting.
I migrated over to the MQTT Server & Webclient that has the HiveMq logo, and havent had issues, not sure why i struggle with the native one, but i have had similar errors with DC’s.
This is the MQTT i use at the moment: https://github.com/hassio-addons/addon-mqtt/blob/master/README.md
Just don’t run both at the same time :p
Dont Forget to thumbs up the solution, and close it if it resolved for you.