MikeLud1
IPCT Contributor
5.4.7.3 is not the Critical and highly stable version 5.4.6.3 is. I have IVS trigging working only with version 5.4.6.3.
Update 5.4.6.4 IVS Trigger Issues
- Thread starter thewolf56
- Start date
On that note, he should turn off auto-update completely. 5.4.6.4 was made the latest critical or highly stable update previously, but it was only rolled back to 5.4.6.3 after a few of us emailed Ken about the IVS trigger issues, So, with auto-update, it still would have updated him to a version where IVS triggers no longer worked. Luckily, I had the 5.4.6.3 exe downloaded previously as I was able to downgrade from 5.4.6.4 to 5.4.6.3 before changing the latest critical or highly stable update. It was not even available in the previous versions dropdown at that time.
Yep, got them there too! I deleted the camera, updated to 5.4.7.3, rebooted the machine, no joy. It is a Windows 7 machine, I have never updated because it is remote and on satellite internet, with very limited bandwidth.
go back to 5.4.6.3. When I went above that, they didn't work. I'll try 5.4.7.3 sometime this weekend. Planned on last night, but got too busy.
That's odd. Did it work before? Can you post screenshots of your screens like the ones I posted and the one @MikeLud1 posted from the alerts tab? Did you double-check that IVS is set in your camera's web interface and is actually triggering using the live view?
When we downgraded to 5.4.6.3, it all worked again for me.
sebastiantombs
Known around here
Yeah, Ken said it was supposed to be fixed on .3, but I had not had a chance to check myself. I didn't want to recommend something I had not tested myself, but I knew 5.4.6.3 definitely worked.
I think you got it! The find/inspect is not getting device information. I tried it for two other Dahuas at this location - a pair of IPC-HDW-2231R-ZS, in addition to this camera, an IPC -T2431T-AS. All of the cameras at this location come up with "bad request". All seem to work fine with IE through their menu systems. The three other cameras here, all Amcrest IP2M variations, appear to work fine with the Find/Inspect.
The network system here is simple and short - one Netgear POE switch and short cables, like 5 feet, going to the cameras. No dropouts with the cameras, so I seriously doubt it is a cable issue.
Attachments
Now we are getting somewhere (maybe)!
I suspect that in the camera GUI under System > Account > ONVIF user that it is corrupt or missing.
I see you are using admin as the user, but if the password has been changed too many times, maybe it didn't carry over.
I would make a new username under Account and then add that username to ONVIF user and see if that gets it going.
If there is an issue with the ONVIF user tab, that would explain the issue.
As an alternative, manually change the mainstream to: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
Since yours is just showing / that leads me to believe there is an issue pulling all the info over.
I suspect that in the camera GUI under System > Account > ONVIF user that it is corrupt or missing.
I see you are using admin as the user, but if the password has been changed too many times, maybe it didn't carry over.
I would make a new username under Account and then add that username to ONVIF user and see if that gets it going.
If there is an issue with the ONVIF user tab, that would explain the issue.
As an alternative, manually change the mainstream to: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
Since yours is just showing / that leads me to believe there is an issue pulling all the info over.
Looking at the results, I would agree with you. I'd guess that onvif user is not setup separately. That's part of the reason I was asking if it worked before. Try to narrow down setup issues vs the real software bugs you and I were experiencing from the updates.
DAMN!!
You got it! It WORKS!!
The admin password one all of the cameras has been changed maybe 3-4 times. I find it odd that all three Dahua ( @EMPIRETECANDY 's) did this at the same time. The two are older, and the password has been set since 2018. Regardless, I created a new user and password under ONVIF users under System in the IE web page for each camera, entered those credentials into BI for the cameras, and find/inspect worked, as did ONVIF/External motion.
Thanks!!
Lag seems to be fixed.
Looking at the log, it keeps showing DeepStack as restarting, so that could be why I am missing AI.
When I roll back to the stable version, it all works as intended. But of course that one doesn't have the custom model option.
Looking at the log, it keeps showing DeepStack as restarting, so that could be why I am missing AI.
When I roll back to the stable version, it all works as intended. But of course that one doesn't have the custom model option.