I have understood, i must make discovery first, but maybe i do something wrong,
java -cp ha-devi-mqtt.jar io.homeassistant.devi.mqtt.service.DiscoveryService
root@lonkero:/home/kari/devireg# java -cp ha-devi-mqtt.jar io.homeassistant.devi.mqtt.service.DiscoveryService
Error: Could not find or load main class io.homeassistant.devi.mqtt.service.DiscoveryService
Caused by: java.lang.ClassNotFoundException: io.homeassistant.devi.mqtt.service.DiscoveryService
OK, i try to ask more clearly… I have got this running…almost… If i start MQTT explorer i can see MQTT flow from my 2 devireg thermostat, but how i could see these in HA ?
There is a solution with ADDONs but because im̀ using docker i cant us these. Also there are solutions with MQTT but MQTT permit only one device and there is https://github.com/pvainio/vallox-mqtt running already. SO i ask, is there any solution to get my Devis to HA. Maybe you have seen that i’m newbie with these issues…
I have another problem. Installed, worked like a charm for a couple of weeks. Suddenly out of nothing 2 out of 11 thermostats became unavailable. Thermostats are visible in DevSmart iOS App. They are online, I can see them connected on my router. In HA i see this:
“OFFLINE;COMMUNICATION_ERROR;Connection refused by grid: 1”
Was already restarting the addon, MQTT Server, Entire HA, Thermostat, router
Any ideas?
same here, like some HA update broke the integration
Devi mqtt log
Connection lost. Reconnecting...
Connection lost (32109) - java.net.SocketException: Connection reset
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:197)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.net.SocketException: Connection reset
at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:328)
at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:355)
at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:808)
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:961)
at java.base/java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288)
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:268)
at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:92)
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:137)
... 1 more
15:38:40.467 [OH-thingHandler-29118] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:28.670 [OH-thingHandler-29434] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:30.462 [OH-thingHandler-29434] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:34.309 [OH-thingHandler-29435] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:38.670 [OH-thingHandler-29430] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:40.462 [OH-thingHandler-29429] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 15 seconds, sending PING
18:01:44.308 [OH-thingHandler-29435] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 30 seconds, reconnecting
18:01:48.670 [OH-thingHandler-29436] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 30 seconds, reconnecting
18:01:50.462 [OH-thingHandler-29430] WARN i.h.b.d.internal.SDGPeerConnector - Device is inactive during 30 seconds, reconnecting
18:01:54.325 [pool-2-thread-1] INFO i.h.b.d.internal.SDGPeerConnector - Connecting to peer 0420f7d942cb67dfe891299f02d8bfc744f7986180da4109a483e1d6094fc901
18:01:58.673 [pool-1-thread-1] INFO i.h.b.d.internal.SDGPeerConnector - Connecting to peer a5eca2df5f249768edf24cdd94b912f4a8d822ce324cba109ed629504a94f669
Mine is actually different. Connection to grid is OK, except grid refuses it (previously it was fine)
17:16:28.179 [pool-7-thread-1] INFO i.h.b.d.internal.SDGPeerConnector - Connecting to peer ***peer id***
17:16:28.230 [pool-7-thread-1] WARN i.h.b.d.internal.SDGPeerConnector - Device went offline: Connection refused by grid: 1
Message published to topic devi/state/10253147/binary_sensor_device_connected: OFF
Message published to topic devi/state/10253147/sensor_device_connected: OFFLINE;COMMUNICATION_ERROR;Connection refused by grid: 1
these go further in log continiously: 18:05:04.975 [pool-2-thread-1] WARN i.h.b.d.internal.SDGPeerConnector - Device went offline: Connection refused by peer: 4
I can see from HA all my Devireg Smart - thermostats and everything seems to be working. No log errors etc. If I change anything by hand or script, the information is not updated to thermostats. If I make a change in DEVI mobile app, it is applied to thermostat and I can see the change in HA at the same time.
Any ideas where to start to debug the issue? I think this problem started with latest HA update (running 2025.1.2 core and 2024.12.3 supervisor) .
I noticed exactly the same issue today after updating to latest HA core 2025.1.2. I also updated the Mosquitto MQTT to latest version at the same time. After the updates the controlling from HA stopped working.
Everything works fine from DEVI mobile app, and I can see all state changes in HA, but cannot control anything from HA. Looking for ideas how to debug and if anyone has an idea on how to fix this issue.
I have tried to restart HA, Mozquitto MQTT and reload the core mozquitto addon. No luck so far.
Hi, I also updated to 2025.1.3 ans no change was seen. Then I rebuilt Devi MQTT and restarted HA. Now it works again. Strange hickup. It would be great to understand / hear what can cause this kind of stall.
Now there is a problem with 2025.3.1
All temperature sensors became unavailable, because of strict check for unit_of_measurement on 2025.03.1 (°C not C)
Waiting for 2025.3.2 to understand this a bug or feature
On a different note, is the “Forecast” feature working for you? When enabled, the thermostat should decide when to start warming up the room to reach the target temperature at the specified time. When it is disabled, it starts warming up the room at the specified time. I have it enabled (double-checked in the Devi app), but it always just starts warming up the room at the specified time, as if the feature is disabled.