**Describe the bug** I have `print_format = "Xml"` in my toml file but nothing is printing out to stdout. I tried Human as well and it also fails. This used to work so something seems to have changed. **To Reproduce** config file... ``` [[cameras]] name = "camera" username = "admin" password = "XXXX" uid = "952XXXXX" address = "192.168.12.XX" discovery = "local" stream = "mainStream" push_notifications = false print_format = "Xml" ``` Command... `~/github/neolink/target/release/neolink image --use-stream --config=/home/david/neolink.toml --file-path=/home/david/image.jpeg camera` **Expected behavior** It should report status including battery level and temperature. **Output** ``` david@neolink:~$ ~/github/neolink/target/release/neolink image --use-stream --config=/home/david/neolink.toml --file-path=/home/david/image.jpeg driveway [2024-10-16T21:29:35Z INFO neolink] Neolink 0.6.3-rc.3 (unknown commit) release [2024-10-16T21:29:35Z INFO neolink::utils] driveway: Connecting to camera at Address: 192.168.12.XX, UID: 952XXXXX [2024-10-16T21:29:35Z INFO neolink_core::bc_protocol] driveway: Trying TCP discovery [2024-10-16T21:29:36Z INFO neolink_core::bc_protocol] driveway: Trying local discovery [2024-10-16T21:29:38Z INFO neolink_core::bc_protocol] driveway: Local discovery success 952XXXXX at 192.168.12.XX:33072 [2024-10-16T21:29:38Z INFO neolink::utils] driveway: Logging in [2024-10-16T21:29:38Z INFO neolink::utils] driveway: Connected and logged in [2024-10-16T21:29:40Z INFO neolink::common::camthread] driveway: Camera time is already set: 2024-10-16 17:29:43.0 +05:00:00 [2024-10-16T21:29:42Z INFO neolink::common::neocam] driveway: Model Reolink Argus 3 Pro [2024-10-16T21:29:42Z INFO neolink::common::neocam] driveway: Firmware Version v3.0.0.4019_24090555 [2024-10-16T21:29:44Z INFO neolink::image::gst] appsrc name=thesource ! h265parse ! decodebin ! jpegenc snapshot=TRUE ! filesink location=/home/David/image.jpeg ```
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by dkerr64 and has received 10 comments.