search

blakeblackshear / frigate-hass-addons

Frigate hass.io addons
MIT License
215 stars 120 forks source link

camera IP address can't change #85

Open mrmarria opened 1 year ago

mrmarria commented 1 year ago

Everything working until changed from ether to wireless connection changed ip appropriately in frigate. yml from 192.168.5.64 to 192.168.5.65 and restarted everything log snippet: tcp://192.168.5.64:554?timeout=5000000 failed: No route to host [2022-12-12 12:33:56] ffmpeg.office_cam.detect ERROR : rtsp://admin:PASSWORD@192.168.5.64:554: No route to host [2022-12-12 12:33:59] frigate.video ERROR : office_cam: Unable to read frames from ffmpeg process. [2022-12-12 12:33:59] frigate.video ERROR : office_cam: ffmpeg process is not running. exiting capture thread...

obviously address of original connection "stashed" somewhere other than frigate.yml:

mqtt: host: homeassistant user: mqtt password: PASSWORD

cameras: office_cam: ffmpeg: inputs:

detectors: cpu1: type: cpu cpu2: type: cpu

NickM-27 commented 1 year ago

the config is the only place that the camera route exists so it is not being cached anywhere. It is possible you didn't actually save the file or you are editing the incorrect file.

mrmarria commented 1 year ago

Well that would be my 1st thought, however, I found that the only way to get it to release the old cached info was that restarting HA was not enough. restarting the RBP4 with reboot at the CLI did the trick - the frigate.yml and the configuration.yaml remained unchanged.

Hmmm...

On 12/12/2022 12:59 PM, Nicolas Mowen wrote:

the config is the only place that the camera route exists so it is not being cached anywhere. It is possible you didn't actually save the file or you are editing the incorrect file.

— Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate-hass-addons/issues/85#issuecomment-1347214750, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4QCGMBOI2BZFPHSNK6JZ2TWM573XANCNFSM6AAAAAAS4K66O4. You are receiving this because you authored the thread.Message ID: @.***>

NickM-27 commented 1 year ago

was that restarting HA was not enough

HA has nothing to do with frigate, restarting it won't restart the frigate addon.

mrmarria commented 1 year ago

Let me expand on that, as I should have before.

mqtt is auto starting with and HA start, successfully

1st tried restarting frigate after change of camera IP in both camera and frigate.yml

it kept trying and failing to connect to old IP according to it's log....

2nd tried restarting HA, then frigate - same results

3rd did reboot from CLI login at RBP4

frigate is happy now, with new IP

On 12/12/2022 6:02 PM, Nicolas Mowen wrote:

was that restarting HA was not enough

HA has nothing to do with frigate, restarting it won't restart the frigate addon.

— Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate-hass-addons/issues/85#issuecomment-1347596681, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4QCGMBC4FI7LHQ5SI4N2XLWM7DK5ANCNFSM6AAAAAAS4K66O4. You are receiving this because you authored the thread.Message ID: @.***>