balena home assistant: status online (heartbeat only)

Looking to build balena home-assistant on a Banana Pi. Following this deployment:

I then etch the image to the host SD card, and power it up.

I can see the device in the cloud fleet manager, but it is constantly in Online (Heartbeat only) mode. Checking the documentation that would indicate the is device is unable to connect to cloudlink (e.g. a firewall is blocking VPN traffic), and won’t be able to provide remote SSH connections. I can’t understand why, as there is local network connectivity and I have other balena hosts that connect just fine.

what’s my next move?

I’ll add, here is the only entries from the log:

Applying configuration change {"RESIN_SUPERVISOR_POLL_INTERVAL":"900000","RESIN_SUPERVISOR_DELTA_REQUEST_TIMEOUT":"59000"}
Applied configuration change {"RESIN_SUPERVISOR_POLL_INTERVAL":"900000","RESIN_SUPERVISOR_DELTA_REQUEST_TIMEOUT":"59000"}
Creating network 'default'

My LAN → WAN setting is Allow all.

As a test, I installed BalenaSound on the same SD and hardware and it just works. I’ll call this post good now, and will further investigate how home-assistant is installed.

Actually, very strange. The same hardware with BalenaSound running on it does work as a Spotify Connect client, but still has the Online (Heartbeat Only).

Anyone have any ideas why that is the case?

nmap -p 443 vpn.balena-cloud.com
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-12 23:28 GMT
Nmap scan report for vpn.balena-cloud.com (3.227.28.93)
Host is up (0.093s latency).
Other addresses for vpn.balena-cloud.com (not scanned): 35.169.89.252 2600:1f18:6600:7f00:3b29:5e04:b6af:68b7 2600:1f18:6600:7f01:b5fc:e785:75fc:2e80
rDNS record for 3.227.28.93: ec2-3-227-28-93.compute-1.amazonaws.com

PORT    STATE SERVICE
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 0.25 seconds

Think it’s time to retire the BananaPi. It did work before (on a different project), but it’s not working now. I put the same application on an RPi3 and it just worked.