Eufy cameras no longer work with 1.9.7 (mse: unsupported scheme)

[z-master42]

After changing from 1.9.6 to 1.9.7 (Docker), the streams of my two Eufy cameras no longer work.
They are a T8410 and a T8210.
The stream comes via the eufy-security-ws addon in Home Assistant.

The message mse: unsupported scheme is displayed in the video stream.

When I switch back to 1.9.6, everything works again.

Do I have to make any adjustments in the config? This was previously generated automatically.

[misc2000]

I am right now working to get my Eufy doorbell T8210 cam that is working good in HA card view (over webrtc-camera) also forwarded to HomeKit.
during I did search here how to configure it in go2rtc for HomeKit I did notice the update to 1.9.7 and did update.
Now my eufy cam stops working also in HA itself. Not 100% sure if the root case is the update but it looks like.
Before the cam live view was working in HA card view over webrtc-camera always, and my main problem was a very slow streaming video in Apple Home app by forwarding the cam over the HomeKit integration of HA.
Now I understand that i should do it direct in go2rtc if I see it right?
But first I need to sort out if the update break my setup or not ???
And how can I go a version back to the old version of go2rtc in HA to verify?

[misc2000]

Update: still not working any more at all.
this is my config that was generated during installation with the eufy addons and webrtc-camera that worked good before the update.

streams:
  T8210P812419166F:
    - T8210P812419166F

And I see now this warning in the log:
23:30:05,783 trace [streams] dial cons=0 prod=0 error=streams: unsupported scheme: T8210P812419166F
23:30:05,782 trace [streams] check cons=0 media=video, sendonly, ANY
23:30:01,904 warn [rtsp] error=streams: streams: unsupported scheme: T8210P812419166F stream=T8210P812419166F

Can someone guide me how to downgrade to verify?

[AlexxIT]

Well. The T8210P812419166F scheme is definitely not supported. I'm not familiar with the eufy addon and don't know how it works. And I don't know why it worked before.

[z-master42]

I think the scheme is made up of model number and serial number.

The setup consists of the eufy-security-ws addon, the Eufy Security Integration, the WebRTC Camera Integration and Go2RTC (in some variant). The use of Go2RTC is actually included in the Eufy Security Integration documentation.

Stream provider is P2P and the stream URL is an RTSP.

[oig123]

I have the same problem.

[ahmed-elgamil]

Same problem here

[foddy-foo]

I see the same problem. My Eufy doorbell stream no longer works in Home Assistant when using 1.9.7
Rolling back to 1.9.6 makes it work again.

This is what I see in config

streams:
  T8210P6421501681:
    - T8210P6421501681

[AlexxIT]

And what you can see in config for old version?

[foddy-foo]

And what you can see in config for old version?

That is the config as seen once I rolled back to 1.9.6

[z-master42]

And what you can see in config for old version?

The config is the same for both versions.

[AlexxIT]

If someone is a developer - it might be helpful to know which commit broke. Just need to build a binary for each commit between 1.9.6 and 1.9.7. Should not be a difficult task, even if you don't know golang.

[z-master42]

You mean just try out nine different builds?

[AlexxIT]

Yes. Just git checkout, go run. Multiple times

[AlexxIT]

OK. Looks like we know the problem #1458
All incoming sources broken.

[misc2000]

Sounds great that you found the source of the problem.

Can someone please give me some how level instructions how to downgrade to 1.9.6 again until the problem is solved?

I am using a Pi4 with standard HAOS Image and did install all over the HA add-on store/hasc as explained in the eufy cam how's to's for HA.
I think go2rtc was installed from webrtc-camera when I installed it.

Could it be a try to uninstall webrtc-camera and reinstall it in the hope it will install again the older version from go2rtc?

[AlexxIT]

Fixed in latest master version

[AlexxIT]

WebRTC camera integration has old go2rtc version - 1.9.4

[foddy-foo]

Sounds great that you found the source of the problem.

Can someone please give me some how level instructions how to downgrade to 1.9.6 again until the problem is solved?

I am using a Pi4 with standard HAOS Image and did install all over the HA add-on store/hasc as explained in the eufy cam how's to's for HA. I think go2rtc was installed from webrtc-camera when I installed it.

