Did you read post #2 specifically the jobs.json file?
1 Like
I did not, just scanned this entire thread. Thanks for the tip, I will check it out and see if I can figure it out!
Well, I added the jobs.json file in said location and restarted Home assistant server from within home assistant. But i still can not update to the newer version of Home assistant Core (2021.1.5)
Do I need to restart the entire package inside synology DSM?
The configuration is validated as “valid”.
Yes stop and restart the package in DSM. Check your logs too under supervisor in the system tab
Restarting HA will not help, you need to restart Supervisor.
Good evening,
I’ve been searching through this page but can’t seem to find the solution to why my container doesn’t want to start.
I get a error message when starting the “homeassistant” container:
Start container homeassistant failed: {“message”:“Bind mount failed: ‘/dev/input/by-id’ does not exists”}.
From what I understand this has to do with finding an USB z-wave device.
Since I don’t need this I was wondering if this can be ignored somewhere to continue starting the container?
Kind regards,
Sander
Hi @fredrike,
I migrated my HA from a Raspberry Pi to my DS718+ last week, I had to create some folders in relation to usb serial devices in order for HA to start(@Sander_Somers mentions one of them in the previous post, creating that folder fixes that issue to then show you what folder to create next) But all in all it went great and it runs way better then on the Raspberry Pi.
Today I installed synology’s Virtual Machine Manager, and since then my HA seems to have unexplained networking issues. I cannot Load the Hassio Page, HA can’t connect to MQTT entities, Zigbee2Mqtt frontend doesn’t load. etc.
Naturally I removed the Virtual Machine Manager, that didn’t fix it.
Then I restarted DSM, didn’t fix it
As it looks like a networking issue I tried the Networking fix from post 2, that didn’t fix it,
Then I reinstalled Docker and HA, that didn’t fix it.
I retried the networking fix, still no fix.
I also tried the Unable to load the panel source: /api/hassio/app/entrypoint.js fix, but the container restarts before I can Clear it.
For now i’m back to the Raspberry Pi, but really want to run it on my DS
Now i don’t know where to look next. Any suggestions?
regards,
Jeroen
Did you uninstall the package. Remove all docker containers and try again?
@gkron, yes I did several times:
The first part of the log right after a clean install:
2021-02-02 23:36:50 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2021-02-02 23:36:56 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request
2021-02-02 23:36:56 WARNING (MainThread) [homeassistant.components.hassio] Not connected with Hass.io / system too busy!
2021-02-02 23:37:06 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/options request
2021-02-02 23:37:16 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/options request
2021-02-02 23:37:26 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request
2021-02-02 23:37:26 WARNING (MainThread) [homeassistant.components.hassio] Can’t read last version:
2021-02-02 23:37:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /ingress/panels request
2021-02-02 23:37:36 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can’t read panel info:
2021-02-02 23:37:41 ERROR (MainThread) [homeassistant.components.updater] Error requesting Home Assistant update data: Cannot connect to host updater.home-assistant.io:443 ssl:default [Try again]
2021-02-02 23:37:42 ERROR (MainThread) [metno] https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:default [Try again]
2021-02-02 23:37:42 ERROR (MainThread) [aiohttp.server] Error handling request
报告此错误。。。。。。@ fredrike
http + docker：//localhost/v1.39/containers/3a36993b8b23d252725af24edaaa1d8f3a1d7cf5f56facb9e69c224ca82e31c1/start的500服务器错误：内部服务器错误（“ OCI运行时创建失败：container_linux.go：345：启动容器进程导致“ exec：” / dev / init ”：stat / dev / init：没有这样的文件或目录”：未知”）
1 Like
Hi ! I would like to ask some news about HASS.IO and DSM7. Is there atm a way to get HASS.IO working on DSM7 ? Thank you 
1 Like
New problems, now it is ESPHome addon v 1.16.0
after update addon doesnot starting
400 Client Error for http+docker://localhost/v1.39/containers/154fbd5c9ad0509d29acd51383e084b24e29db090fdd2abdfea87462f95fff8c/start: Bad Request ("OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown")
ha integration is working for now but what is easiest a way to downgrade version?
PS restoring by snapshot esphome addon didnt help - same error with old version
Nope. Not at this point.
But then again. DSM 7 is still not out… Maybe by the time DSM 7 is released there will be some news.
1 Like
Is there any specific reason you think this is related to the package? I have updated, I’m using it and I have no issues with ESPHome v1.16.0
I have almost the same issue with the MQTT broker add-on since a few days, but as a server error. Tried everything from reinstalling, downgrading and restoring old snapshots. Without any luck so far. I think the error sits somewhere in docker but lacking the knowledge to fix it. As soon as I start it this message appears;
500 Server Error for http+docker://localhost/v1.39/containers/1507ae0890350d1504041a9a0ce08f40523541255644566cab5e152105541893/start: Internal Server Error (“OCI runtime create failed: container_linux.go:345: starting container process caused “exec: "/dev/init": stat /dev/init: no such file or directory”: unknown”)
@rule you might fix this by just creating the folder /dev/init on your diskstation. (can be done trough SSH with root permissions)
Anyone already did the last upgrade to version 2012.2.0? This python upgrade is safe for our Synologys? 
Thanks Jeroen! This might have brought me a step closer to the solution. After creating the /dev/init directory the error changed to the 400 Client error as fufar described. Also after giving the folder 777 rights. When rebooting the Synology (DS220+) the created /dev/init directory has disappeared.
400 Client Error for http+docker://localhost/v1.39/containers/f5cb95b480f7391d64515a3969f310cd0bfeebcf8ca9b237213742426e31f3e0/start: Bad Request (“OCI runtime create failed: container_linux.go:345: starting container process caused “exec: "/dev/init": permission denied”: unknown”)
SO far working great…
1 Like
Thanks! Will try to update! Fingers crossed
1 Like