onvif: Not enough data to satisfy content length header when using older Dahua firmwares (Dahua, Lorex, other rebrands) -- workaround scheduled for 2025.8.x -- can also be solved with a firmware update if available

[familyegu973]

The problem

Hello,

I report here an issue when I tried today to upgrade from HA 2025.6.3 to HA 2025.7
My ONVIF integration with my DAHUA product, has been broken. I got the following message
Could not connect to camera 192.168.1.108:80: Response payload is not completed: <ContentLengthError: 400, message='Not enough data to satisfy content length header.'>

I did not performed any update on my DAHUA product, and never faced any issue like this one in the past during HA upgrade.

So I had to roll back on HA 2025.6.3 to retrieve Onvif integration working.

Is there something I missed ?

Best Regards

What version of Home Assistant Core has the issue?

2025.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[PeteRager]

Please resubmit with the correct fields filled out. You have a problem with the ONVIF integration but did not include that.

[home-assistant]

Hey there @hunterjm, @jterrace, mind taking a look at this issue as it has been labeled with an integration (onvif) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of onvif can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign onvif Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

onvif documentation
onvif source
_{^{(message by IssueLinks)}}

[TepMan]

Hi all,

have the same issue with my dlink DCS-8300LHV2, after the update to 2025.7.0 i had the connection issues. I have deleted the ONVIF integration an re-added it, now the device is found but stream profiles are disabled "by configuration" and i can't enable them and there is no camera entity anymore. Before 2025.7.0 evrything worked fine.

[xray3334]

Same issue with 2N IPONE camera

[PeteRager]

Please submit diagnostics and debug log file.

[Tumblehawk79]

Same thing
upgraded from HA 2025.6.3 to HA 2025.7.1
My ONVIF integration with my DAHUA product, is now broken. I get the following message:

Dahua - e0:xx:xx:xx:xx:xx
Failed setup, will retry: Could not connect to camera 192.168.x.xx:80: Response payload is not completed: <ContentLengthError: 400, message='Not enough data to satisfy content length header.'>

I deleted the integration and reinstalled same error, have not rolled back yet.

home-assistant_onvif_2025-07-05T10-03-05.735Z.log

[TepMan]

Here is the log:

Logger: homeassistant.components.onvif
Quelle: components/onvif/event.py:181
Integration: ONVIF (Dokumentation, Probleme)
Erstmals aufgetreten: 12:20:07 (1 Vorkommnis)
Zuletzt protokolliert: 12:20:07

Heizungskeller: No registered handler for event from b0:c5:54:5f:1c:5b: { 'SubscriptionReference': { 'Address': { '_value_1': 'http://192.168.178.105:8123/api/webhook/onvifb0c5545f1c5b', '_attr_1': None }, 'ReferenceParameters': None, 'Metadata': None, '_value_1': None, '_attr_1': None }, 'Topic': { '_value_1': 'tns1:RuleEngine/MotionDetector/MDEvent', 'Dialect': 'http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet', '_attr_1': { } }, 'ProducerReference': { 'Address': { '_value_1': 'http://192.168.178.104:80/onvif/device_service/8', '_attr_1': None }, 'ReferenceParameters': None, 'Metadata': None, '_value_1': None, '_attr_1': None }, 'Message': { '_value_1': { 'Source': { 'SimpleItem': [ { 'Name': 'IPCamera', 'Value': 'DCS-8300LHV2' } ], 'ElementItem': [], 'Extension': None, '_attr_1': None }, 'Key': None, 'Data': { 'SimpleItem': [ { 'Name': 'MDEvent', 'Value': 'MD Alarm(true)' } ], 'ElementItem': [], 'Extension': None, '_attr_1': None }, 'Extension': None, 'UtcTime': datetime.datetime(2025, 7, 5, 12, 20, 7, 123000, tzinfo=datetime.timezone.utc), 'PropertyOperation': 'Initialized', '_attr_1': { } } } }

logs.txt

[jterrace]

@TepMan I believe that "no registered handler for event" log line is unrelated to this issue.

There were some changes in this release to aiohttp related to content-length header processing.

@bdraco my guess is aio-libs/aiohttp#11139 may have triggered this. It could be that the content length response header is not being sent from the camera or is somehow malformed, leading to a behavior change of trying to read more bytes than available.

Is anyone here able to get an HTTP capture from their camera when this happens? Using something like wireshark?

[bdraco]

Definitely a wire shark or TCP dump, with follow TCP stream is likely going to be required to figure out what's going on here. It does seem likely that is a bug in the camera and is sending a partial payload.

[TorvaldUtne]

I have the same problem with a Lorex system since upgrading. I don't seem to have the option to download diagnostics.

[jorgeEF]

Reporting a bug on onvif integration as well (HA 2025.7.1):
"Error de configuración, se volverá a intentar: Could not connect to camera 192.168.1.5:80: Response payload is not completed: <ContentLengthError: 400, message='Not enough data to satisfy content length header.'>"

[TorvaldUtne]

home-assistant_2025-07-05T16-13-41.280Z.zip