Can yopu check your log to see if you have a line like this:
[MONITOR]: Configuration for Thing 'zoneminder:monitor:xxxxxx:monitor-1' is not loaded correctly.
The ‘xxxxxx’ should be changed toi the same id as your bridge?
I am quite sure that this is somethineg that appears when something isn’t started correctly. Somehow it seems like things can happend in a order so that it doesn’t work.
Nope, I really believe that your connection is stable. It is something in the binding that falsely indicates an unstable connection. If you take a look at the debug log all http calls is logged with returd code. I bet all of them returns 200 (=not wrong with your connection).I see somewhat the same problem, so I guess it is related to initialisation.
This is really strange, My openHAB build i #929, I am having somewhat the same problems. I have now build a addon from sources and when running in debug env. there is no problems, when running the same addon in #929 I see problemjs. I will try to update to latest openHAB build. Hopefully that solves the problem.
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…
I’ve recently updated to the 7/1 snapshot and I’m seeing better performance until this happens:
06:26:08.892 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:10.328 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:11.761 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:13.237 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:14.674 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:16.409 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:17.862 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:19.291 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
06:26:20.763 [ERROR] [andler.ZoneMinderServerBridgeHandler] - [MONITOR]: Method 'refreshThing()' for Bridge failed for thing='zoneminder:monitor:756ae518:monitor-1' - Exception='java.lang.NullPointerException'
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 a lot for you observations, I haven’t had time to look at them due to vacation :-). I will try to find som time to look at the code with your observations in mind.
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’.
Is it possible to change the ‘state’ of the ZM server in rule?
Here is a short log
2017-08-16 19:01:57.077 [ItemCommandEvent ] - Item 'ZoneMinderMonitorLiving1_OperatingMode' received command Monitor
2017-08-16 19:01:57.080 [ItemStateChangedEvent ] - ZoneMinderMonitorLiving1_OperatingMode changed from Modect to Monitor
2017-08-16 19:02:35.977 [hingStatusInfoChangedEvent] - 'zoneminder:server:daced488' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): ZoneMinder Server Daemon not running
2017-08-16 19:02:35.980 [hingStatusInfoChangedEvent] - 'zoneminder:monitor:daced488:monitor-2' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2017-08-16 19:02:35.987 [hingStatusInfoChangedEvent] - 'zoneminder:monitor:daced488:monitor-3' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2017-08-16 19:02:35.988 [hingStatusInfoChangedEvent] - 'zoneminder:monitor:daced488:monitor-1' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2017-08-16 19:02:53.202 [hingStatusInfoChangedEvent] - 'zoneminder:server:daced488' changed from OFFLINE (COMMUNICATION_ERROR): ZoneMinder Server Daemon not running to OFFLINE (CONFIGURATION_ERROR): ZoneMinder Server Daemon not running
@whopperg, yes the logs do show that zmc has stopped working. It is some sort of race condition which cause zm to shutdown. Here are the details of it.