Open rabner opened 3 weeks ago
Thanks for the report. I'll have a more detailed look at this in the next week or so once time permits. I am running OH 4.2.1 here but my frigate instance is not behind HTTPS and everything works. What does your frigateServer thing configuration look like? Particularly the serverURL parameter?
I have had some reports of strange behaviour with docker instances, but not this specifically.
I've just recreated it: serverURL: http://192.168.xx.xx:8971
. Rest is default.
``` UID: mqtt:frigateServer:frigate:nvr label: frigateSVR Server thingTypeUID: mqtt:frigateServer configuration: ffDASHPackageCommands: -seg_duration 1 -streaming 1 serverClientID: "" ffDASHTranscodeCommands: -acodec copy -vcodec copy enableAPIForwarder: false ffMJPEGTranscodeCommands: -q:v 5 -r 2 -vf scale=640:-2 -update 1 ffmpegLocation: /usr/bin/ffmpeg ffHLSStartProducerOnLoad: false enableStream: false streamWhitelist: DISABLE ffTempDir: "" ffMJPEGStartProducerOnLoad: false ffHLSTranscodeCommands: -acodec copy -vcodec copy ffMinFramesToStart: 10 serverURL: http://192.168.xx.xx:8971 serverKeepAlive: 5 HTTPTimeout: 100 ffDASHStartProducerOnLoad: false ffKeepalivesBeforeExit: 2 bridgeUID: mqtt:broker:frigate channels: - id: fgAPIVersion channelTypeUID: mqtt:fgAPIVersion label: API version description: Version of current Frigate API configuration: {} - id: fgUI channelTypeUID: mqtt:fgUI label: Frigate UI URL description: URL to Frigate user interface configuration: {} - id: fgAPIForwarderURL channelTypeUID: mqtt:fgAPIForwarderURL label: URL of API forwarder description: Local URL of Frigate HTTP API forwarder configuration: {} - id: fgBirdseyeURL channelTypeUID: mqtt:fgBirdseyeURL label: Birdseye stream URL description: URL to re-streamed birdseye view configuration: {} ```
Could it be frigate's builtin nginx? Is there a way to access it's config?
BTW I've checked again with curl and it shows '401 Authorization Required'
Frigate 0.14 is introducing authenticated API
As workaround I've exposed unauthenticated port 5000 in frigate docker.
# docker-compose.yaml
ports:
- 5000:5000
I will look at this in more detail when things get less busy - however the binding's HTTP client that talks to the frigate server really doesn't do anything clever beyond standard HTTP. I suspect there is something going on on the Frigate side.
Frigate ver: 0.14.1 Proxmox unprivileged LXC in Docker
OpenHab ver: 4.2.2 Different host. Frigate binding build locally, but 4.2 doesn't work either.
With TLS disabled in frigate I'm getting 401 Authorization Required from nginx
Openhab log:
With TLS enabled hitting http:
And https response:
After setting MQTT in docker yesterday I'm loosing marbles with this one. How should it be authenticated from openhab thing?