Skip to content

Loxone

The WattWächter Gas integrates with Loxone via its Modbus TCP server. There are two ready-made Loxone templates that create all sensors with address, data type and polling cycle. The WattWächter Gas does not provide SunSpec but its own register block, see Modbus TCP → Register block.

Prerequisites

  • Modbus TCP enabled on the WattWächter Gas — web interface → Settings → Modbus TCP → Enable Modbus TCP server → Save. Other ways under Modbus TCP → Enabling
  • A Loxone server on the same network — Miniserver, Miniserver Go or any other server with Modbus TCP (Miniserver Gen 1 only with the Modbus Extension)
  • A static IP address for the WattWächter Gas (see the warning below)

Loxone needs the IP address — not the .local name

Loxone does not resolve mDNS/.local names. Enter the WattWächter's IP address in the Modbus server object, not wattwaechter-XXXXXXXXXXXX.local.

Set up a DHCP reservation in your router or configure a static IP on the WattWächter. Without it the connection breaks on the next lease change — and Loxone will silently keep showing the last value it read instead of reporting an error. The FAQ explains how to find the current IP.


Downloading the templates

  • WattWächter GW


    4 values: meter reading (m³), flow rate (m³/h), energy (kWh) and power (kW)

    Download

  • WattWächter GW – All Values


    11 values: adding energy factor, pulse volume, pulses, medium, sensor type, status and pulses per revolution

    Download

Both templates require firmware 1.3.0 or later.

Importing the template

  1. In Loxone Config, add a Modbus Server under Network Periphery and enter the IP address of the WattWächter Gas with port as Address, e.g. 192.168.178.106:502.
  2. Select the Modbus server, open Device Templates in the ribbon and click Import Template…. Choose the downloaded XML file.
  3. The template then appears under Device Templates → My templates. Click it — Loxone creates the device with all sensors below the Modbus server.
  4. Save the program to the Loxone server and check in LIVE mode that Meter Reading shows the same reading as the web interface of the WattWächter Gas.

Meter reading empty?

As long as no meter reading has been entered on the WattWächter Gas, Meter Reading and Energy deliver no value. Enter the reading in the web interface — see Setup.

Adding the values manually

Without a template you add the values yourself:

  1. In Loxone Config, add a Modbus server and enter the IP address of the WattWächter Gas with the port as Address, e.g. 192.168.178.106:502.
  2. Below it, add a device via Add Modbus device and one analogue sensor per value (Add analogue sensor).
  3. For each sensor set function code 0x03 (Read Holding Registers), the address and the data type from the table.
Value Address Count Data type
Meter reading (m³) 41010 2 float32
Flow rate (m³/h) 41012 2 float32
Energy (kWh) 41014 2 float32
Power (kW) 41020 2 float32

All values are float32, big-endian with the high register first — there are no scale factors. The remaining registers are listed under Modbus TCP → Register block.


Troubleshooting

All sensors stay at 0 / no connection
  • Is Modbus enabled on the WattWächter Gas? Check in the web interface under Settings → Modbus TCP whether the server is running.
  • Does the Address field contain an IP address with port (192.168.178.106:502) and not a .local name?
  • Did you save the program to the Loxone server after making the change?
  • The WattWächter Gas allows a maximum of 2 concurrent Modbus connections. If a test with modpoll or Home Assistant is still running, disconnect it first.
Values were there and are now frozen

A classic sign of a DHCP address change: Loxone holds the last value instead of showing an error. Check the current IP of the WattWächter Gas and set up a DHCP reservation.

More items in the Modbus TCP troubleshooting section.