Alexbelgium repo : 90+ addons

alexbelgium · February 2, 2022, 6:15pm

thanks for the info! I’ll have a look

poudenes · February 2, 2022, 8:23pm

It didn’t work. The path is:

/config/addons_config/fireflyiii_data_importer/configurations

ANd I added this also, restart the add-on but no pulldown…
in the configuration folder I have add the 2 json files I use for the import

* Store the files in `storage/configurations`
* Mount a local directory to the `/var/www/html/storage/configurations` directory in Docker.
* Change the `JSON_CONFIGURATION_DIR` to any custom directory (mount it if you want to), and place them there.

Is the earth for the JSON_CONFIGURATION_DIR link to /var/www/html/storage/configurations?

EDIT:

Using config file found in /config/addons_config/fireflyiii_data_importer/config.yaml
Config file is a valid yaml

config.yaml:
JSON_CONFIGURATION_DIR=config/addons_config/fireflyiii_data_importer/configurations

alexbelgium · February 3, 2022, 3:31am

Have you tried JSON_CONFIGURATION_DIR: config/addons_config/fireflyiii_data_importer/configurations?

My yaml interpreter looks at “:” symbols to export the env variables. Strange I didn’t think a = value was accepted by yaml I’ll have to modify the script

Mappings
Mapping gives you the ability to list keys with values. This is useful in cases where you are assigning a name or a property to a specific element.

animal: pets
YAML Syntax | Grav Documentation

poudenes · February 3, 2022, 7:53am

Solved it: (Fireflyiii Data Importer)

JSON_CONFIGURATION_DIR: /config/addons_config/fireflyiii_data_importer/configurations

This is the correct path.

Inside the configurations you add the json files for each bank you want to use it.
Restart Add-On and you’re done!

alexbelgium · February 3, 2022, 9:37am

Thanks for sharing!

alexbelgium · February 5, 2022, 6:22pm

Hi, I’ve added a new automatic upload of the configurations files if they are stored in /config/addons_config/fireflyiii_data_importer/configurations (or whatever path you set in the addon config + /configurations at the end)

Btw, there seems to be another way of auto-import : https://github.com/alexbelgium/hassio-addons/issues/203

poudenes · February 5, 2022, 8:59pm

I think that is a method to import CSV files from you bank.

SolidRhino · February 6, 2022, 3:47pm

Can you please add Plex-Meta-Manager? It is supported bij linuxserver: linuxserver/plex-meta-manager - LinuxServer.io

Thank you

alexbelgium · February 6, 2022, 5:12pm

Hi I don’t have much time now but I’ve created a request on github to keep track of it here https://github.com/alexbelgium/hassio-addons/issues/206

As it is based on linuxserver it should be rather easy to adapt

SolidRhino · February 6, 2022, 6:58pm

Thank you

alexbelgium · February 7, 2022, 8:59am

Hello, v1.0 is pushed. Please let me know how it goes ! At first run, a config.yml will be created. You’ll then need to customize the file in /config/addons_config/plex-meta-manager/config.yml according to the infos on the site, then restart. And then hopefully it should work

poudenes · February 7, 2022, 11:25am

You will.become the Addon master sooner or later! You’re githhb has so many Addons at the moment

alexbelgium · February 7, 2022, 11:38am

Ahah, thanks! But there will be a moment where I won’t be able to continue adding addons or it will take too long supporting them all… But as long as its good I continue

hulkhaugen · February 22, 2022, 10:32pm

Unable to update the latest Transmission, get this in config:

22-02-22 23:29:11 INFO (SyncWorker_4) [supervisor.docker.interface] Updating image db21ed7f/amd64-addon-transmission_ls:3.00-r2-ls109 to db21ed7f/amd64-addon-transmission_ls:3.00-r5-ls112
22-02-22 23:29:11 INFO (SyncWorker_4) [supervisor.docker.addon] Starting build for db21ed7f/amd64-addon-transmission_ls:3.00-r5-ls112
22-02-22 23:29:13 ERROR (SyncWorker_4) [supervisor.docker.addon] Can't build db21ed7f/amd64-addon-transmission_ls:3.00-r5-ls112: The command '/bin/sh -c sed -i "s|config|config/transmission|g" /etc/services.d/transmission/run     && sed -i 's/bash/bashio/g' /etc/cont-init.d/10-adduser     && sed -i 's/{PUID:-911}/(bashio::config "PUID")/g' /etc/cont-init.d/10-adduser     && sed -i 's/{PGID:-911}/(bashio::config "PGID")/g' /etc/cont-init.d/10-adduser     && ln -s /usr/share/transmission/web/style /transmission-web-control &&     ln -s /usr/share/transmission/web/images /transmission-web-control &&     ln -s /usr/share/transmission/web/javascript /transmission-web-control &&     ln -s /usr/share/transmission/web/index.html /transmission-web-control/index.original.html' returned a non-zero code: 1
22-02-22 23:29:13 ERROR (SyncWorker_4) [supervisor.docker.addon] Build log: 
Step 1/23 : ARG BUILD_FROM
Step 2/23 : ARG BUILD_VERSION
Step 3/23 : FROM ${BUILD_FROM}
 ---> 6c28d3c47712
