Partial functionning when deploying to Raspi 4 or 3B+ - INFLUX_TOKEN

Hello CC team,

I work at EPV (in France) with EnergyID (BE) on a new european project on domestic flexibility, and I met Matt through Rescoop last year. I just deployed HEMS2.0 (64bits) on a Raspberry4 and a RaspberryPi3B+ via the free BalenaCloud option, for testing, and something is odd:

• On first run, the web interface was failing with an error "INFLUX_TOKEN not set".

I investigated and realised that the InfluxDB is still in onboarding mode (http://10.42.0.1:8086/onboarding/0). I tried to fix it by adding a device variable in BalenaCloud : "INFLUX_TOKEN: 0". And then it seemed to work, at least HomeAssitant displayed a home dashboard. But there is a new bug down the road

• The Home Assistant seems to have no MQTT broker available (it fails when I try to add Tasmota integration for a device I have).
• IPScan from outside show that the 1883 port is live on the device though.

I don't know if the bugs comes from me, the underpowered device, or a bug in the software. Documentation for deploying was sparse, so I may have missed some steps. Can you help me investigate? Or start anew?

Thanks,

PS: Is this a good place to ask for support? I always truy to do it in public, in case someone else encouters the same bugs. Feel free to redirect me to a better space if needed.