Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On 1.9.5 tapo cams stucks in loading #1415

Closed
xitters opened this issue Oct 29, 2024 · 16 comments
Closed

On 1.9.5 tapo cams stucks in loading #1415

xitters opened this issue Oct 29, 2024 · 16 comments
Labels
duplicate This issue or pull request already exists

Comments

@xitters
Copy link

xitters commented Oct 29, 2024

Whit this configuration my cams dont show image, stuck on loading

type: custom:webrtc-camera
url: rtsp://albin****:MA***[email protected]:554/stream1
poster: https://home-assistant.io/images/cast/splash.png

on 1.9.4 works perfectly, why?

@GeorgeCastanza
Copy link

All my Unifi cams too. I rolled back and its working again.

@rinners
Copy link

rinners commented Oct 29, 2024

All my Unifi cams too. I rolled back and its working again.

Same here

@blanknam3d
Copy link

blanknam3d commented Oct 29, 2024

I figured it out: if you are using the WebRTC Home Assistant card, it seems the API now expects to be told the name of a stream present in the go2rtc config, rather than being able to accept a given RTSP link for either src or url.

Not sure why it needs to be that way to work now, but that seems to be how it now works. ex:

type: custom:webrtc-camera
ui: true
poster: http://192.168.X.XXX:1984/api/frame.jpeg?src=kitchen
streams:
  - url: ""
    name: PLAY
  - url: kitchen
    name: HD
    mode: webrtc,webrtc/tcp,onvif
    media: video,audio
    

As opposed to kitchen being something like rtsp://skyna:[email protected]. Suspect it's related to this: #1407

Add your Tapo camera streams to your go2rtc config, then just put the names of the streams into the card config rather than the RTSP or Tapo URLs.

@pajikcz
Copy link

pajikcz commented Oct 29, 2024

My ZOSI Cams and ICSEE cams stopped working with latest release, will rollback

@Glideh
Copy link

Glideh commented Oct 29, 2024

Same thing with my Android IP cams, were working in 1.9.4 but not in 1.9.5
image
Dashboard card config:

type: custom:webrtc-camera
url: http://192.168.x.y:8080/video
#...

I'm also getting these errors on the browser console (one for each cam):
image

Weird thing is we can see the source as video-rtc.js?v=1.9.4:253 but I'm using gotortc:1.9.5

Rolling back to 1.9.4 for now.

@steuerlexi
Copy link

Same thing with my Android IP cams, were working in 1.9.4 but not in 1.9.5 image Dashboard card config:

type: custom:webrtc-camera
url: http://192.168.x.y:8080/video
#...

I'm also getting these errors on the browser console (one for each cam): image

Weird thing is we can see the source as video-rtc.js?v=1.9.4:253 but I'm using gotortc:1.9.5

Rolling back to 1.9.4 for now.

How to roll back to 1.9.4 ? I can only choose 1.9.5 out of the addon store

@pajikcz
Copy link

pajikcz commented Oct 29, 2024

to rollback go to Setting/System/Backup where u can find all backups.
/hassio/backups

@Glideh
Copy link

Glideh commented Oct 29, 2024

Doesn't seem to be an easy way to rollback an addon. I personally use Docker so it's really simple.
You can still restore a backup if you have nothing else to loose as @pajikcz said.

@pajikcz
Copy link

pajikcz commented Oct 29, 2024

in Backups there are also ADDONS backups of previous versions

@arakasi55
Copy link

Same issue for me too, all cards just show loading. Rollback to 1.9.4 fixes things.

@blanknam3d
Copy link

Same thing with my Android IP cams, were working in 1.9.4 but not in 1.9.5 image Dashboard card config:

type: custom:webrtc-camera
url: http://192.168.x.y:8080/video
#...

I'm also getting these errors on the browser console (one for each cam): image

Weird thing is we can see the source as video-rtc.js?v=1.9.4:253 but I'm using gotortc:1.9.5

Rolling back to 1.9.4 for now.

While on 1.9.5, did you try visiting your.go2.rtc.addr:1984/api/frame.jpeg?src=http://192.168.x.y:8080/video in a browser to see what it did? On 1.9.5 myself, doing so would make it just respond "stream not found", unless I defined the stream in the yaml & told it the name of the stream as defined in the config instead.

I think I'm pretty certain what's breaking here - seems that in 1.9.5 it's now strictly expecting a stream name with info as defined in go2rtc.yaml, and will not accept just being given an RTSP link or whatever else, ex. instead of putting http://192.168.x.y:8080/video as the URL in the lovelace card, you'd instead put a name like "foyer", and have lines like the following in your go2rtc.yaml defining your streams:

streams:
  foyer: http://192.168.x.y:8080/video
  livingroom: rtsp://securecamera:[email protected]/live
  frontporch: tapo://[email protected]
  ...

And of course, ex. in the lovelace card:

type: custom:webrtc-camera
ui: true
poster: http://your.go2.rtc.addr:1984/api/frame.jpeg?src=foyer
streams:
  - url: ""
    name: PLAY
  - url: foyer
    name: HD
    mode: webrtc,webrtc/tcp,onvif
    media: video,audio

@AlexxIT AlexxIT added the duplicate This issue or pull request already exists label Oct 29, 2024
@AlexxIT
Copy link
Owner

AlexxIT commented Oct 29, 2024

#1417

@AlexxIT AlexxIT closed this as completed Oct 29, 2024
@AlexxIT
Copy link
Owner

AlexxIT commented Oct 29, 2024

You can check master version (available via addon/docker). If there are no problems in it, I'll make a release.

@xitters
Copy link
Author

xitters commented Oct 29, 2024

You can check master version (available via addon/docker). If there are no problems in it, I'll make a release.

Works perfectly master version for me

@AlexxIT
Copy link
Owner

AlexxIT commented Oct 29, 2024

@Glideh
Copy link

Glideh commented Oct 29, 2024

Works fine thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

9 participants