Could it be a try to uninstall webrtc-camera and reinstall it in the hope it will install again the older version from go2rtc?

Personally I went to Settings, System then Backups within Home Assistant and looked through the recent backups listed. I saw one entry for go2rtc from the day before when the add-on got automatically updated. I selected that and restored (it only restores that one item not your whole HA). This took about 10 seconds to complete. I then restarted the whole Home Assistant and it fixed the problem. I've now turned off Auto-Update for that particular add-on. Hope this helps.

[z-master42]

Fixed in latest master version

Tried it out, it works.

Many thanks for the quick fix.

[misc2000]

Also for me its working again.

Now because I have some eufy users reading this a quick question:
I want to forward the video stream of the eufy doorbell with 2-way audio to HomeKit.
currently I have good and stable video with the direct HomeKit export from go2rtc. But a kind of slow-motion video from the HomeKit camera from the HA own HomeKit integration.
This are my config:

homekit.yaml:
- name: Haustürklingel
port: 56324
mode: accessory
filter:
include_entities:
- camera.haustur
entity_config:
camera.haustur:
linked_doorbell_sensor: binary_sensor.haustur_ringing
linked_motion_sensor: binary_sensor.haustur_motion_detected

go2rtc.yaml
streams:
T8210P812419166F:
- T8210P812419166F
homekit:
T8210P812419166F:
pin: 33322333
pairings:
...
How should the stream source: Tag look like in the HA HomeKit.yaml and do I need some more stream config in the go2rtc side to reach my goal?
Or can someone with a eufy doorbell cam share the relevant config parts?
Thanks

[saschawj]

For AlexxIT.
Seen the same issue for a bunch of cameras. Good that you potentially found the source of this, however I would like to add a portion of the log here, in case it helps:

END of File warning

12:31:53.503 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error=EOF url=http://192.168.XX.XXX:8123/api/camera_proxy_stream/camera.front_door?token=9eaaXXXXeead096c349d5e38ba3984a1a23e2aecc9b3d58be1902824e03b2
12:31:53.539 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error=EOF url=http://192.168.XX.XXX:8123/api/camera_proxy_stream/camera.ingarage?token=a3e0XXXX8e20e2fb5d77eb7c8fd5bd8a82e8d52d404aa66bcc66c7346c3c9cd9

New Stream error Warning with unsupported scheme

12:32:31.493 INF [streams] create new stream url=rtsp://127.0.0.1:8554/T8423TXXXXXXXXXX

As above unsupported scheme error

12:35:21.542 WRN [rtsp] error="streams: streams: unsupported scheme: T8170TXXXXXXXXXX" stream=T8170TXXXXXXXXXX
12:39:16.282 WRN [rtsp] error="streams: streams: unsupported scheme: T8423TXXXXXXXXXX" stream=T8423TXXXXXXXXXX

I have a whole bunch of Eufy cameras and as stated none are displaying any more.

Eufy Floodlight Cam S330 (Model: T8423)
Eufy Solocam S340: (Model: T8170)
Eufy Floodlight Cam E340: (Model: T8425)
Eufy Garage-Control Cam: (Model: T8452)

Should you need any tests done, please let me know.

[oig123]

Fixed in latest master version

thanks

[AlexxIT]

Unsupported scheme is correct error. Eufy integration creates an invalid config. This issue should be added to the eufy project.

[z-master42]

What should a valid configuration/schema look like? Use of entity ID?

[AlexxIT]

I have a list of 19 of my projects that I devote my free time to one by one. There are no definite plans for dates unless there are critical issues.

[mantiview]

@ fuatakgun: i've tried your steps, but it´s not working for me.

@ AlexxIT: i thank you for your time and skills, but -with all due respect and understanding- not working security cams (in ha) are critical! i hope you don't get me wrong.

[Stephan-4711]

If you have that critical security cams, I would recommend a professional survilance solution and nothing self build

[AlexxIT]

As I understand it, the problem is solved with two clicks. Stop release go2rtc addon and start master go2rtc addon.
I don't know why the HA GUI doesn't provide for a quick rollback of the addon to any preferred version.
A very obvious feature that HACS has.

[mantiview]

As I understand it, the problem is solved with two clicks. Stop release go2rtc addon and start master go2rtc addon.

