The iSaver with ESP Board and RS485 connecter
My first step…
Weird that I never thought that this Aseko device would have a web UI. 
never crossed my mind. Pretty stupid.
@tipofthesowrd Thanks for knocking on my head and bringing this option to my attention. Now it’s a completely new ballgame. 
(Device is Aseko, Asin Net)
First step, get the data flow into Home Assistant via Node-Red (creating MQTT sensors) to monitor the current data from the Aseko Asin sensors.
This is what I’ve done:
In the Aseko Web UI: Changed the Aseko Local IP settings from DHCP to a static IP (to keep all comms steady)
In the Aseko Web UI: Changed the Aseko setting for Serial Port “Remote Server Adds” to my HA server (with Node-Red) IP address.
In NODE-RED:
In Node-red the “TCP-IN” Node is Listening to the default port 47524 (stream of Buffer). I am getting data almost every second.
Tried to identify where the correct data is in the Buffer. First used what was posted but got the wrong data. Spent some time going through the Buffer to parse. So I am starting with the main sensors for my first version. This is what I found. (Only receiving the 120 bytes packet, haven’t seen 27… yet).
In my function node:
const buffer = msg.payload;
const serialNumber = buffer.readUInt32BE(0);
const pH = buffer.readUInt16BE(14) / 100.0;
const redox = buffer.readUInt16BE(16);
const temperature = buffer.readUInt16BE(25) / 10.0;
msg.payload = {
serialNumber: serialNumber,
pH: pH,
redox: redox,
temperature: temperature
};
Next I’ll try to see what else I can find.
Anyone that manage to identify the data in the Buffer… please share so we can create an overview table for everyone who wants to go down this route.
Prio now is to find and parse the state of water flow to the probes.