Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Configuration not persisted when using --config
See original GitHub issueHi all,
I’m using the UniFi Protect Integration for Home Assistant and the Proxy Container – all seems to go well when manually adding cameras via config.json but cameras that are added via the Home Assistant integration seem to fail due to the URL format.
The cameras are added with rtsps URLs like rtsps://IP:7441/token?enableSrtp and the URL needs to be changed to rtsp://IP:7447/token to make things work – the port changes to 7447 and the protocal to rtsp. I already set channel_defaults to "insecure_skip_verify": true to ensure this is not causing any issues, too.
It would be awesome if new cameras would be either added to config.json (so people can manually edit them) or if there would be support for RTSP (or port and protocol remapping).
Thanks in advance and keep up the great work, Tim
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
OK, lets use this to track the persistence issue. I made the dockerfile for this as well as the add-on so maybe its the same issue in both. When running from go, it is able to overwrite the config file correctly.
@azbutz You are right – that seems to be fine. Not sure why it didn’t work for me in the first attempt.