Compatibility with Dreame L40

[incline02]

Description

As of now, I have my vacuum bot entity. When I try to create an MQTT Vacuum Camera integration, on the very first screen (Camera setup), I select my vacuum entity and click submit and get a "Unknown error occurred". talking to some other users, I hear it's not compatible yet with Dreame L40

Solution

compatibility with dreame L40

Alternatives

I've tried HomeAssistant stock camera integration, homekit integration, Proxy camera, and go2rtC they all give the same results when I try to watch the live stream full screen in homekit: When watching the preview of camera, it seems to update every 5 seconds. When going into the live stream, it's on constant buffer.

Context

No response

[sca075]

@incline02
This integration works with all vacuums integrated via mqtt:


The error indicates that your vacuum somehow do not provide any data to MQTT, if you are using the stock firmware so you can use for Dreame L40 this integration instead.
Sorry but can't do that within this project... unless.. the vacuum entity is providing this data to MQTT... I know it seams a little strange.. but soon I will release some library that can probably be used...

[sca075]

@incline02 I did read the conversation you had here I'm wander is the vacuum is having a camera entity with data in "valetudo" format.. probably.. but this is a huge work around.. if the vacuum data instead are provided as an MQTT entity then this camera could work.

[sca075]

@incline02 had a look on the code of the integration you are using and I do not think you will found out the data in there. But so far I can see the Bot Current Map is actually already decoded and rendered as it should be...

Probably there is some setting to tweet on your proxy.. but I think you got to investigate.

mmmm I can try one think only but this mean.. develop a different camera but before of all.. to let you try it I would need to create a dummy test camera. This could take a while.. mmmm.. the idea basically is the following:

• yaml config a camera that will use the default value.
• will render one or two dummy images to check if HomeKit is happy with those images.. if not sorry but can't help.
  if this solve the problem you have with the rendering (without proxy) probably we can use "bot current map data" and render your vacuum.. but this work is not going to be publish as an official part of this project.. basically.. this would create a bridge for your bridge... it isn't a clean way to do this to be clear.

[incline02]

Well, I'm available for testing for the first part of your message but I agree a bridge of a bridge wouldn't be sustainable.

Whatever you choose, I'll make myself available.

[sca075]

@incline02

Here we go this is a just a test camera that reproduces 3 different images at interval of 3 sec.
If this is rendered correctly in HomeKit we can give a try to decode the images from the integration you are currently using.

test_camera.zip

You will need to decompress the zip in the custom_components of Home Assistant and add to your configuration.yaml the following:

camera:
  - platform: test_camera
    name: "Test Camera"
    images:
      - "custom_components/test_camera/test_png/test1.png"
      - "custom_components/test_camera/test_png/test2.png"
      - "custom_components/test_camera/test_png/test3.png"
    interval: 3

The 3 images was downloaded from wikipedia and are 3 desktop view.
If that works once again.. I can seriously think to get in contact with @Tasshack and try to found with him a solution.

[incline02]

just got our mail.

Following your instruction, I'll report as I'm done, please stand by.

[incline02]

unfortunately it doesn't work. Keeps buffering :/ (works as expected on HAOS dashboard)

[Tasshack]

Please note that Dreame Vacuum integration has nothing to with MQTT or does not provide any MQTT connection or entity for it.

[incline02]

So back to square one on how to get the video stream for the entity decoded and encoded properly for homekit... We can close this topic then.

Like another user you discussed with, they and I tried everything but it doesn't work. I've got a netatmo camera > homeassistant > homekit bridge > homekit and it works so it really is just this stream from the bot entity.

[Tasshack]

You need to learn and master the ffmpeg usage for that.

[Tasshack]

You are the the wrong place since you dont have a rooted vacuum...

Tasshack/dreame-vacuum#724

[Tasshack]

ffmpeg is a tool for converting any media format to any other media format so you cannot find examples for infinite possibilities, instead you need to read its documentation.

https://www.reddit.com/r/ffmpeg/comments/rw9vjz/convert_mjpeg_to_h264_livestream/
https://ffmpeg.org/ffmpeg-all.html

[incline02]

So I have tried to the best I could:

1. get the dynamic URL (token)

2. Check if the URL is active by copy pasting the template result in a browser, works and I refreshed every time to make sure the token is valid 3. I copy pasted said URL in FFMPEG camera config 4. 5. I've also tried dynamic url (#'ed in the screenshot above 6. Finally I've tried extra_args and redone everything above.

None of the above works: the camera shows unavailable in the dashboard.

[incline02]

I think I'm gonna give up. It's getting excruciating.

I've tried 2 test url

1. https://www.earthcam.com/usa/louisiana/neworleans/bourbonstreet/?cam=bourbonstreet error: wrong header
2. http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/Sintel.mp4 barely works: freezes, buffers, wrong header
3. My own static urls extracted from template work in safari just like 1. and 2. but don't display via FFMPEG

none of the above work in got2RC or FFMPEG. got2rC is supposed to read anything but never worked. it's hair pulling

When I try my url, I don't even get header errors. I've tried tons of arguments, including -useragent, none would work.

People with the exact same issues never got answers, those with similar but different either don't use home assistant, or sometimes they're not sharing their configuration file, or they went another route which is much more complicated that just making ffmpeg work in config file or don't use the dreame L40. I'm in a pickle and building up anger, time to go outdoor

[sca075]

@incline02

Actually Home Assistant has a kind of native support for FFMPEG.. it can also stream snapshots.. and of course.. there is to make a complete new implementation probably for lat it works with this kind of cameras we use for the maps...

I'be outdoor too have an I perfectly understand this can be a little frustrating... I'm anyhow the kind of person that do not give-up easily.. also knowing Apple quite well, nothing is 100% easy when using 3dt parity software and hardware with them product, but there isn't to disparate as "better to be frustrated because we try then doom as we never did try".

Apparently there is a also an "ffmpeg-python" library that I'll study a little and can be useful too for the next level of implementation as there is a native I/O library that I'm willing to explore.. never the less.. I hope you can kindly understand how difficult could be to maintain a project like this or the one of @Tasshack natively designed for Home Assistant (not HomeKit).

[incline02]

alright, I've made progress:

The robot camera of the vacuum goes into a proxy camera which goes into go2rtc and success, I can see it in there as well as I've managed have a shell command update the token in go2rtc (thanks chat GPT).

Now ,go2rtc provides me with a dozen links to use into Proxycamera, Generic camera and/or FFMPEG but bad news: none of those links work and this time, no error message other than "unvailable