Hi AlexxIT, thx for your reply!
I've tried this many times, but unfortunately it doesn't work.

[AlexxIT]

So you have some other problem and the release won't change anything. Because the release won't bring anything new.

[roflware]

Hi @AlexxIT and @fuatakgun, thanks for your replies.

I generally do not have issues with my doorbell, thanks for that. In terms of receiving hundreds of warnings per second, I just want to confirm that this model is supported along with the firmware version and that they are acceptable:

T8160
Firmware: 3.4.2.4

Thanks for all that both of you do!

[gewaechshaus]

Hey guys,

this minimal yaml config is working (on a dashboard) with the Add-On master release.

type: custom:webrtc-camera
entity: camera.buero1
poster: image.buero1_event_image
ui: true
muted: true
shortcuts:
  - name: Play
    icon: mdi:play
    service: eufy_security.start_p2p_livestream
    service_data:
      entity_id: camera.buero1
  - name: Stop
    icon: mdi:stop
    service: eufy_security.stop_p2p_livestream
    service_data:
      entity_id: camera.buero1
ptz:
  service: eufy_security.ptz
  data_left:
    entity_id: camera.buero1
    direction: LEFT
  data_right:
    entity_id: camera.buero1
    direction: RIGHT
  data_up:
    entity_id: camera.buero1
    direction: UP
  data_down:
    entity_id: camera.buero1
    direction: DOWN

But I can also verify that warnings are flooding the log @AlexxIT @fuatakgun @roflware

Cheers
Jan

[z-master42]

I am using the latest master version in a Docker container in conjunction with the WebRTC Camera card and the Eufy addon and integration and I have no ongoing warnings in my log.

[Minta79]

After changing from 1.9.6 to 1.9.7 (Docker), the streams of my two Eufy cameras no longer work. They are a T8410 and a T8210. The stream comes via the eufy-security-ws addon in Home Assistant.

The message mse: unsupported scheme is displayed in the video stream.

When I switch back to 1.9.6, everything works again.

Do I have to make any adjustments in the config? This was previously generated automatically.

Hi. How does that work: "When I switch back to 1.9.6, everything works again."? And is it possible to install an older version of Home Assistant [Add-on]?

[roflware]

Hi. How does that work: "When I switch back to 1.9.6, everything works again."? And is it possible to install an older version of Home Assistant [Add-on]?

Possibly if you do a local install? Create the folder in the right directory in Home Assistant, wget the URL, unpack the zip, chmod it, and then restart HA. You should be able to find it in the add-ons section under local add-ons and then install it that way. This is just a guess since I installed a different Eufy add-on that way.

[z-master42]

If you do not know this, you are not using the Docker version.

To get the latest version in Home Assistant, install the master version of the Home Assistant add-on. It's all here.

[Minta79]

If you do not know this, you are not using the Docker version.

To get the latest version in Home Assistant, install the master version of the Home Assistant add-on. It's all here.

Thank you, but the lastest verion does not work.

[roflware]

Hi @AlexxIT and @fuatakgun, thanks for your replies.

I generally do not have issues with my doorbell, thanks for that. In terms of receiving hundreds of warnings per second, I just want to confirm that this model is supported along with the firmware version and that they are acceptable:

T8160 Firmware: 3.4.2.4

Thanks for all that both of you do!

Hey @fuatakgun, can you please confirm that the above-mentioned model and firmware should be supported?

Specifically:

• eufyCam S330 (T8160), firmware: 3.4.2.4
• eufyCam S330 (T8160), firmware: 3.2.2.5 (it says it's up to date, not sure why it can't match the other firmware)

Thanks!

[fuatakgun]

@roflware , it is not realistic to ask me to confirm if a specific device/firmware is working. I own a couple of eufy cameras, I cannot confirm it. Only other users can confirm it.

Moreover, this specific issue is about go2rtc, not directly related to eufy.

[roflware]

@roflware , it is not realistic to ask me to confirm if a specific device/firmware is working. I own a couple of eufy cameras, I cannot confirm it. Only other users can confirm it.

Moreover, this specific issue is about go2rtc, not directly related to eufy.

