| One device does not react from the app | Connection status (see “Connections”); unbound objects; Health page (see “Value Transformations & Health”) | Bind the missing objects, repair the connection, clear transformation errors. |
| A device ignores "all off" / room commands | Is it excluded from global commands (see “Alarm PIN & Global-Command Exclusions”)? | That exclusion is deliberate — the admin set it. Remove it in the admin panel if unwanted. |
| No history, empty charts | Is the history service enabled (see “Services & Protocols”)? Is Log historical values switched on for that object (see “Object Settings, Logging & Notifications”)? | Enable the history database and switch on Log historical values per object. History starts from the moment logging is switched on — it is not retroactive. |
| Weather shows nothing | API key entered? Location set (see “Network & Time Settings”, “Weather Service”)? Service enabled? | Enter a valid provider key and set the city/coordinates; test with the live reading on the Weather page. |
| Energy prices are empty | ENTSO-E key? Bidding zone chosen (see “Energy Price Service”)? | Enter the key, pick your bidding zone, click Save Configuration, then switch the service on; the switch goes back to off if the fetch fails. |
| An MQTT connection shows down | Test the connection (see “Connections”): does the broker report Not authorized or refuse the connection? | Fix the username/password or the port; for mqtts:// check the certificate (CA certificate, or Accept self-signed certificates for a broker using its own). The server keeps retrying on its own once it is right. |
| An MQTT widget never updates | Is the object's topic exactly what the device publishes? Does a JSON path point at a field that exists? | Click Scan broker in the object editor (see “MQTT Integration”) and pick the topic and field from what the broker really carries — a wrong path drops every message silently. An outgoing topic must not contain + or #. A broker that refuses topic filters (its access-control list) is reported in the server log. |
| The built-in broker shows nothing on the MQTT Broker page | Is the MQTT Broker service switched on, and was the server restarted afterwards (see “Services & Protocols”)? | Enable the service, restart, then reopen Configure. The Status panel says when the broker is not running (see “The Built-in MQTT Broker”). |
| A device cannot connect to the built-in broker | Does it have its own account? Is the address in the device exactly the one under Address to enter in a device? | Add an account per device; anonymous connections are off by default, so a device with no credentials is refused. Check the listener card reads Listening and not Off. |
| A device stops working right after topic rules are switched on | Does that account have a rule covering the topics it uses? | With Restrict topics per account on, an account with no matching rule is refused everywhere. Add a rule per device; HyperVisu's own account needs none — it always keeps full access. |
| Retained values are gone after a restart | Is Keep retained messages across restarts on? Is Allow retained messages on? | Switch both on. Without persistence the broker starts empty and every widget waits for the next device publish. |
| Nothing appears on the published state topics | Is Publish widget states to MQTT on? Does the panel say it is enabled but not publishing? | Publishing needs the MQTT protocol enabled and a connection to a broker. Check the topic preview matches what you subscribed to — the serial and the topic style are part of it. |
Commands on a …/set topic do nothing | Is Accept commands over MQTT on? Is anonymous access off? Is the object an incoming-only one? | Commands are refused wholesale while the broker accepts anonymous clients, and per message on read-only objects or payloads that cannot be read as the object's type. |
| A BACnet Scan network finds nothing | Is the BACnet/IP service running (see “Services & Protocols”)? Is the device on this subnet, on the standard port? | Enable the service; then use Scan address (see “BACnet/IP Integration”) with the subnet broadcast (192.168.1.255) when broadcasts are filtered between VLANs, or the device itself (192.168.1.70:47808) — a device on a non-standard port is never found by a broadcast. |
| A BACnet device ignores the widget | Is another system (the building management system) writing the same object? Multi-state off by one? | Set a Write priority lower in number than the other writer (see “BACnet/IP Integration”); use offset -1 on multi-state bindings. |
| A TCP/UDP test fails or the connection stays down | Cannot reach … connect timed out or ECONNREFUSED | Check address and port, and that nothing else holds the device's single connection (the vendor's own tool). A test on a connection the service already holds reports the live state instead of probing — that is expected. |
| A Sonos Scan network finds no zones | Are the speakers on the same network segment as the server? Is the Sonos protocol enabled? | Discovery uses a network broadcast, which routers and VLANs often block. Type the seed speaker IP address by hand instead — one address is enough for the whole household (see “Sonos Integration”). |
| Sonos source buttons show the wrong names | Were the favorites changed in the Sonos app after the widget was created? | Press Sync Sonos favorites on the widget (see “Devices Library & Sonos Binding”). The names are stored on the widget and do not follow the Sonos app on their own. |
| A device created from the library does not react | Was Apply changes run after creating it? Does the device require an option to be switched on (its Setup requirements)? | Apply the pending changes; then re-read the template's requirements — most inverters ship with Modbus TCP disabled and some need an installer account to enable it (see “Devices Library & Sonos Binding”). |
| A TCP/UDP device ignores commands or sends no values | Does the template end with the delimiter? Are commands sent back to back? Is there a Match pattern? | Check the Frame sent preview (see “TCP/UDP Integration”); raise Delay between commands; an incoming object without a match pattern never receives a value, and the key must appear in the device's feedback frame. |
