Hello, I’ve pushed the migration to the 1.8.2 version.
Fell free to update and discuss any encountered issue ! (Looking at you @Chaoscontrol 
)
The github action have been updated to follow major version as well
Cheers
1 Like
Amazing, thanks!
I just risked it and updated it and so far it seems good. At least I could access fine without doing anything special.
It detected my subdomain as dangerous, which is something that happened during the original set up. But this might be more of a me issue as I have a reverse proxy to access etc. Will have to dust off and debug again.
Aside from that, I will report in a couple days as all my automations run at 00:00h once a day. But looks promising.
Questions: didn’t their migration guide say MariaDB was deprecated? I use MariaDB in HA as my db and was worried I’d have to change to PostgreSQL.
I also noticed the WEBHOOK_TUNNEL_URL being removed, but I am still using it in my config for some Google auth. Do you know if it will still work?
Many thanks!
Hey,
thank you for taking a look.
Yes the cert error is tied to your reverse proxy settings.
How the automation went ?
About your question, the database deprecation is about n8n itself. Let me explain a bit. the n8n lives in a Docker container and do not connect to external database. In other cases than home assistant, you would like to connect it to an external database like mysql / postgres or whatever.
But in our case, we are using the default settings which is a sqlite database. Sqlite is a database as a file living inside the container. So it does not refer to your Home assistant database directly
About the WEBHOOK_TUNNEL_URL, they seems to have changed the way to expose your webhook, with a new command line start (not env var). Taking that change into account, I’ve added the cmd_line_args to the addon config. You should be able to set start --tunnel as commandline args. It haven’t been tested yet* so please feel free to try it 
Thanks
Great stuff, thanks for the explanation. Makes sense, the db thing was what worried me the most. Good it wasn’t that impactful on HA.
I’m terrified of CLI, so really can’t test much for you. I’ve noticed the setting I had has changed into an env_vars_list, and it has been retained.
Log says: exported WEBHOOK_URL=http://localhost:5678
Automations have worked just fine. So apparently nothing broke.
However, I went to double check into the Google OAuth I have set up, and while it seem ok (it shows the Redirect URL as the one in the webhook, which I think it’s what’s supposed to do), I wanted to force check and clicked reconnect again. And this happened:
So now I guess something should be fixed but I’m not sure what. Any idea?
Is there an HACS integration for n8n that would allow communication with the API from Home Assistant?
2 Likes
I keep getting this error when I tried to update n8n addon from 1.0.29. Why is that? I get this message when trying to update to any version after 1.0.29.
2024-04-25 19:44:40.847 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 3cfc8f0f_hass-n8n
2024-04-25 19:44:47.793 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 3cfc8f0f_hass-n8n
2024-04-25 19:44:47.793 INFO (MainThread) [supervisor.backups.manager] Backup 1e552ca2 starting stage finishing_file
2024-04-25 19:44:47.796 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 1e552ca2 completed
2024-04-25 19:44:47.796 INFO (MainThread) [supervisor.docker.addon] Updating image 3cfc8f0f/amd64-addon-hass-n8n:1.0.29 to 3cfc8f0f/amd64-addon-hass-n8n:1.0.34
2024-04-25 19:44:48.943 INFO (MainThread) [supervisor.docker.addon] Starting build for 3cfc8f0f/amd64-addon-hass-n8n:1.0.34
2024-04-25 19:44:49.630 INFO (MainThread) [supervisor.api.middleware.security] /network/interface/default/info access from ccab4aaf_frigate-fa
2024-04-25 19:44:55.590 ERROR (MainThread) [supervisor.docker.addon] Can't build 3cfc8f0f/amd64-addon-hass-n8n:1.0.34: Get "https://docker.n8n.io/v2/": remote error: tls: internal error
2024-04-25 19:44:55.590 ERROR (MainThread) [supervisor.docker.addon] Build log:
Step 1/14 : ARG N8N_VERSION=1.36.4
Step 2/14 : FROM docker.n8n.io/n8nio/n8n:${N8N_VERSION}
2024-04-25 19:44:56.103 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/beta.json
Hello,
It does not seems to be related with the plugin itself. I’am able to pull the n8n docker image without any issue :
$ docker pull docker.n8n.io/n8nio/n8n:1.36.4
1.36.4: Pulling from n8nio/n8n
bca4290a9639: Already exists
31e174fedd23: Pull complete
df998480d81d: Download complete
e6f4e57cc59e: Download complete
d9aa7efe069e: Download complete
89368adbe7af: Download complete
4f4fb700ef54: Download complete
f957c89b510f: Waiting
dc562193ebf3: Waiting
aa6eeff09f88: Waiting
The error in your logs (Get "https://docker.n8n.io/v2/": remote error: tls: internal error) is probably due to a networking issue (VPN, Firewalls …)
I just discovered this addon, nice work! I’m currently running n8n in a Docker container but got stuck, so I thought I’d reach out here for some advice.
I’m trying to use the todo.get_items service and need to figure out how to process the response in n8n. Has anyone managed to do this, or does anyone have any tips on how I might proceed?