dahua: AD410: Failed to read data and goes goes offline

Version of the custom_component

Dahua version 0.9.34 on HACS 1.18.0

Configuration

I do not have a configuration as it was done through the integration. It should be noted that I did enable the ‘cross region detection’ because without it enabled, motion detection didn’t work until it was enabled. When I was listening for events, I did noticed that it seemed required.

Describe the bug

I am seeing errors appear in my home assistant log related to teh following:

Logger: custom_components.dahua Source: custom_components/dahua/vto.py:355 Integration: Dahua (documentation, issues) First occurred: 4:39:16 PM (1 occurrences) Last logged: 4:39:16 PM

Debug log


I do not have debug logging enabled but I can enable it and wait for it to reoccur if that would help.

ailed to read data: b' \x00\x00\x00DHIP\xdc^,f\x08\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00{"id":8,"method":"client.notifyEventStream","params":{"SID":513,"eventList":[{"Action":"Stop","Code":"CrossRegionDetection","Data":{"Action":"Appear","CfgRuleId":1,"Class":"Normal","CountInGroup":0,"DetectRegion":[[0,0],[0,4093],[0,8191],[8191,8191],[8191,4093],[8191,0]],"EventID":10437,"EventSeq":222,"FrameSequence":3113933,"GroupID":222,"LocaleTime":"2022-01-25 16:39:16","Mark":0,"Name":"IVS-1","Object":{"Action":"Appear","Age":0,"Angle":0,"Bag":0,"BagType":0,"BoundingBox":', error: substring not found, Line: 348
Failed to read data: b' \x00\x00\x00DHIP\xdc^,f\x08\x00\x00\x00t\x04\x00\x00\x00\x00\x00\x00t\x04\x00\x00\x00\x00\x00\x00{"id":8,"method":"client.notifyEventStream","params":{"SID":513,"eventList":[{"Action":"Start","Code":"CrossRegionDetection","Data":{"Action":"Appear","CfgRuleId":1,"Class":"Normal","CountInGroup":0,"DetectRegion":[[0,0],[0,4093],[0,8191],[8191,8191],[8191,4093],[8191,0]],"EventID":10439,"EventSeq":224,"FrameSequence":3114692,"GroupID":224,"LocaleTime":"2022-01-25 16:40:25","Mark":0,"Name":"IVS-1","Object":{"Action":"Appear","Age":0,"Angle":0,"Bag":0,"BagType":0,"BoundingBox":[2984,3504,5304,7984],"CarrierBag":0,"Center":[4144,5744],"Confidence":0,"DownClothes":0,"Express":0,"FaceFlag":0,"FaceRect":[0,0,0,0],"FrameSequence":3114692,"Gender":0,"Glass":0,"HairStyle":0,"HasHat":0,"Helmet":0,"HumanRect":[0,0,0,0],"LowerBodyColor":[0,0,0,0],"MainColor":[0,0,0,0],"MessengerBag":0,"ObjectID":582,"ObjectType":"Human","Phone":0,"RelativeID":0,"SerialUUID":"","ShoulderBag":0,"Source":0.0,"Speed":0,"SpeedTypeInternal":0,"Umbrella":0,"UpClothes":0,"UpperBodyColor":[0,0,0,0],"UpperPattern":', error: substring not found, Line: 348
Failed to read data: b' \x00\x00\x00DHIP\xdc^,f\x08\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00{"id":8,"method":"client.notifyEventStream","params":{"SID":513,"eventList":[{"Action":"Stop","Code":"CrossRegionDetection","Data":{"Action":"Appear","CfgRuleId":1,"Class":"Normal","CountInGroup":0,"DetectRegion":[[0,0],[0,4093],[0,8191],[8191,8191],[8191,4093],[8191,0]],"EventID":10439,"EventSeq":224,"FrameSequence":3114692,"GroupID":224,"LocaleTime":"2022-01-25 16:40:57","Mark":0,"Name":"IVS-1","Object":{"Action":"Appear","Age":0,"Angle":0,"Bag":0,"BagType":0,"BoundingBox":', error: substring not found, Line: 348
Failed to read data: b' \x00\x00\x00DHIP\xdc^,f\x08\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00s\x04\x00\x00\x00\x00\x00\x00{"id":8,"method":"client.notifyEventStream","params":{"SID":513,"eventList":[{"Action":"Start","Code":"CrossRegionDetection","Data":{"Action":"Appear","CfgRuleId":1,"Class":"Normal","CountInGroup":0,"DetectRegion":[[0,0],[0,4093],[0,8191],[8191,8191],[8191,4093],[8191,0]],"EventID":10441,"EventSeq":226,"FrameSequence":3117357,"GroupID":226,"LocaleTime":"2022-01-25 16:46:25","Mark":0,"Name":"IVS-1","Object":{"Action":"Appear","Age":0,"Angle":0,"Bag":0,"BagType":0,"BoundingBox"', error: substring not found, Line: 348


About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 19 (6 by maintainers)

Most upvoted comments

That didn’t seem to fully fix this issue. I’m still digging in.

I was able to reproduce this and found the bug with the parsing of the AD410 events.

It’s fixed in 0.9.35

https://github.com/rroller/dahua/releases/tag/0.9.35