Grandtech III turns itself off

Support and queries relating to all previous versions of ZoneMinder
Locked
jerji
Posts: 13
Joined: Mon Jan 15, 2007 3:29 am
Location: Canberra, Australia

Grandtech III turns itself off

Post by jerji »

Hi,

I am using zoneminder to monitor our church facilities after four breakins :cry:

It has been working REALLY well, but...

I have noticed lately that one of three grandtech cameras that were all working fine has suddenly started turning itself off :?

I have it changing from monitor to modect at night and then back to monitor during the day, all via a cron job, which seems to be working perfectly :)

When I go in to check the system the camera in question has turned off the 'enable' tick in the config. I turn it back on and it accepts the change (the console has the camera all back to orange - if it is in moitor mode - or green if it is in modect mode). Come back some time later and it is red again (mumble, mumble).

I know that no-one else is playing with it (for fear of broken fingers :wink: )

I have checked the forums but cannot find anything like this behaviour.

Any idea where I can start troubleshooting?

After another broken window last night I am keen to fix this ASAP.

Thanks

Jerji
User avatar
cordel
Posts: 5210
Joined: Fri Mar 05, 2004 4:47 pm
Location: /USA/Washington/Seattle

Post by cordel »

Is this system available through the internet and if so would you mind PMing me SSH and web access?
Flash_
Posts: 441
Joined: Wed Jan 11, 2006 12:19 pm

Post by Flash_ »

Sounds like the bug with the last version where the enabled states are not saved when you switch run-modes.

I believe it was fixed in the most recent version (although I've not tried it) but it was reported by Phil at the time to be a bug rather than a config issue - the "Enabled" value simply wasn't saved to the sql.
User avatar
cordel
Posts: 5210
Joined: Fri Mar 05, 2004 4:47 pm
Location: /USA/Washington/Seattle

Post by cordel »

This problem has been addressed in the current release 1.22.3 and I think it was addressed in 1.22.2 as well.
I can patch your version of 1.22.0 to fix this issue or it might be better for you to just upgrade to the current release. This is a known problem with the version you are running.

Regards,
Corey
Locked