Cannot add DS-KV8213-WME1(C): ISAPI error Client error '404 Not Found' for url 'http://192.168.1.25/ISAPI/System/status' #196
Comments
|
@bkarakashev mind sharing your doorbell/camera model? |
|
I think your issue is very different. I'd recommend you open a separate issue. |
|
Similar error for DS-KV6113-WPE1(C). Logger: custom_components.hikvision_next.config_flow ISAPI error Client error '404 Not Found' for url 'http://192.168.1.77/ISAPI/System/status' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404 |
|
Maybe not working with doorbells (yet?) |
|
hi there, |
|
The following happens:
I also found this log: |
|
It finished the config flow showing a success message but than it showed this Failed setup, will retry: Unknown error connecting to http://192.168.##.##. Cannot initialize hikvision_next. Error is 'str' object has no attribute 'get' |
|
That's correct, config flow finished successfully. |
|
Update the branch and check again. |
|
No devices or entities |
|
Home Assistant Core |
|
I added the lines in config.yaml, enabled debug in the integration page, filtered the logs in home Assistant core by http://192.168.1.77/ISAPI/System/deviceInfo |
|
I also temporarily stopped an addon that has access to the device. If I need to do something different please let me know. |
|
Also, my device is DS-KV6113-WPE1(C) if it matters in any way |
|
This is the output: <?xml version="1.0" encoding="UTF-8"?>
<DeviceInfo version="2.0"
xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceName>OUTDOOR STATION</deviceName>
<deviceID>7d49925b-4fc7-406b-a0ec-bc5e3359252f</deviceID>
<deviceDescription> Vis</deviceDescription>
<deviceLocation>STD-CGI</deviceLocation>
<systemContact>STD-CGI</systemContact>
<model>DS-KV8213-WME1(C)</model>
<serialNumber>DS-KV8213-WME1(C)0120230508RRAB0353909</serialNumber>
<macAddress>bc:5e:33:59:25:2f</macAddress>
<firmwareVersion>V2.2.77</firmwareVersion>
<firmwareReleasedDate>build 240515</firmwareReleasedDate>
<bootVersion>33685581</bootVersion>
<bootReleasedDate>1574159</bootReleasedDate>
<hardwareVersion>0x0</hardwareVersion>
<encoderVersion>V2.9</encoderVersion>
<encoderReleasedDate>build 240223</encoderReleasedDate>
<deviceType>VIS</deviceType>
<subDeviceType>villaDoorStation</subDeviceType>
<telecontrolID>88</telecontrolID>
<supportBeep>true</supportBeep>
<supportVideoLoss>true</supportVideoLoss>
<alarmOutNum>2</alarmOutNum>
<alarmInNum>4</alarmInNum>
<RS485Num>1</RS485Num>
<customizedInfo></customizedInfo>
</DeviceInfo> |
|
These are the logs I was able to capture: |
|
@felipecrs I don't see any errors, does it work for you? |
|
Not really, it stays under the same situation:
And no error is thrown in the logs indeed. |
|
ha, I found sth, we are close! |
|
logs helped |
|
Yay, it works! chrome_80Gp33MIbU.mp4 |
|
@maciej-or do you have some script to generate fixtures for you? I can try generating for my device. |
|
yes please, all you need is to hit DOWNLOAD DIAGNOSTIC button and send the file |
|
sth went wrong all requests have 401 unauthorized status, did you change integration user access? |
|
Not really: chrome_CVsbz4sSSN.mp4config_entry-hikvision_next-01JATHQFSAS7NS9RAS04T5DS7A (1).json |
|
This works: Maybe authentication is different for Hikvision doorbells? But then how come the entities are working? Weird. |
|
The same connection is used for entities and diagnostics. Weird indeed. Another wrong behaviour is you don't have picture for stream. It is displayed in the circle and on the video until stream starts. in the web browser snapshot should appear |
|
Additionally I found these logs: But I also found these: Which indicates that |
|
That's the question why by init deviceInfo returns valid data with status 200 and in diagnostic 401? |
$ curl --fail-with-body -sSL --digest -u 'admin:pass' http://192.168.1.25/ISAPI/Streaming/channels/101/picture --output image.jpegBut doesn't work through the browser:
Which I suppose means Basic Auth isn't supported, only Digest.
$ curl --fail-with-body -sSL --digest -u admin:pass http://192.168.1.25/ISAPIContentMgmt/StreamingProxy/channels/101/picture
<!DOCTYPE html>
<html><head><title>Document Error: Not Found</title></head>
<body><h2>Access Error: 404 -- Not Found</h2>
<p>Can't locate document: /ISAPIContentMgmt/StreamingProxy/channels/101/picture</p>
</body>
</html>
curl: (22) The requested URL returned error: 404 |
|
I believe the most reasonable explanation is that the integration isn't using the proper authentication method when collecting diagnostics. |
|
you are right, I found small bug in authentication method detection |
|
Weird. The same behavior was kept. @mihaimdinca can you try it too? |
|
I do not see any difference compared to previous iteration. |
|
@felipecrs let's see what will happen if we disable basic auth detection |
|
I found this in the logs: But I don't know if these errors are thrown because of the integration. |
|
If I clear the logs and then reload the integration, the error throws again: Weird. |
|
does it occur after commenting out this line? |
That's too bad, the bug you had found actually made sense! |
@mihaimdinca the device in fact works now, pretty much alright. That's a huge improvement lol. Maybe you forgot to restart your HA and re-add the integration after updating the branch? |
I agree it works. I was referring to the previous test version when I said it is no different from the present one.I am getting the camera feed and the diagnostic section. It is a very nice start. I hope in the future we may also get motion sensor, call sensor, door switch and so on. |
|
Or am I missing something? |
|
No, I think we are on the same page then. |
|
I found this home-assistant/core#124653 |
|
Wow. That's crazy. Thank you. |
|
hi @felipecrs the bug related to aiohttp is fixed in HA 2024.12.0 in the meantime new version of hikvision_next was released you can check both |
|
I think this means it's working:
I can stream video too. Yay! Maybe someday we can also get some useful sensors or event entities, like button pressed or a switch to unlock the door. Thank you very much so far. |
When I fill the doorbell URL, username and password, and press the button, the form just refreshes and the device is not added.
I can see the following in the logs:
I can confirm ISAPI is working though:
The text was updated successfully, but these errors were encountered: