Hi @nickrout, I am very sorry abour posting picures, I didn’t understand the protocol. It this one better?
@greengolfer, Thank you again, you are a real life safer. Please see below my configuration.yaml.
camera:
You are getting there. If you put three backticks before and afetr the code it will be even better and look like this:
- platform: generic
stream_source: rtsp://admin:[email protected]:554/0
still_image_url: http://admin:[email protected]/jpeg/view.html
verify_ssl: true
name: gds
On an english keyboard the backtick is usually at top left, below
By looking at the picture of the chrome debug window, I can see that the url used to access the stream is https://abadeeha.duckdns.org without the port.
What is configured for the base_url (or equivalent now) in your configuration.yaml?
Do you need :8123 to access lovelace interface?
If yes, then, there is something not correct somewhere 
In 0.117 base_url is deprecated and should be replaced by something like this:
homeassistant:
internal_url: http://192.168.0.30:8123
external_url: https://abcdefghijklmnopqrstuvwxyz.ui.nabu.casa
Hope this helps…
I didn’t have a URL statement in the config.yaml as I am using NGINX proxy manager. But I have now added
internal_url: http://192.168.1.5:8123
external_url: https://abadeeha.duckdns.org
It hasn’t made any difference to the message or results. Do you have any other suggestions?
I don’t. Sorry. My setup seems to be the same as yours and it works… So, I don’t know.
Not entirely…
The framerate is much lower than yours…
Using https shouldn’t make a difference though.
Thank you so much for your quick reply. I have changed my settings to be the same as yours. Still no improvement. I am woundering if it is to do with NGINX. I am thinking about trying to turn if off.
If anybody has any suggestions on how I can trace the cause of the issue, it would be much appreciated.
Kind Regards
Mark
Using chrome and the debug mode (F12).
Display your HA interface and do a reload. Go to the page where the camera stream should be displayed.
On the debug side, display the network tab.
Then, in all the request made you should have one called “camera.gds”. On the right panel, in Header you should see the URL that is build by HA to access the stream.
If you copy/paste that link, you should see the image…
OK.
And if you copy paste the link in the browser, no image as well?
Ì can see that you go through an nginx proxy, can you configure a direct http(s) access from HA to the GDS3710 without going through the proxy by using the IP address of the GDS in the configuration.yaml file?
And then, redoing the same test. That’s really the only clear difference between your setup and mine…
Correct, if I copy of paste the link in the brower I get no image as well.
I have turned off Nginx, and tried again. Very similiar results. Very strange.
Hi @Nath,
Did you find the reason for getting only constant Loading SIPPhone in browser developer tools, sometimes doordroid-card.js?v=0.0.1:198 Uncaught TypeError: Cannot read property 'offsetParent' of null .??
I am having similar problems.
Kind Regards
Mark
Yep. Weird… And the same stream in another card is working? Can you compare the url that are used to access the stream in both cases?
@greengolfer, I don’t know how to thank you for all your support. I really appreciate it.
I don’t know how to fund the URL of the picure entity card as it is using the entity: camera.gds, which is the same as Doordroid is using. It must be something to do with NGINX. Using f12 doesn’t show anything when the card is displaying.
Regards Mark
If you do the same debug with the lovelace view including the picture card and do a reload, you should see exactly the same thing. Otherwise, I am out of suggestions…
@greengolfer, Thank you again for this amazing project and your tireless helping my dumb questions. I nearly gave up, but decided to reformate my Freepbx and start again. This has helped signifcantly.
I can now call me Hassio from a tablet with the Grandstream app and audio works both ways. I can call the GDS3710 from the tablet and audio works both ways. Now the next problem, when the GDS3710 calls Hassio, it shows as ringing, but when I answer the call, I have no audio. I assume this is a codec mis match. Kind Regards Mark
Here is what I have on the GDS side:
And on freepbx:
On freepbx, it is in the Settings > Asterisk SIP Settings page.
@greengolfer, Thank you. Those settings match mine. Could you please show me your seeings for the GDS3710 Account> Account 1. Thank you.
