I currently encountered a problem. I can’t change the setpoint temperature in the UI
Any idea?
In the logs I get this error:
2020-07-16 19:44:22 WARNING (MainThread) [xknx.log] max value exceeded at heater: 6.5
2020-07-16 19:44:27 WARNING (MainThread) [xknx.log] max value exceeded at heater: 6.5
2020-07-16 19:44:33 WARNING (MainThread) [xknx.log] max value exceeded at heater: 8.0
2020-07-16 19:45:11 WARNING (MainThread) [xknx.log] max value exceeded at heater: 14.0
2020-07-16 19:45:30 WARNING (MainThread) [xknx.log] max value exceeded at heater: 6.5
2020-07-16 19:45:34 WARNING (MainThread) [xknx.log] Ignoring not implemented CEMI: <UnsupportedCEMIMessage description="APCI not supported: 0b1111000000" />
[Update]
Alright. I found my mistake
I had to enable send setpoint change in the MDT-device and after that I could add a group address for the temperature state address
[/Update]
Hi all,
after a long time I giving it a new try.
I am running the newest Version of HA (0.115.2) but I cannot manage to get my climate controlled via HA. I am still facing the problem that I am not able to set a target_temperature_state_address because it is simply not supported by the MDT heating actor. It only works with setpoint_shift_address.
The is only a group address that gives me the status of the actuator in percent.
I dont understand why I need the target_temperature_state_address when I just want to set the target temperatur to an “comfort value + setpoint_shift”.
Does anyone have an idea how I can solve this problem?
So have you now found a solution @markusmazurczak
can you share your ETS Config and KNX config? I’m currently setting it up and still struggeling to get it right.
Update, I got it working, except that the mode changes always back to away, when I change temperature and stays like this until the configured cyclic hvac state update is received from KNX.
After changing that configuration and programming the device the channels stepped into Standby mode and I have had to manually set every channel to comfort-Mode back so that HA can send new current setpoint temperature.
Thank you! I have played around further as well and made it work to have it come up with Comfort Mode and I’m using cycling 5 minute updates for HVAC mode so it all changes to comfort after reboot and after changing the value. If you like I can also share what I have configured.
I’m going crazy with this. Currently I get the message all the time: 2020-09-24 11:15:34 WARNING (MainThread) [xknx.log] Attempted to set value for non-writable device: climate_control.bathroom - Target temperature (value: 15.0)
And I dont get it. The device works with setpoint_shift and not by setting an target temperature but the HA config needs a target_temperature_state_address. Why is Home-Assistant always trying to set the target temperature and not sending the setpoint_shift to the given address (setpoint_shift_address)
you can see what I did at this post: KNX Climate heating actuator MDT
I can read the value without any problem using ETS. I dont know any way in Home-Assistant to execute a proper KNX-read to see it if works.
[Update]
I can read the value using a little NodeJS Script without any problem:
> C:\Users\Shelltux\Programming\nodejs>node knx_weather_server.js
> [info] "2020-09-24T09:49:00.130Z" 'Loading knx: KNXnet/IP protocol implementation for Node(>=4.x), version: 2.3.7'
> Ich lebe nun auf deinem KNX-Bus
> Got guestroom temp change. OldValue: 0 - NewValue: 26
var knx = require('knx');
var guestroom_temp = new knx.Datapoint({ga: '7/1/6', dpt: 'DPT9.002', autoread: true});
var connection = new knx.Connection( {
ipAddr: '192.168.178.118', ipPort: 3671,
loglevel: 'info',
manualConnect: true,
forceTunneling: true,
minimumDelay: 10,
suppress_ack_ldatareq: false,
handlers: {
connected: function() {
console.log('Ich lebe nun auf deinem KNX-Bus');
guestroom_temp.bind(connection);
},
// get notified for all KNX events:
/*event: function(evt, src, dest, value) {
console.log("event: %s, src: %j, dest: %j, value: %j", evt, src, dest, value);
},*/
error: function(connstatus) {
console.log("**** ERROR: %j", connstatus);
}
}
});
guestroom_temp.on('change', function(oldvalue, newvalue) {
console.log("Got guestroom temp change. OldValue: %d - NewValue: %d", oldvalue, newvalue);
});
connection.Connect();
Try to set the Read-Flag on your actuators setpoint_shift communication object and configure setpoint_shift_state_address to the same GA as setpoint_shift_address. (It needs a value on this GA and target_temperature_state_address before it can work).
Also remove min_temp and max_temp - this is covered by setpoint_shift_min and _max.
I change my temperture via 1 Bit. This works perfectly with my mdt gt2.
But if i change my temperture +0,5 on HomeAssistant the value ist written to my temp state adress.
After some min. my MDT GT2 writes his current target temp and the value bouces back to -0,5.
