homebridge-camera-ffmpeg: Config Changes Not Being Saved
Describe The Bug: Starting in 2.0.x seeing that any changes to cameras after initial setup do not get reflected in config. NOTE: Seeing this in the release version of 2.0.x and the beta
To Reproduce:
Using 2.0.x add a camera in with a set criteria (regular -re -i {stream} etc).
- After saving and rebooting Homebridge go back into the Config or Plugins, Settings and adjust a parameter, save, reboot again.
- After doing this I find that the config is showing the previous (original) version, not updating the changes you made. SO for example if you change the IP address in step 1 and rebooting, the IP address is not updated.
- Again this happens whether you are using the Plugins / Settings option to update or directly updating the config.JSON
- What is strange is that if I remove the camera from Plugins / Settings, save, reboot then add from scratch, that update is reflected fine but cannot edit it afterwards.
Expected behavior: Expect this to update the config.JSON and the camera-ffmpeg plugin to read the updated config
Logs: Not seeing anything in the logs that pinpoints this issue currently but happy to provide.
Screenshots So here is an example. When I run v2.0.x here is what the logs show when accessing the camera:
[6/29/2020, 4:48:41 PM] [Camera-ffmpeg] ffmpeg -rtsp_transport http -re -i rtsp://xxxxxxx:xxxxxxx@192.168.xx.xx:554/cam/realmonitor?channel=1&subtype=0 -t 1 -vf scale=1280:720 -f image2 -
HOWEVER, here is what the Plugins / Settings section shows (notice the lack of -rtsp_transport in the config):

Same can be said if you look at the config.JSON therefore its as if after initial setup of v2.0.x that NO changes/updates even in the JSON are being read by the plugin

Here is what is shown in the Homebridge-UI logs which shows the config.json is being saved and again the config file itself reflects those changes BUT camera-ffmpeg is not reading them:
[6/29/2020, 5:04:21 PM] [Config] Changes to config.json saved. [1593471861811] INFO (90189 on mycomputer.localdomain): request completed reqId: 10 res: { “statusCode”: 201
**Homebridge Config:**
**Environment:**
* **Node.js Version**: v12.16.3
* **NPM Version**: 6.14.5
* **Homebridge Version**: 1.1.1
* **Homebridge Camera FFmpeg Version**: v2.0.2=beta13 but appeared on all versions of 2.0.x tested so far
* **Homebridge Config UI X Plugin Version**: v4.23.2
* **Operating System**: macOS
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 3
- Comments: 16 (9 by maintainers)
Commits related to this issue
- Ensure that configureAccessory always uses the latest configuration provided by the config file #579 — committed to Supereg/homebridge-camera-ffmpeg by Supereg 4 years ago
- Ensure that configureAccessory always uses the latest configuration provided by the config file #579 (#593) — committed to Sunoo/homebridge-camera-ffmpeg by Supereg 4 years ago
- v2.1.0 (#574) * Update CHANGELOG.md * Add MQTT to motion Detect (#572) * Update package.json * Update config.schema.json * Update index.ts * Add files via upload * Update index.ts ... — committed to Sunoo/homebridge-camera-ffmpeg by donavanbecker 4 years ago
I can confirm v2.0.2-beta.39 fixes the config issue for me.
I can
I experienced the same issue. I think I found a temporary workaround which is to change the camera name when you make a change. For example, I renamed “Cam Driveway” to “Cam Driveway2” to force changes to be picked up.
I was able to reproduce it too. Was playing with different params for hours to find the best set and in the end realized I didn’t even change anything 😭