I rely a lot on Hikvision binary sensor for automation. However, recently I notice that some of my automations were not triggered when it suppose to. Upon further investigation, I realize that my Hikvision binary sensors have stopped working.
From iVMS-4200 software installed in my main PC, I can see the sensors are working fine. It just that it is not received by HA. I have to restart HA to make it work again.
I am wondering is this an isolated case or a known bug? Anyone else having the same issue?
I too noticed this a couple days ago, I restarted HASS and it started working working again. I think I caused the problem as I was having problems with my switch and had to restart the switch a few times. been OK since. still running 38.3 here
FYI, the only error I am seeing in my log is thrown by Orvibo S20 switch. I am wondering is it the same problem. This is what I have in my error log.
ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform orvibo
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/entity_component.py", line 151, in _async_setup_platform
entity_platform.add_entities, discovery_info
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/switch/orvibo.py", line 37, in setup_platform
from orvibo.s20 import discover, S20, S20Exception
File "/home/pi/.homeassistant/deps/orvibo/s20.py", line 314, in <module>
_setup()
File "/home/pi/.homeassistant/deps/orvibo/s20.py", line 56, in _setup
_SOCKET.bind(('', PORT))
OSError: [Errno 98] Address already in use
I am also having this problem. The binary-sensors import fine, but it only reports “off.” I know that the camera is working properly. I was wondering if it was a firmware problem. I got one of those “gray market” cameras (Chinese version flashed with English bios) and it doesn’t look like I can safely update the firmware (Hikvision warns that I may brick the camera). So I am running firmware version V5.2.5, the latest version is 5.5.0.
I’m thinking about running the python script on my local pc in a debugger to see what data is coming through. Anyone have any other ideas?
Thanks @arsaboo. My config looks the same. What camera/firmware are you using?
I checked the code and it updates the alertStream every 5 seconds… could it miss the event? I’m not sure how long hikvision publishes the event…
I also stepped through the code in a debugger on my computer and everything looked good. So it looks to me like a hikvision issue. That’s my best guess.
I have the DS-2CD2032F-IW, so we both run the same firmware. I’m wondering if I just need to try a reboot. I just realized I haven’t tried rebooting the camera. I should try that.
Is there a way to reboot the cameras once in a while, automatically? An option is to use a smart socket where the poe switch is connected, but prefer a more elegant solution
Some cameras have the option to reboot by a schedule. My hikvision does not. I think there is a way to get ssh into the camera… maybe there is a way to set up a cron job or something… I’ve seen tutorials on how to do that for people you have bricked their device by installing unsupported firmware. If you figure out how to do that. Please share!
piattaforma: hikvisioncam
host: 192.168.188.24
nome utente: admin
password: camera_psw
errore nel registro:
1:
status_code 405
11:58 componenti / hikvisioncam / switch.py (ERRORE) - il messaggio si è verificato per la prima volta alle 11:52 e confrontare 14 volte
2: si è verificato
un errore durante la connessione a http://192.168.188.24:80/MotionDetection/1/
11:58 components / hikvisioncam / switch.py (ERRORE) - il messaggio si è verificato per la prima volta alle 11:52 e confrontare 13 volte