@fuatakgun: This, as I learned, was more of a question of what bropat's Eufy integration can support, which you specifically highlight in your readme, so I've already confirmed that. It would have been more helpful if you directed me to there, instead.

The reason for me asking this at all is for process of elimination to better understand why it still does not work, even though Alex says otherwise. Since my Eufy devices are supported by bropat and only sometimes works with Alex's go2RTC, I (as well as others) are still unfortunately in the same rut with "mse: unsupported scheme". My only conclusion at this point would be that I would need to find an alternative RTC that has better stability for Eufy, if such exists.

[fuatakgun]

@roflware if you have go2rtc master, latest eufy-security add-on and integration, that is all.

I am responding to 10 different users per week and I am not fine to say "look at readme" anymore, because it is supposed to be the first thing to do.

Lastly, if it is working sometimes but not always, it is integration related, not go2rtc.

[roflware]

@roflware if you have go2rtc master, latest eufy-security add-on and integration, that is all.

I am responding to 10 different users per week and I am not fine to say "look at readme" anymore, because it is supposed to be the first thing to do.

Lastly, if it is working sometimes but not always, it is integration related, not go2rtc.

@fuatakgun: Regarding device support, it wasn't really clear and took some digging, so there could be some improvements there.

The only thing I can glean from this thread is that given the inconsistencies with actually working, this seems to be a go2rtc issue with the s330 cameras, given that the doorbell works relatively fine.

[roflware]

Hey @AlexxIT, I think I will finally be in a good place with my cameras after figuring this bit out: the Eufy cameras apparently randomly serve up either WebRTC (appears as RTC on the stream itself), MSE, or MJPEG. Any time MJPEG is selected, it takes forever, crashes, or artifacts to a green or gray screen. Via go2rtc, is there a way for me to only enable it to serve WebRTC and MSE only and disable MJPEG from being served? Controlling it from the HA card still doesn't avoid go2rtc serving MJPEG anyway, because if I specify "mode: webrtc,mse", it gives me an error. But if I could guarantee WebRTC or MSE from go2rtc, it would consistently work well for me.

[AlexxIT]

By default, the mode parameter is set to webrtc,mse,hls,mjpeg. Because the card doesn't know in advance what technologies your browser and stream supports. Changing the mode parameter should help select only the preferred technologies. I don't know why it might not work for you.

Also, the stream usually comes with the H264/H265 codec - so only webrtc/mse/hls will work for you.
Or stream comes with MJPEG codec - so only mjpeg will work for you.
Support for both codec types is a very-very rare situation.

[roflware]

That last comment is really interesting. I know that I've seen both RTC/MSE and MJPEG, with the latter being very choppy and terrible. I'm not sure what causes that to happen.

But okay, it sounds like this can only be determined by the card, understood.

[fuatakgun]

@roflware , are your cameras supporting RTSP natively or is it handled by integration?

[roflware]

@roflware , are your cameras supporting RTSP natively or is it handled by integration?

This is via the integration by bropat, what I mentioned before. It serving up RTSP would be a completely different conversation, but I imagine that Eufy doesn't support it since it's solar powered.

[fuatakgun]

If it is coming from eufy-security addon and eufy_security integration, it will always generate rtsp, never webrtc.

@AlexxIT does not have full picture of our custom stream generation implementation.

[roflware]

I clearly don't know the entire flow here, but all I do know is that when referencing the the entity, it is streamed either as WebRTC, MSE, or MJPEG. This is done via eufy-security-ws, Eufy Security integration, and I guess it's handled via go2rtc thereafter and then displayed via the HA card with WebRTC after that. I see in go2rtc that there are HTTP links/streams specifying different modes, but I haven't figured out how to consume anything RSTP. It wouldn't be of value to me in that way anyway, since the cameras need a trigger in order to be enabled since they're solar powered. RTSP inherently implies constant on, which these cameras are not, due to power restrictions.

[blockiindahood]

Any updates on this?

[fuatakgun]

@AlexxIT can you please a new version of go2rtc so it will include your latest fixes?

I can also help if it requires some work, greatly appreciated

[AlexxIT]

I'll try release today. Planned to collect more changes. But I may split them into several releases.

[AlexxIT]

https://github.com/AlexxIT/go2rtc/releases/tag/v1.9.8