There is a rudimentary web server available in ESPHome which would allow you to see the entities defined on the device without going through HA. I’m not sure that would be sufficient for this project, but I figured I’d mention it in case it’s helpful.
I think Nathan has you on the right track, so I have nothing further to add.
Check the docs: Management and Monitoring 
Smart BMS + ESP8266 = MQTT https://www.youtube.com/watch?v=eR4DOCQnUxA From what I understand, it works without a server.
Probably not. Minimum a mqtt broker would be necessary… 
Hi! People say it works, so I’ll give it a try with 1GB of RAM. I’ve got some Banana Pi boards lying around unused — worth trying!
Is the Raspberry Pi 4 with 1GB RAM good enough? · home-assistant/operating-system · Discussion #4071 Is 3B+ with 1GB Ram 16GB not enough for HA? : r/homeassistant
It might work. I’m still running on a 1G RPi 3B+. Caveat: I don’t do streaming video or audio. But right now I’m sitting at about 60% memory utilization and single-digit CPU.
This is the full model of my Banana Pi. https://linux-sunxi.org/Sinovoip_Banana_Pi_M2 Most likely, I’ll buy a different one.
I would suggest to actually buy hardware that is supported by HaOS 
(no 
!)
I bought an Orange Pi Zero 3 with 4GB of LPDDR4 RAM, WiFi, and Bluetooth, and I will try to install Home Assistant on it.
Why do you insist on going down the rabbit hole of hardware that is not officially supported by HA and capable of running HAOS? Did you miss the big deprecation announcement that all 32-bit, HA core, and HA supervised installs (what the Orange Pi HA install is) will be unsupported as of December 31st? Almost everyone else with incompatible hardware is rushing to move onto a supported installation platform…not buying something else that will become an unsupported paperweight in two months…
This orange apparently is not supported by HaOS!
Again, I would suggest to actually buy hardware that is supported by HaOS (no , no 
!)
…unless you want to get stuck with an unsupported 
…
I installed Ubuntu Server and I’m going to set up L2TP.
Spoiler alert: I think that I’ll be unsubscribing from this thread before it becomes a self-fulfilling tragedy…
Are you aware of the difference between 32bit CPU/SOC’s and 64bit ones? 
Why create this thread at all if you’re obviously going to ignore what everyone else tells you?
His plans changed since the original 32-bit Banana Pi.
Per a visit to my web search engine du jour, the Orange Pi Zero 3 that he/she/it bought is based on the Allwinner H618 SoC, which contains four 64-bit Cortex-A53 cores and considered ARMv8-A (64-bit) architecture.
Whether or not it is 100% binary compatible with any supported Raspberry Pi board and can run HAOS on the bare metal is another question. I’m thinking no, since someone is maintaining a Raspbian fork for the Orange Pi on GitHub that is obsolete and hasn’t been updated in two years. Plus, Orange Pi’s own docs say that the newest OS that it can run is Debian 12, so it has apparently already been left behind by Debian 13 trixie. Given that the chip is 3 years old and was intended for an embedded consumer device, I don’t expect someone to put the effort into maintaining support for it in a current Linux distro for a tiny audience using that chip for another purpose.
The Allwinner H618 SoC was intended for use in an Android TV box, so at least the OP can repurpose it into a set top streamer box when it fails to boot HAOS.
If he/she/it had taken a step back and looked at their original requirements to monitor the state of charge on a LiFePO4 battery management system and not do anything home automation-related, they would have just gone to a smartphone app store and downloaded something like the XiaoxiangBMS or Overkill Solar app that should both be able to communicate with that BMS via Bluetooth/BLE…
And made with 28nm lithography which was standard 15 years ago 
Go to for SBC’s is usally Armbian which also supports Trixie for this board 
I’m quite confident the author @sat-prof suffers the (today very common in this community) x-y syndrom problem 
