Closed avol-io closed 3 years ago
Default config will not start currently - there are mising wheels for cloud and mobile_app integrations, so you must disable in your configuration.yaml default_config:
and manually add all except cloud and mobile_app:
#default_config:
# all integrations from default_config:
#cloud:
config:
frontend:
history:
input_boolean:
input_datetime:
input_number:
input_select:
input_text:
logbook:
map:
#mobile_app:
person:
ssdp:
sun:
system_health:
updater:
zeroconf:
zone:
works thanks
IMO this should be left opened - issue should be fixed in package. My answer was just a workaround.
you are right
May you please detail from where does this "default config" comes from?
After fresh install and initial run - if there will be no manually created configuration.yml, then it will be created automatically with this default_config:
line (and also with some more defaults, like automations or scripts files)
OK thanks... As I have understand two different DSM install, I missed that point for initial setup.
I don't really get how to resolve the issue on my side. I have freshly installed and am also stuck in same issue atm.
My config currently looks like this.
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
In the logs I found following:
Setup failed for cloud: Requirements for cloud not found: ['hass-nabucasa==0.35.0'].
Setup timed out for stage 2 - moving forward
What do I need to do specifically to make it work?
You need to change default_config:
to:
https://github.com/SynoCommunity/spksrc/issues/4182#issuecomment-693302307
Unfortunately that doesn't resolve the issue. Config looks like this.
# Configure a default setup of Home Assistant (frontend, api, etc)
#default_config:
# all integrations from default_config:
#cloud:
config:
frontend:
history:
input_boolean:
input_datetime:
input_number:
input_select:
input_text:
logbook:
map:
#mobile_app:
person:
ssdp:
sun:
system_health:
updater:
zeroconf:
zone:
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
Is the indentation correct in above comment?
Config is OK now - what is now written in log?
tried couple of restarts, but no new logs coming in when tailing the log.
If nothing is logging, then something else is happening, try looking in syslogs
Before I was restarting via the web interface of Home Assistant. Now I stopped via the synology package and started it again I got some logs, all INFO logs in this case.
It seems all is working now.
So the restart functionality in admin panel of Home Assistant doesn't seem to work on synology package. Is that something we could resolve? I could file a new issue for that.
restrat functionality from frontennd is working - but first full initiall run must be done. Just wait now
Could I make a friendly enquiry about any plans to include the missing wheels for cloud and mobile_app integrations? I have a DS218 and would love to use the mobile_app integration in particular. I suspect that the mobile_app integration would be a key one for many people. Would the required wheels be included in an update of the SynoCommunity Python3 package, or the HomeAssistant package?
@alistairwitt would love to have the mobile_app integration working on my DS413 as well.
fixed with Home Assistant Core 0.114.2-9
Setup
Package Name: Home assistant Package Version: 0.114.2-7
NAS Model: dj218j NAS Architecture: Armada38x
Expected behavior
Application run correctly
Actual behavior
After #4171 the application start but when i complete the access to dashboard it give me this message: "Home Assistant is starting, not everything will be available until it is finished." and notthing happen.
Package log
cat /var/packages/homeassistant/target/var/homeassistant.log
Other logs
End of
/var/log/synopkg.log
_