Node-RED requires enough technical knowledge that it becomes not easier, but harder than writing JS code when things go medium size. N8N is superior in UX.

Also although I greatly appreciate everyone’s efforts, I don’t want to rely on community plugins that require maintenance and may or may not abandoned after it’s developer loses interest/move on with their life. TBH NPM is brimming with those.

Yeah, businesses went big in N8N but home users are somehow unaware of it. It even has Home Assistant integration.

Have you tried beaver docking? I really like it. I just learned of it recently and do it everyday. Better than a lot of other docking.

Firefly

Nope. I found AB and saw that they had experimental support for SimpleFIN, which supports financial institutions in my country (USA), and it was cheaper than my old, non-selfhosted solution (Tiller). SimpleFIN provides a pretty simple API, so there’s no reason Firefly couldn’t support it as well (and there’s an issue for it).

I also really hate PHP, so the fact that Actual Budget is written in node.js is a plus.

How would the timed tasks be handled if they’re offline

It probably would work well with those as long as the startup time was quick (my containers come up almost instantly) and the initiating clients can handle a bit of latency. I didn’t notice any hiccups in my use at all.

I used Traccar before switching to FMD. It used a lot of battery for somewhat inaccurate results in my case (might be phone related).

You need to install the client from F-Droid and it periodically polls your device for its location.

the only change I had to make was to add the config file to the volumes list:

services:
  fmd-server:
    image: registry.gitlab.com/nulide/findmydeviceserver:v0.7.0
    container_name: fmd-server
    volumes:
      - data:/data
      - ./fmd/data:/fmd/db/
      - ./fmd/config/config.yml:/fmd/config.yml:ro
    restart: unless-stopped
    networks:
      - fmd_server
#    ports:
#      - 8080:8080

# legacy
volumes:
  data:

networks:
  fmd_server: