Troubleshooting and Diagnostics

Troubleshooting and Diagnostics

Setup says "Failed to connect"

• Heat pump dialog: check that Modbus TCP is on, that its network and netmask admit the Home Assistant host, and that the port matches (see Installation and Setup).
• Web interface dialog: check that the web server is on (see Web Interface) and that the web interface opens in a browser; a slow controller may need another try a little later.

Setup says a device answers but refuses the value

The network is fine, but the device at that address and port is not the heat pump's Modbus TCP server, or not a Weishaupt one: check the address and the port.

All entities are unavailable

Four polls in a row failed. The heat pump is off the network or does not answer; the entities come back with the next good poll.

What you see	Where it is logged
The entities go unavailable because the heat pump does not answer	Info level
The entities go unavailable because it answers wrongly, a read hangs past its limit, or the integration failed	One error
They come back	Info level
Shorter drop-outs, which keep the last values	Debug log only
A register range the controller stops serving, and its return	Info level
A web interface page whose values go unavailable, and their return	Info level
Web interface polling paused	Info level, beside the repair notice

Home Assistant's default log level hides every info line here, the going and the coming back alike; set the integration's log level to info, or enable debug logging, to see them.

Some entities stay unavailable

• A module the heat pump does not have refuses its register range; its entities stay unavailable - on the tested WBB for example the fifth heating circuit.
• A heating circuit you switched on that the controller does not have may instead answer with factory values, its sensors unavailable; if the controller reports it switched off, a repair notice says so (see Installation and Setup).
• A sensor that is not connected reports a "no sensor" word and reads unavailable.

A write is refused

The value is outside the range the controller currently allows, or the daily write limit from the options is reached (see Installation and Setup). A system operation mode the controller does not offer is not refused but ignored by the controller (see How Data Updates).

Repair notices

Notice	Meaning	It goes
Heating circuit N not read	The controller has circuit N set up, this entry does not read it	When the entry, at a later load, reads it or the controller no longer has it; ignored, it stays ignored
Heating circuit N switched off at the heat pump	This entry reads circuit N, the controller reports it switched off	When the two match at a later load
Web interface polling paused	A page failed three times in a row; the notice names the page and why (see Web Interface)	By itself when the page comes whole again, or at once when the entry is reloaded

The heating circuits are compared each time the entry loads (see Installation and Setup). If the controller refuses the web interface's login, Home Assistant asks to re-authenticate that entry; polling stays stopped until a new user and password are accepted.

Debug logging and diagnostics

1. On the integration's page choose Enable debug logging, reproduce the problem, then Disable debug logging; the log file is downloaded.
2. Attach it to an issue, together with Download diagnostics from the entry's menu.

What the diagnostics hold: the register values and which address bands the heat pump serves, without its address or any name you typed (prefix, postfix, map file). They need the entry to be loaded. A web interface entry's diagnostics leave out the user, the password, the page addresses and the heat pump's title.

What the log holds: it is not cleaned the same way. With debug logging a connection error names the heat pump's address, and a map that fails to load names its path. Replace IP addresses and host names, your user name in paths and any names of people or rooms before you attach it to a public issue. For the web interface the log lists every request with its answer and how long it took, page addresses included; the user name, the password and the session ID never appear in it. Debug logging also switches on the log of the Modbus transport library (tmodbus); reproduce the problem and switch it off again.

A heat pump model nobody has tested

Entities stay unavailable or show odd values. tools/weishaupt_scan.bat in the repository reads every register the heat pump answers, without Home Assistant, and saves them as a CSV file: download it to a Windows PC in the same network, double-click it and enter the heat pump's address. It only reads, never writes, and the file holds no address, so it can be attached to an issue as it is. The scan takes about a minute.

For the web interface, tools/webif_capture.py collects the titles of its pages (see Web Interface).

The recorder warns after an upgrade

A changed unit or a removed state class after an upgrade: see Migration.