Did anything change on your WiFi?Nelly’s db cam and it’s gone flashing blue again, happened 3x now. The only way I’ve been able to fix it is to reset and setup new. Should I be concerned and or start looking for a replacement?
Did anything change on your WiFi?Nelly’s db cam and it’s gone flashing blue again, happened 3x now. The only way I’ve been able to fix it is to reset and setup new. Should I be concerned and or start looking for a replacement?
Did anything change on your WiFi?
Something is resetting it...probably ONVIF...try this...
The DB just goes to AP mode (Ad-Hoc mode). Log in to it in client mode. (use original configuration password) You should be seeing the AP SSID.
You do not need to use your phone to fix this as you will see the SSID from any computer on your network. You have to use batch configuration to do this though.
Once you log in to it with Batch Configuration check the configs and it should be all the same and change the DB from AP mode to client mode. You settings should be there.
My two admin accounts and passwords remained intact.
I saw this issue when using the ONVIF-MQTT plugin and BI ONVIF and switched to BI RTSP.
The BI server is on one W2016 of two servers running on a Lenova M93A with a Gb NIC and a Wireless card. I just turn on the WLAN and connect to the doorbell via WiFi and Batch Configuration.
I will have to check it out...thanksWhat your thoughts on the new v5 EZVIZ app?
I liked the "day" fast forward feature
....
Most important:
1 - admin access
2 - validate RTSP and ONVIF connectivity
3 - remove and disconnect DB from cloud app
For MQTT stuff here always utilize MQTT explorer.
Once connected to the DB via the DB AP mode and logged in with Batch Configuration...
Change the admin password and add another admin user and password or just add another user if you want to keep what you already have configured.
Using Batch Configuration configure the SSID of your choice (home ssid and pw) and configure a static IP versus DHCP.
Once rebooted in client mode then you will be able to access the DB via RTSP and ONVIF.
Then if you want to install a cloud app on iOS or Android just add the camera manually to the app in the cloud.
Are you talking about a different password?⦁ DO NOT change the admin Password in iVMS-4200 or Batch Config. Tool. We found when loading the Batch Configuration Tool for the first time and your Doorbell is Discovered, it will show as "not activated" under security (IGNORE THIS), DO NOT Click the Activate Button. It will force you to set a NEW admin Password on your device (Doorbell) which for most Hikvision Cameras would be a normal process but in this case it disrupts future re-inclusions/configuration through the Mobile Apps. Once done, it is not reversible and cannot be Reset either by Factory Settings Reset or Firmware Reload. - rafale, rafale, - Mtoo22 (Hikvision Partner) Note: digdoug has had a different experience, his DB's password Reset back to it's original password.
I admire your dedication to privacy and security.Understood. The 101 FAQ relates to using the DB with the cloud app. Modifying the firmware / taking it off the cloud can be treacherous and you can brick you DB.
Yes here took the DB off of the cloud (no apps) when upgrading from the Nelly firmware to the Hikvision firmware and changed the admin password and added another admin user.
Once you configure your DB with your phone it becomes connected and managed by the cloud server even if you have your phone off and personally I did not want that.
That said many or most of the smart phone apps now will update your firmware.
Recently reinstalled the LaView Android app on my phone and it did connect right way just to test it and then removed it.
Here not tethered to any of my 5 T-Mobile SIM cards, phones are typically off. I have a deal with T-Mobile that if someone calls a cell phone that is off user gets a disconnected message.
Are you talking about a different password?
Yes and an added user.
You can check it for ONVIF using the Linux/Windows ONVIF application. It does work except it locks up occassionally.
ONVIF PIR triggers do work for me but they were too sensitive and I could not adjust them right with the original Android app and or Batch Configuration.
Here no package delivery folks ring the doorbell these days (Amazon, FedEx, UPS or USPS). The motion detection is what rings the doorbell and creates events.
Guessing it is now an invasion of the privacy of the delivery folks. I had this issue in the early 2000's post 911 installing cameras everywhere. Issues with privacy relating to job site monitoring. Facial recognition is a big issue now a days just like finger printing was in the 1930's.
Too much motion (false triggers) from the built in PIR was very low on the WAF.
So here went with a small outdoor on the front porch 433Mhz PIR facing the doorbell. (the PIR talks to a Tasmota Sonoff 433Mhz MQTT hub).
In the old house in the early 2000's used an Optex combo camera PIR (wired) facing the front door from the side and Geophone sensors adjacent to the cement walk from the driveway to the front door. Much easier now a days except that I prefer wired over wireless sensors and cameras.
I use it for JPG captures here to my OmniPro 2 alarm touch screen and HA stills. You can test that too typing:
hxxp:/ipofvideodoorbell/onvif/snapshot.jpg
The newer batch configuration program doesn't allow you to enable ONVIF.
ONVIF device manager for Windows lets you see the ONVIF configuration.
With this I can do RTSP, ONVIF and JPG captures. If using the cloud app the app itself will make changes to your configuration on your DB.
I do VPN to my home with my Android phone and run a Hikvision app on the phone which directly connects to my camera where I can see motion events recorded et al. I see the cloud features on the app and do not have any of it configured.
Frigate looks interesting, been using Deepstack through Blue Iris. So Google Coral runs locally, no cloud service, correct? I have read it is fast...If you are integrating into home assistant, I would recommend using frigate over any of the built-in motion sensing. It does AI detection and is very accurate and fast with a google coral. It uses MQTT to create a counter, motion sensors and snapshots of the detections.
ok on the 2.4 ghzUnderstood.
It is many times all related to the WAF. Here wife wouldn't touch security touchscreens or automation touchscreens for fear that she will debend the house.
@David L runs the LaView App / firmware doorbell and on his phones while concurrently connecting to Blue Iris and it works for him using RTSP.
The windows app locks up or the camera itself?
The ONVIF app locks up.
I think though the cloud app uses ONVIF to talk to your doorbell such that if you make changes to your doorbell with the ONVIF app the changes will revert back to the cloud configuration stuff.
What do you get from HA with the ONVIF integration? A sensor with an on/off State?
This and I do not use it much these days for automation triggers.
View attachment 106477
Video motion algorithms are better but not really good for outside. Best to use hard sensors outide. Here used combo hardwired Optex combo cameras with PIRs. There is 6 wires connected. 2 for PIR, 2 for night dark switch and 2 for tamper switch plus power to the camera and PIR board.
The ONVIF to MQTT PIR plugin appeared to reboot/reset my DB sometimes so I quit using it. Also stick to using 2.4Ghz rather than 5Ghz for your DB.
If only I had so much time to learn a new piece of hardware and frigate. Very cool stuff what option did you pick for the hardware (version of coral)?If you are integrating into home assistant, I would recommend using frigate over any of the built-in motion sensing. It does AI detection and is very accurate and fast with a google coral. It uses MQTT to create a counter, motion sensors and snapshots of the detections.
Yup, all local and done on the coral stick. Basically does the same thing as deepstack but live and with less overhead needed as the AI is running on purpose-built silicone. You can also run it without the coral as they are kinda hard to come by right now but with coral is so much quicker.Frigate looks interesting, been using Deepstack through Blue Iris. So Google Coral runs locally, no cloud service, correct? I have read it is fast...
ok on the 2.4 ghz
video motion algorithm in motioneye is what I suspect your suggesting to use instead of onboard hikvision. My FOV for the doorbell is pretty binary if you know what I mean so it might work out but who knows with wind and changing angle of the sun with the seasons? I would like to avoid more sensors.
If only I had so much time to learn a new piece of hardware and frigate. Very cool stuff what option did you pick for the hardware (version of coral)?
Sorry let me qualifyIt's running on my hassos box a I3 nuc with the google coral. The good news is there isn't much to learn about the hardware. The google coral is just it, it doesn't require any config outside of frigate. It does one thing and only that one thing and that is object recogonition.
Sorry let me qualify
What version of Google Coral did you get the usb stick the board etc