sorry dont know. the only thing i see at the moment when looking at your config: i have remote control set to enabled, i see you have it disabled. i dont know what remote control is, but the name suggests it could prevent remotely changing the program?
remote control enabled means that the central unit accepts remote commands (openwebnet commands).
Means that with remote control disabled, only physically at the central unit changes can be made.
Not setting changes from outside i.e. from openhab or from an original Bitcino touch panel are accepted.
Therefore it only shows the status if the remote is enabled or not and for the same reason it only can be changed directly on the central unit.
Hi Andrea. In these days I have installed OH 3.3 on an RPi4 and I have installed the new OpenWebNet (before I used the 2.5 version of Massi). Apparently everything is simpler at the graphical interface level, but in doing two tests on thermoregulation (the thing I need most) I noticed that now the individual zones can only be set to MANUAL, PROTECTION and OFF. I can no longer find a way to bring the single zone back to AUTO mode (i.e. put it back in step with the programming of the control unit). I also armed the 99-zone control unit, but from it I can only force all the zones to take the programming at the same time. For me on OH 2.5 the function of being able to set each single zone to MANUAL was very convenient, and then put it back in AUTO without having to physically do it on the command. It seems strange to me that this thing was not thought of, so I guess I am doing something wrong in the use of the binding.
Can you let me know how I can do to be able to put a single zone back into automatic mode, after I have put it in manual or have turned it off?
Thank you so much for the suggestions, good day everyone! Emiliano.
I am running OpenHab 3.3 with the latest openwebnet binding 3.3.0 All my lights, switches, energy meters etc work fine, but I am having a problem with the stand-alone thermostats LN4691. I can read all the values correctly, but cannot change the setpoint temperature from OH. Changing the setpoint with the buttons on the thermostat works correctly and the changed values are also displayed correctly in OH.
But if I change the setpoint value with a widget such as the slider, then although the OH value changes, the new value is not written back to the LN4691. If this is a configuration issue, could someone post an example of how to do it using the UI in OH 3.3
You already have an example with BasicUI in the binding README
If this does not work you should post here the DEBUG logs when you try to change the setpoint in one of the thermostats from OH.
DEBUG level should be set also to the other messages log (see the link I already suggested), otherwise it’s impossible to see the sent/received messages between OH and the bticino gateway
always, always, always use code fences when posting logs. Or even better copy-paste the log in a .txt file and upload it on the post
Here are there images of the configuration for the thermostat taken from the UI. NOTE that they show a setpoint temperature of 22C which was the last value sent by OH, but not accepted by the thermostat whch still shows 20.5C on the display screen.
@pjgregory can you change in the configuration of yout thermo zone 1 Thing the OpenWebNet Address parameter: 1#1 to → 1
and see if this way it works correctly ?