Step 4/23 : RUN sed -i "s|config|config/transmission|g" /etc/services.d/transmission/run     && sed -i 's/bash/bashio/g' /etc/cont-init.d/10-adduser     && sed -i 's/{PUID:-911}/(bashio::config "PUID")/g' /etc/cont-init.d/10-adduser     && sed -i 's/{PGID:-911}/(bashio::config "PGID")/g' /etc/cont-init.d/10-adduser     && ln -s /usr/share/transmission/web/style /transmission-web-control &&     ln -s /usr/share/transmission/web/images /transmission-web-control &&     ln -s /usr/share/transmission/web/javascript /transmission-web-control &&     ln -s /usr/share/transmission/web/index.html /transmission-web-control/index.original.html
 ---> Running in d2ac2565673d
ln: failed to create symbolic link '/transmission-web-control/style': File exists

Removing intermediate container d2ac2565673d

Not gonna pretend i understand what’s going wrong here.

alexbelgium · February 23, 2022, 5:31am

Thanks, it’s actually easy : they merged in the upstream image a fix I had put in my on addon, so the code is now in duplicate I’ll publish a new version. Thanks!

vmartinv · February 27, 2022, 10:16pm

Thank you so much for the addons, it’s all I ever needed for my Home Assistant, you made the OS x10 more useful with your work.

nclapham · March 5, 2022, 8:47pm

Hi,
Portainer has been removed from the community add-on store, so I tried to install your portainer add-on today but it failed to start…

[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-aaa_dockerfile_backup.sh: executing... 
Executing script
[cont-init.d] 00-aaa_dockerfile_backup.sh: exited 22.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

Any ideas what the problem is?

alexbelgium · March 5, 2022, 8:56pm

Hi, mmh an invalid argument without error details. I’ve pushed a new version with debug mode turned on. Could you please update and copy paste the log here please? Thanks

nclapham · March 7, 2022, 11:35pm

Here you go:

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 30-nginx.sh: executing... 
[cont-init.d] 30-nginx.sh: exited 0.
[cont-init.d] portainer.sh: executing... 
[cont-init.d] portainer.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[23:32:18] INFO: Starting Portainer...
[services.d] done.
[23:32:18] INFO: Waiting for port 9000 to open...
[23:32:18] INFO: ... password set to default
[23:32:18] INFO: ... non-addon containers hidden
[23:32:18] INFO: ... portainer launched
INFO 2022/03/07 23:32:19 Encryption key file `portainer` not present
INFO 2022/03/07 23:32:19 Proceeding without encryption key
INFO 2022/03/07 23:32:19 Loading PortainerDB: portainer.db
level=info msg="2022/03/07 23:32:19 [INFO] [internal,ssl] [message: no cert files found, generating self signed ssl certificates]"
INFO 2022/03/07 23:32:19 Created admin user with the given password.
2022/03/07 23:32:19 server: Reverse tunnelling enabled
2022/03/07 23:32:19 server: Fingerprint 6f:b6:d9:19:bf:47:c2:6c:60:be:a0:0f:33:4c:57:d1
2022/03/07 23:32:19 server: Listening on 0.0.0.0:8000...
INFO 2022/03/07 23:32:19 [INFO] [cmd,main] Starting Portainer version 2.11.1
level=info msg="2022/03/07 23:32:19 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"
level=info msg="2022/03/07 23:32:19 [DEBUG] [internal,init] [message: start initialization monitor ]"
level=info msg="2022/03/07 23:32:19 [INFO] [http,server] [message: starting HTTPS server on port :9443]"
level=info msg="2022/03/07 23:32:19 [INFO] [http,server] [message: starting HTTP server on port 0.0.0.0:9000]"
[23:32:20] INFO: Starting NGinx...

EDIT:
I also now get this when I try to load portainer (port 9000) in browser:
ERR_SSL_PROTOCOL_ERROR

Whenever I do that, i get this showing in the logs:

[07/Mar/2022:23:33:05 +0000] 400 -(192.168.101.13) \x16\x03\x01\x02\x00\x01\x00\x01\xFC\x03\x03\x8F\x7Fn\xB9\xAE\xEFq\xDF\xDB>\x80\xFC\x88M\xF8\x88\xE7\x1D\xD3w\x18\xAB_\xC5\xF3\x839\x096=\x8F\xDB \xDF\x0B\xA8\x7F\xA5UT\xE93\xDB\x22z\x19\xEC\xB1BE\xF0\x88\x81\xC8+\x94\xFF\x92'\xCDm\x04\x90\x11\x0B\x00 \x1A\x1A\x13\x01\x13\x02\x13\x03\xC0+\xC0/\xC0,\xC00\xCC\xA9\xCC\xA8\xC0\x13\xC0\x14\x00\x9C\x00\x9D\x00/\x005\x01\x00\x01\x93\x9A\x9A\x00\x00\x00\x00\x00\x15\x00\x13\x00\x00\x10homeassistant-vm\x00\x17\x00\x00\xFF\x01\x00\x01\x00\x00 (-)

alexbelgium · March 8, 2022, 8:07am

Hi, I’ll need a few more infos. As I understand :

Initially you had an error message with “00-aaa_dockerfile_backup.sh: exited 22”, but now it starts correctly and you have the ERR_SSL_PROTOCOL_ERROR message ?
Have you just accepted the error message and seen if you can still connect ? If you are using a self signed ssl certificate (as described in the log), then the certificate won’t match your url and you will have such an error. However, you can safely accept it.
Have you tried to connect using Ingress instead of ip:port (by simply clicking open UI in HA) ?
If you confirm that 2) and 3) don’t work, could you please post your full log? You’re missing the banner and steps before (the execution of the “00-aaa_dockerfile_backup.sh”)

Thanks!

EDIT : the ssl certificate is only used to connect to the internal portainer container. However, you need to access it from an http address - http://homeassistant.local:9000 . This is what causes your error message, and the message in portainer log (replicated on my system)