The strange thing is these cameras all used to work in Cockpit.
Another strange happening is Video Manager stating “It looks like there’s no video stream accessible from your device’s detected IP address (192.168.1.90).” We don’t use the IP address. Perhaps it was entered inadvertently? We can’t find where it may have been entered. Any ideas?
Hi @grantdutoit -
Updating to the latest Cockpit is strongly recommended!
Can you share more information on what IP camera you’re using? Are they providing an H264 stream? It may be challenging to get that many working at once…
Hi @tony-white
The cameras are from security cameras and re-housed. They are ONVIF compliant. They worked before. Yes, they provide H264. Either way, none of them work in Cockpit whether one or all. I stand under correction but I believe we had them all working at one point. Didn’t run them for some time and with time you guys have improved things with many releases since. The same config doesn’t work anymore.
Can you check in BlueOS’s ethernet menu (two computers on the right top corner) if you have an static IP set to 192.168.1.90? If so, and it was not intended, you can delete it.
I found the IP on the top-side computer. Do you have any idea why it is looking for video streams on the top-side? Shouldn’t it be looking/obtaining the IP for the RPi?
My mistake on that one. The message is actually clear, I got it wrong. It’s just saying that from your top-side computer (192.168.1.90), which is where the BlueOS frontend is running, there are no streams accessible. That’s why you are not receiving them on Cockpit.
As this is on the BlueOS/MCM side, I will transfer the issue to that forum and let @joaoantoniocardoso help you as this is his field.
The most probable source of problem would be the list of Allowed WebRTC remote IP Address. The IP there should be your tether IP address (eth0, which is 192.168.1.44 on your screenshot from BlueOS).
We have to do a fresh install as the system appears to be corrupted. Can no longer connect to BlueOS at all after having electrical supply problems. I’ll not be able to provide what you have requested. Once complete with fresh install, we’ll see if the problem still exists and get back to you. Thank you.
Hi @grantdutoit -
What kind of electrical supply problems? Does the 5v UBEC still provide 5V when checked with a multimeter? Plugging in a HDMI monitor to the Pi via an adapter is a great way to understand why a system may be failing to boot…
Hi,
sorry if I join this conversation but I have a similar problem.
I’m trying to view an external RTSP IP camera inside cockpit but I’m not able to redirect the streaming in the BlueOS configuration.
I’ve tried both the latest BlueOS Master and Beta but none of them are working. Of course I can view the streaming in VLC.
Hi @EnricoT -
Yes, unfortunately you’ve missed that BlueOS does not support mpeg4 video streams - only h264 encoding! If your cameras have such a stream available, things should work, otherwise I’m afraid the behavior you’re seeing is expected…
Hi @tony-white ,
thanks for your help. Actually the camera I am using is set to h264, this is why I am still confused.
Anyway, I’ve managed it to work for now with the camera low quality sub-stream.
I’ll try to find another camera which is more compatible.
Do you know if there are plans to upgrade the streaming options?
Hi @EnricoT -
There is indeed some experimentation with other video streaming software options, but a lot of the limitations come from Chrome/Electron itself, in the case of Cockpit…
Checkout @williangalvani 's latest extension, a packaging of MediaMTX for BlueOS!
It’s my turn to apologise for the late reply. We got a new RPI4 and MicroSD just to rule out hardware problems and did a fresh install. We’re not running the latest versions, so we opted to stick with a known set of versions that worked at the time. We’re creating an extension and needed to create a “stable” platform.
Since it’s a fresh install and start, I’m hoping you can direct us to get it right. If there are resources online, please direct me to those as I search but couldn’t any that helped. Thank you!
Hi @grantdutoit, could you post your video streams configurations? (feel free to redact authentications if you need to).
I see that you are aiming for 1.3.1, but If you are using redirect streams, I recommend you give a chance for the current 1.4.0-beta.20, which among many things, improves the redirect streams and feedback about stream problems. This beta is the stable release candidate, to be released within a week if no major problems are found.
I seem to have solved the problem. It appears the main cause was incompatibility with our last known working configs and the more current release of BlueOS. We had remained with a set of versions that we found to be stable as we were developing an extension. In addition, we had other problems that led to a fresh install using BlueOS v1.3.1. This was shortly followed by an upgrade to BlueOS v1.4.0-beta.20. We did a fresh configuration in Video Streams:
The PTZ requires a user and password. The previous password had an ! mark that required converting to “%21”. This worked in earlier versions however it appeared in later versions it no longer worked. We changed it to a simpler password and it worked.
For others to reference, this is the version matrix on which the problem was resolved. We’ll now update these to the latest.
