I think plex is the only one. Do you have another instance of plex running?
Yes its there also saw the path in the package details.
How can I make this shared to I can access this path on a Windows PC?
Tried to create a softlink and adding a folder that didnt work
Hi,
I’m not sure, i’ve even tried moving it to another synology NAS I have and I’m getting the same issue. I did a a recursive search for 1900 and the following came up:
/volume1/docker/hass.io/addons/git/a0d7b954/plex/config.json: “1900/udp”: 1900,
/volume1/docker/hass.io/addons/git/a0d7b954/plex/config.json: “1900/udp”: “Plex DLNA Server”,
/volume1/docker/hass.io/addons/git/a0d7b954/unifi/config.json: “1900/udp”: null,
/volume1/docker/hass.io/addons/git/a0d7b954/unifi/config.json: “1900/udp”: “L2 discoverable port”,
/volume1/docker/hass.io/addons.json: “1900/udp”: 1900,
/volume1/docker/hass.io/addons.json: “1900/udp”: “Plex DLNA Server”,
I’m on Discord and have subscribed as a Patron if you wouldn’t mind popping on?
Thanks.
You were almost right.
ln - s /volume1/hass.io /volume1/<share name>/hass.io
But I highly recommend that you set your datapath to a subfolder of a share instead.
What do you recommend?
No Linux experience here
Used the samba add-on to make it work
But because I still have the other HA running it created a new shared folder under NULL
\NULL\config
Will start testing today.
Tnx for your help @fredrike
I couldn’t find you on discord, but ask in the hassio channel of homeassistant.
I’m in there now pal, didn’t realise that was the channel to be in
It is recommended to fill in a correct share in this dialog during installation.
No Linux experience required, but it is a good thing to read instructions. (Should the Please fill the desired storage location for the data directory below. be reworded (or perhaps in red)?)
True, but i think it is a synology thing. Couldnt find that folder in the file manager, so i could make it shared.
In Control Panel → Shared folder you I have this.
That means /volume1/Server
and is where I store all my server settings (eg. I store hass.io config in /volume1/Server/hass.io
).
Would a dialog like this be clearer (it does however not fit my use-case where I already have a Shared folder I like to use)?
I’m not really an expert on how to build installation dialogs but I think the best would be to let the user select a share to use for hass.io data (if anyone seen a package that allows this it would be great to share that so I can copy that code for the hass.io package).
I have these folders available, probably the other one is hidden.
But cant make it visible.
Will try to reinstall hassio and pick the docker folder as base.
Create a share instead.
Reinstalled it under a shared map and all folders are directly available
Will add some integrations and add ons and see if all runs stable
hello @fredrike
first issue encountered though not completely related to hassio installtion.
so my ssl setup is working fine on synology hassio installtion and i’m able to access it externally.
https://xxxxxxx.duckdns.org:9123
however media_extracter.play_media call giving ssl handshake error like below when i try to access a media file to play from dev_service panel
{
"entity_id" : "media_player.office",
"media_content_type" : "music",
"media_content_id" : "https://xxxx.duckdns.org:9123/local/door_chime.mp3"
}
2019-07-07 13:41:23 WARNING (SyncWorker_8) [homeassistant.components.media_extractor] Could not send HEAD request to https://xxxxxx.duckdns.org:9123/local/door_chime.mp3: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)>
2019-07-07 13:41:23 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:1056)
2019-07-07 13:41:23 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:1056)
2019-07-07 13:41:23 ERROR (SyncWorker_8) [homeassistant.components.media_extractor] ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)> (caused by URLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)')))
2019-07-07 13:41:23 ERROR (SyncWorker_8) [homeassistant.components.media_extractor] Could not retrieve data for the URL: https://xxxxxx.duckdns.org:9123/local/door_chime.mp3
if i try to access the mp3 directly in browser it’s running without any error.
just to re-iterate all SSL setup is working for all other url calls on my hassio setup and i see valid certificate info in browser as below. my tts is working and all other internet calls on ssl/tls are working.
any idea what’s the problem and possible solution?
ok, solved the problem. issue was with the in-build certificate tool in synology since it wasn’t creating any fullchain.pem file. when i delete the one created by synology and install the duckdns addon from community addon store all is sorted now.
Whoa, dude, you’re a legend. Gonna have to give this a go on the weekend. Didn’t know this was being worked on
I ordered a Pi 4 to move to so I could get the add on store back. But now I may just stick with the Synology, and maybe use the Pi for image processing or something
The add-on zigbee2mqtt doesn’t work at my synology. Installing is not a problem, but he doesn’t start the addon. No logging available.
Check with the developer of the addon perhaps there are some tweaks needed.
I would be happy to take over your pie.