Google assistant integration breaks HASS?

Configuration
1

I added the following in my configuration.yaml to integrate google assistant. Kept getting service_account errors. I changed the filename for the google JSON file, and at that point HASS went dead until I commented the service_account line out. I also added duckdns for ssl (not sure if that contributed to dead HASS?), which I think google requires? I got the service_account from google itself…
Anybody got any ideas? Should I post this in a google assistant thread?

#http:
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem
    
    # Example configuration.yaml entry
#google_assistant:
 # project_id: home-assistant-1e2d5
#  service_account: !include google.JSON
#  report_state: true
#  exposed_domains:
#    - climate
#    - switch
#  entity_config:
#    light.office_switch_2_cans:
#      name: office
#      aliases:
#        - oklahoma
2

I think you should read this and post again. How to help us help you - or How to ask a good question

3

Ah, figured that out, thank you. Code is now proper. I installed classic Hassos image. When I remove comments, I don’t get safe mode, I can’t get into Hassos at all…
It’s the google.json file. I changed the long string service_account filename to that…maybe it hates the simple name?