nexuri2mqtt

A Nexuri flat is already fully metered: electricity, hot and cold water, indoor temperature, humidity, CO2, boiler and ventilation state. All of it measured by hardware the rent pays for, and all of it visible in the vendor’s dashboard. What the dashboard does not do is automate. It shows values and lets you change a setpoint by hand, and its history is monthly, which answers a billing question and little else.

The bridge does the plumbing: log in, discover what the account can see, poll on a sane interval, publish to MQTT with Home Assistant discovery. After that the data behaves like any other sensor - full resolution history, energy meters in the Energy dashboard, CO2 that can drive ventilation alongside hardware Nexuri knows nothing about. It is read-only on purpose, because writing to a building management system moves real boilers and blinds, and that waits until the read path has proven itself. Unofficial: Nexuri publishes no API documentation, so the client was built by watching the official web app’s own network traffic, and it can break whenever the vendor changes something.