You have filtered the logs, so the device responses to the “GET” are not shown, so I can’t see what the device is saying to the “Set” command (on-OFF). There should be a State Update message too. EDIT:maybe the extra space in the binary item is a problem? node67:switch_binary "
On the items, all the temperature items should be Number:Temperature, not just Number (maybe that will help).
As to configuration that is not normally how that works. You could create a channel(s) in that CC and link to parameter 10 or 11 and see what happens. Normally those are used to configure a device, not get something back from a device. Messages from a device normally come across in the Alarm (or Notification) CC. I don’t see that CC on the myot2.
thanks for the fast reply.
It’s a lot of things that doesn’t work, so I think, it will the best, we split it.
I’d set the items Heizwasser_Setpoint, DHW_Setpoint, HeizungRuecklauftemperatur and Heizung_Aussentemperatur to type Number:Temperature.
The first 2 Channels/Items accept the changes on OpenHAB. I’ll see tomorrow, if the boiler it will accept.
The value of the second 2 Cannels/Items now are constant 0,0 °C .?
The switch On/Off will change on OpenHAB to On/Off, but the boiler does not respond.
I send you the complete log, when I’d switched to On/OFF here: Request_BoilerOffOn.log (83.2 KB)
It seems, the change of the value to ON/OFF trigger a complete request to all channels. Normally the system do it every 6 minutes.
Is there any information in the log, what is going wrong?
Did you change the channel to eliminate the space? Are you filtering the log to node 67? There are no messages from the device in the log. Using the log viewer; If you are not filtering, the device is not in communication with the controller
Here is an example of a switch binary ON. Note the TX is transmit and RX is received from the device. You are not getting any messages from the device.
Did you change the channel to eliminate the space?
Yes, and I had create a new Item on the Channel zwave:device:18af13d3:node67:switch_binary with the OpenHAB GUI, but with no success. This 2 channels will change in OH on the same time, but not on the boiler.
Are you filtering the log to node 67?
Yes, on the console: tail -f ./openhab.log | grep “NODE 67” . I’d send you the complete log for the device (node 67) between 2024-11-25 19:17:45 and 2024-11-25 19:19, 4 minutes- this should include all data without timeouts.?
There are no messages from the device in the log. Using the log viewer;
I’m not using the log viewer- I’d not install it
If you are not filtering, the device is not in communication with the controller
OpenHAB does not request the new status from the device, but it seems, on the line 99 and above on the log ‘Request_BoilerOffOn.log’ the device send the current status back to OpenHab.? The status switch to OFF. The status will hold in OpenHab until the next change.
It seems also, on the line 410 in the log, the device send the status ‘On’ back to OpenHab.
But the boiler not accept the data. It is on the status ‘OFF’ all time.
Generally the devices must have a connection on different times: 2 channels has valid data, one channel is valid with leaks in the data.
The device is on the same room with one Fibaro rollershutter. The rollershutter works always as expected and it can route as ZWave-Device- so myot2 should be always on the zwave net.
On the boiler I can switch On/Off without problems, and on the remote control from the manufacturing company it also works. I’m affraid, the channel On/Off is a problem with the hardware from the boiler and the OpenTherm-protocoll.? Or can it be another cause? Can we test some others?
Is the configuration of the device ok? The device is like a plug always on the power supply.
here is a unfiltered log: log4Export.log (645.4 KB)
on line 436 I switch ON, on line 1693 OFF and on line 2775 ON again.
I hope, you’ll find something…
Thanks for the log. Between your charts and the logs it appears a very quirky device as to reporting. The messages from the device (those were what I wanted to look at) conform to zwave standards, but don’t always report a value. As to the On-Off those seem fine too. Could it be that ON just means it is ready to run, not that it is actually running and OFF means it won’t run even if it needs to?
What I don’t understand (I’m in the USA) are the values. It appears your setpoint is 26 or 27 C and the water seems to run around 20-24 C (ignoring your setpoints) those seem pretty cold versus the recommended 49 C (here). I’m also thinking the exhaust gas temperature only reports when whatever you use for fuel is running. Do these values from Zwave match your wifi app? Is your “hot” water really at 20C? Another suggestion is to contact OpenTherm support for how this device reports
Hello Bob,
Thanks for the reply.
The answers to your questions:
Yes, thats’s right. ON means heating, OFF ist StandBy. Thats also the answers to your second questions ON the temperatures: the Boiler was run to OFF. ON the time the log was created, the Boiler switched Automatic from Standby to nonfreeze. The termperature was minimally 20°C in this mode.
The Boiler Not accept the Setpoints.
I can work with the 3 channels, where send valid Data. IT seems, the problems related to the compatibility from the device or the Boiler. I will send a question to the manufacturer from the devices…
Jens
