{"id":8601,"date":"2026-08-13T08:02:00","date_gmt":"2026-08-13T06:02:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=8601"},"modified":"2026-10-24T02:20:22","modified_gmt":"2026-10-24T00:20:22","slug":"hardware-resilience-in-the-electrical-panel-modbus-monitoring-and-emergency","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/it-networks\/hardware-resilience-in-the-electrical-panel-modbus-monitoring-and-emergency\/","title":{"rendered":"Backup Power Monitoring: Modbus, Home Assistant and Independent Protection"},"content":{"rendered":"

Local Modbus monitoring keeps inverter data available without the manufacturer’s cloud, provided the inverter, gateway, network and Home Assistant remain powered. Grid status, battery charge and power limits can then be observed locally. Home Assistant does not replace guaranteed backup transfer or electrical overload protection.<\/p>\n

Two responsibilities need separating. A professionally designed electrical installation handles grid isolation, backup supply and required load shedding independently of the automation server. Home Assistant adds displays, history and notifications. Local communication reduces external dependencies but does not guarantee real-time response.<\/p>\n

1. Establish the electrical backup path first<\/h2>\n

Not every solar inverter can form an island during a grid outage. Backup operation requires a supported function, a suitable battery or available generation, and the manufacturer’s intended transfer equipment. Continuous output, short-term overload capacity, starting currents, phase allocation and battery limits determine usable loads. State of charge alone does not describe these limits.<\/p>\n

Electrical-panel design and commissioning require a qualified electrical professional. Contactors switch loads; RCBOs protect against specified residual-current and overcurrent faults. These components do not automatically create grid isolation or safe backup logic. Selection, wiring and failure behavior must suit the installation. A heat pump is not universally a non-critical load: frost protection, controls and manufacturer requirements can change priorities.<\/p>\n

One possible architecture supplies only selected circuits through the backup path. Other installations require manufacturer-provided load management or an appropriately designed independent controller. The loads disconnected when control power disappears, and the conditions for reconnection, need definition and verification. A single relay or a Home Assistant switch command does not establish these properties.<\/p>\n

\"Independent
The electrical backup path works independently. Home Assistant reports measurements and uncertainty; two registers do not prove safe transfer or successful load shedding.<\/figcaption><\/figure>\n

2. Separate Modbus transport from the register map<\/h2>\n

Modbus RTU typically uses a serial RS485 connection. Modbus TCP uses a different message format over TCP. A translating gateway can provide Modbus TCP; a transparent serial server instead carries unchanged RTU messages over TCP. These cases correspond to type: tcp<\/code> and type: rtuovertcp<\/code> in Home Assistant. An Ethernet connector alone does not determine the choice.<\/p>\n

Register addresses and state codes depend on the device and firmware. Grid status is not universally located at 33000, nor battery charge at 37000. Home Assistant uses zero-based addresses. A manual’s reference such as 40001 can mean the first holding register, at address 0; conversion must follow the register documentation.<\/p>\n
Measurement<\/th>Required checks<\/th>Meaning<\/th><\/tr><\/thead>
Grid and backup status<\/td>Address, register type, valid codes and update behavior<\/td>Grid absent and backup active are different states.<\/td><\/tr>
Battery state of charge<\/td>Data type, scaling and invalid values<\/td>Energy reserve, not a direct measure of available output power.<\/td><\/tr>
Power and overload status<\/td>Sign, unit, phase reference and device limits<\/td>Additional operating information, not a replacement for protection.<\/td><\/tr><\/tbody><\/table>\n

Polling intervals request updates. Device response, serial transmission, other requests, timeouts and retries extend actual detection time. Even a two-second interval does not guarantee a response within two seconds. Unchanged or restored readings can be stale; reliable freshness monitoring needs, for example, a documented device heartbeat or the timestamp of a successful read.<\/p>\n

3. Read-only YAML with explicit prerequisites<\/h2>\n

The following template is deliberately incomplete. Entries using !secret<\/code> must be supplied from the verified device map; register addresses are centrally configured, not thereby confidential. This template fits only a device with a 16-bit input register for grid status and a 16-bit holding register reporting charge in whole percent. Different register types, word order, scaling or error codes require changes. An existing supported device integration can simplify manual mapping.<\/p>\n

YAML<\/span>