I’m not using ipcamera binding because I have a separate pc running zoneminder. I have the streams working well in browsers and on sitemap from OpenHAB. I use ffmpeg on that pc for the CPU load from ffmpeg to not stress the RPi running OpenHAB. The issue I have is that my Chromecast starts streaming the provided m3u8 link but the image is as shown on first post and don’t know why.
LE:
I’ve tested the HLS stream from the IP Camera binding, with same results. No image in Chromecast. tested the stream in browser, VLC, sitemap…working
You missed my point. Does not matter how you produce the HLS, there are certain things you need to be aware of as the chromecast is far more fussy over the format than a web browser. The readme has things you need to check and they will also apply to streams created by zoneminder.
One example is there MUST be an audio track and AAC is the only format it can be in.
I misunderstood your point first, I will have a closer look on the special HLS format for Chromecast. Thanks for pointing me there. I will report back after I try them out.
I am not using the IP Camera binding because i dont want to raise the CPU usage with encoding on the RPi, i use FFMPEG running on my surveillance PC. I’ve come so far to stream but Chromecast is not showing the stream. Stream is viewable in browser, VLC, … but none in chromecast.
i’ve tested this settings on ffmpeg now with source direct from camera and not zoneminder:
I just tested my ChromeCast V3… It doesnt work either… I get the same result as you…
Yet another Google fuck up!
And to make things worse…
When I set up my camera to use MJEPG, and I cast my camera to my Home Hub, the picture is twisted 90 degree. When I cast the same camera with the same setting to my Chromecast V1 or my Lenovo Smart Display 10", then the picture is just fine…
I´m getting more and more tired of Google these days
EDIT - Just got streaming to work on my CC V3… Resolution 704x576 seems to work. (Still aac audio).
I think both the Home hub and the CC are very dependable on the resolution.
1920 x 1080 seems to work fine as well…
I use voice command on my Google Mini (or Smartphone Google Assistant) to stream the Camera to Chromecast
Bridge between OpenHAB and Google Home working with all other Items i synced. When i use the Command "Show on " i get the black image shown posted earlier every time.
Okay, thats odd. Cause that the only way I can use voice command. If I use voice command directly to my Home Hub (or Lenovo Smart Display) I get an error. But If I use voice command to my Home Mini, and tell it to show camera om my Home Hub, it works fine…
Did you try a direct PlayStream from openhab using the Chromecast binding? (I havn´t tried this yet, but I would assume it works).
I got that error on my V1 chromecast when I first tried it. I think this was due to some error in the ipcamera binding. I restarted the binding, and then streaming to the chromecast worked fine.
I think much of these problems are a mix of Google having issues, ffmpeg is having some smaller issues, and perhaps some “cache” settings in the binding in openhab… I´m not quite sure…
So maybe you´ll need to restart your binding/services.
Right now it seems my devices are running (1920 x 1080) when camera is set to h264. If I change the input stream to mjpeg, my Home Hub show the picture 90degree twisted. I have tried making som changes to the ffmpeg settings to change that, but it doesnt seem to do any difference.
However - Both my Lenovo and my Home Hub seems to having problems keeping up the stream in 1920 x 1080… That may be a cache/speed problem for the devices because I use an Rpi3B+… Just strange that my chromecats devices does not having this problem.
I really feel your pain - I have been struggling for days now.
I’m excluding the cache/binding issue because i’m streaming from a desktop PC running linux and not using Openhab or any binding to stream to chromecast…only the Item created in Openhab (running also an Rpi3B+) that makes the link between my Camera stream comming from the PC (running on i5 CPU with 8GB Ram) and Google Home.
I’ll guess its a Google problem but not 100% sure yet