I have updated to latest build and now it starts to connect (consistently) as expected. The strange thing though is that in console it is still reporting Build #929, so I am uncertain if the upgrade is done completely. Also Zwave seems to work, but haven't testet in details.....

Which seems to trigger sometimes when a command is sent to the Thing to change its state to Movies or Nodect (the only thing my rules do when someone comes up the driveway). The logs get full of this every two seconds and stopping/starting the bundle in karaf is the only way to fix it.

These refreshThing errors seem to happen any time the camera changes state on its own to. If the monitor is set to mocord, the errors start if a recording is triggered from zoneminder due to motion. Then the log is filled with these errors every 2 seconds

Thanks for your logs, seems like I have to do some debugging. Unfortunately I have been quite busy with other things lately, first of all a broken disk in my fileserver - ended with a large cleanup project…

Unfortunately, my ZM server goes from Running state to Stopped state if i do an Operating mode change from Modect to Monitor. I have to then login into ZM webserver, and change the ZM state from Stopped to ‘Start’.

No data lost. Since long ago I wanted to add Write cache (SSD disks) to my storage. been pushing that in front of me, because I know I had to rearrange a lot in the server. So it ended up with a slightly larger project than just buy and install a new disk

For the moment I am working on a Jython script to presence detection, when that comes to some point where I can put that aside, I believe it is time to look at ZoneMinder Binding. Hopefully in a couple of days.

@mr_eskildsen Rather than restarting zmserver each time the camera operating mode changes, I wanted to only restart it if it has gone offline. However, I noticed that even when the bridge goes down like this

Went through the troubleshooting steps and noticed a flaw on the “I have tried all of the above, it still doesn’t work” part. When I issued the command given “curl -d “=XXXX&=YYYY&action=login&view=console” -c cookies.txt http:///zm/index.php” it will proof that connectivity is working, but actual login failed.
When using “curl -d “username=XXXX&password=YYYY&action=login&view=console” -c cookies.txt http:///zm/index.php” it does login successful.

Would be good to have that changed on the Github and document page.
(there’s a typo anabled instead of enabled in the top, next to some table <tags> on the document page)

Running the 2.1.0 release build with standard bindings, but guess I need to obtain and load a later zoneminder-binding, correct?

There has been reported some issues, so whenever get the time I will dig into it.
I might have an idea about the problem. As far as I remember the API has it’s own path, Normally zoneminder is http://zoneminder.mydomain.org/zm and thus API is based at http://zoneminder.mydomain.org/zm/api
From what you post it looks like you have redirected to NOT using /zm. I briefly tried this setting in ZoneMinder and it seemed like the API still located at http://zoneminder.mydomain.org/zm/api (in my test) - and thus things failed.
I gues that could cause the problem you describe