I've tried using the manual PTZ controls; switching between Preset 1(Day) and Preset 2 (Night) for each camera, but to no effect. The PTZ controls seem to be enabled (checkbox in upper left corner) when digging into each camera's settings on the PTZ tab. Is there some other B.I. global PTZ setting that I may have inadvertently turned off, thinking that "yeah, these camera's don't have that function, so I might as well disable that control"? If so, I can't find it again, LOL.I guess go into BI and can you select Preset 2 for that camera? Maybe the PTZ controls for that camera is turned off in BI?
My 5442s from Andy are working just fine with the utility and the Feb. 2022 firmware.Has anyone had any issues getting this Sunrise/Sunset switching to work correctly on the EMPIRETECANDY / Dahua 5442 cameras that are running the latest (Feb. 18, 2022) firmware that just came out this week?
Unfortunately I am setting this up for the first time, so I don't know if the problems I am having are due to this newest firmware behaving differently, or just some other setup mistake/typo of my own doing. I followed the directions explicitly from the first post of this thread (using the more recent native B.I. method, not the old software utility), and I do have the cameras set to "Full time" and Always Enable "Day" in Profile Management. My daytime camera settings are forced to Color mode, and Night settings are forced to B/W, so the changeover should be obvious, but I am currently seeing only color mode regardless of time.
The B.I. logs indicate that each of the cameras do see the "Event: PTZ Preset 2 (2202)" happening, followed by the "Web: HTTP/1.1 200 OK" response at Sunset, so it would seem that they should be switching to B/W at that point, but it doesn't happen. I would think that would also indicate that my string with the Camera IPs, user/password info, and "0" or "1" at the end, is being read and interpreted correctly, but perhaps these cameras on the new firmware want to see a different number at the end (some cameras seem to need a "3", right?).
Any suggestions on other troubleshooting steps that I should take?
Yes, as I noted above in post #444, the issues are resolved, they were due to my use of an "@" symbol in my camera password, which wasn't being parsed correctly in the HTTP API command string that is used in the PTZ control presets.My 5442s from Andy are working just fine with the utility and the Feb. 2022 firmware.
^Yes...I haven't tested the limits like bp2008 just did (or looked it up...what a concept), but I would call this an internal "sanity check" on the logic of referencing anything relative to sunrise/sunset if it is SO far off as to perhaps be irrelevant. Most of the time we are referencing these times as a night/day camera settings adjustment due to dramatic changes in lighting, so the offset is usually considerably less than an hour from sunrise/sunset.Hmm. It looks like you need to be scheduling a time that is within 2 hours and 30 minutes of a sunrise/sunset time, or else the box gets grayed out. Adjust your time a little.
Grayed out no matter what time I set it for. Very strange and frustrating!Odd..although it is unfortunate that your latest screenshots show no offset at all from sunset time. If you offset the desired time by say 15 minutes (from actual sunrise or sunset shown in the box) is the "Relative" checkbox still greyed out?
Grayed out no matter what time I set it for. Very strange and frustrating!
Ugh, you know what guys, I was one version behind (5.5.6.8). Just updated to 5.5.6.9 and it is indeed broken like that. Someone should send a bug report to BI support.