AVM Fritzbox resets Comet Dect SetPoint

Ahnungslos · July 15, 2017, 1:08pm

Hello everyone,

my configuration:

Raspberry with openHAB 2, AVM Fritz! Binding from Robert Bausdorf
Fritzbox 7390, Firmware 6.83
Comet DECT Heating device connected to Fritzbox

Problem: when I set a new temperature with SetPoint to the Comet heating, it works, but within a few seconds the Fritzbox resets the value. Please have a look to my logfile, first change is initiated with the openHab, seconds is done automatically by the Fritzbox

HeizungArbeitszimmer_SetpointTemperature changed from 6.0 to 25
'avmfritz:fritzbox:192_168_1_1' changed from ONLINE: FRITZ!Box online to ONLINE: Resuming FRITZ!Box connection with SID 3ae20090f758a53c
HeizungArbeitszimmer_SetpointTemperature changed from 25 to 6.0
'avmfritz:fritzbox:192_168_1_1' changed from ONLINE: Resuming FRITZ!Box connection with SID 3ae20090f758a53c to ONLINE: FRITZ!Box online

//Ahnungslos

cweitkamp · July 15, 2017, 3:20pm

Hi Frank,

which configuration do you use for your Comet DECT in the FRITZ! OS? Do you set up a schedule? Vacation mode? Turned off? Do you use groups with a master device?

Ahnungslos · July 15, 2017, 3:45pm

Hi Christoph,

vacation mode is disabled, no “Heating of” (Heizung aus) period is defined, maybe the Fritz scheduling is active, there is no option to turn it off, I’ve seen no option like “manual mode”- I added a screenshot of the schedule section

//Frank

cweitkamp · July 15, 2017, 3:54pm

Which dates do you configure for “Heating off” (Heizung aus)?

Ahnungslos · July 15, 2017, 3:59pm

Hi Christoph,

i defined from 01.05 until 01.09, but if delete this section it is excactly the same behavior.

//Frank

cweitkamp · July 15, 2017, 4:15pm

Okay. That’s the reason why the SetTemp is set back to 6.0 (off).

The FRITZ!Box is the leading system and overrules the OH2 binding. You configured the Comet DECT to remain off from first of may until first of september. In this period you cannot set the temperature using the OH2 binding. If you need to do control the Comet DECT using the binding you could try to define a schedule always using EcoTemp (Spartemperatur) set to “off” (aus). I can observer the same behavior in my environment.

StvR · November 14, 2017, 7:18pm

Hi Christoph,
i 'm also dealing with this problem but using node red for the rules changing values. Did i maybe miss the solution or is it still an issue ?

BR Stefan

cweitkamp · November 14, 2017, 7:32pm

Hi Stefan,

I will do some tests.

cweitkamp · November 15, 2017, 12:22pm

Hey Stefan,

Can you give me an example of your item configuration? Did you configure those manually or did you use Paper UI? Thanks.

StvR · November 15, 2017, 6:16pm

Hi Christoph,

I’m quite not sure if that’s what you asking for. This is a screenshot showing the active channels of the comet dect defined via paper UI.
Down below there is the rule from node red where i tried quite simple to inject manually two different setpoint to the comet.

[{“id”:“6fab6b65.d5462c”,“type”:“openhab2-out”,“z”:“284b8de6.d11d12”,“name”:“XS_Comf_EG_WC_20.0”,“controller”:“8632d183.60c23”,“itemname”:“avmfritz_Comet_DECT_192_168_178_1_117950373200_set_temp”,“topic”:“ItemUpdate”,“payload”:“20.0”,“x”:693.1666870117188,“y”:149.34707641601562,“wires”:[]},{“id”:“98cf942e.9e1fc8”,“type”:“openhab2-out”,“z”:“284b8de6.d11d12”,“name”:“XS_Comf_EG_WC_18.0”,“controller”:“8632d183.60c23”,“itemname”:“avmfritz_Comet_DECT_192_168_178_1_117950373200_set_temp”,“topic”:“ItemUpdate”,“payload”:“18.0”,“x”:694.0556030273438,“y”:198.01387786865234,“wires”:[]},{“id”:“978f84a6.879368”,“type”:“inject”,“z”:“284b8de6.d11d12”,“name”:"",“topic”:"",“payload”:“true”,“payloadType”:“bool”,“repeat”:"",“crontab”:"",“once”:false,“x”:205.41680908203125,“y”:147.68045043945312,“wires”:[[“6fab6b65.d5462c”]]},{“id”:“1633b498.e0534b”,“type”:“inject”,“z”:“284b8de6.d11d12”,“name”:"",“topic”:"",“payload”:“true”,“payloadType”:“bool”,“repeat”:"",“crontab”:"",“once”:false,“x”:210.08355712890625,“y”:196.56929779052734,“wires”:[[“98cf942e.9e1fc8”]]},{“id”:“54881e1d.058368”,“type”:“openhab2-in”,“z”:“284b8de6.d11d12”,“name”:“XI_EG_WC”,“controller”:“19ed4f09.32cad1”,“itemname”:“avmfritz_Comet_DECT_192_168_178_1_117950373200_actual_temp”,“x”:655.4098510742188,“y”:91,“wires”:[[],[]]},{“id”:“8632d183.60c23”,“type”:“openhab2-controller”,“z”:"",“name”:“Raspberry”,“protocol”:“http”,“host”:“localhost”,“port”:“8080”,“path”:"",“username”:"",“password”:""},{“id”:“19ed4f09.32cad1”,“type”:“openhab2-controller”,“z”:"",“name”:“Raspberry”,“protocol”:“http”,“host”:“localhost”,“port”:“8080”,“path”:"",“username”:"",“password”:""}]

BR Stefan

StvR · November 15, 2017, 6:49pm

Hi Christoph,

sorry for that. I found the fault. I had to use grafik
instead of grafik

in the grafik

output module.

Also feels like a trap to me
Sending a setpoint like 20.4°C Fritz is rounding to 20.0 °C
Sending a setpoint like 20.6°C Fritz is rounding to 20.5 °C
Looks like Fritz only accepts step’s in half degrees.

Thanks for helping

BR Stefan

cweitkamp · November 15, 2017, 8:38pm

Sounds cool. To be honest, I am absolutely not familiar with Node Red. But I am glad you solved your issue on your own.

You are right. The FRITZ!Box only accepts temperatures in 0.5°C steps starting at 8.0°C up to 28.0°C.

EnerGiehl · January 6, 2018, 6:25pm

So ist there still no soloution for this Problem?

cweitkamp · January 7, 2018, 7:59am

Hi Robin,

What do you mean exactly?

Equinox · January 12, 2018, 5:31pm

Hi Robin,

I’ve had the same issue. After deleting cache and tmp, setting the temp works flawlessly again and without resetting the Comet.

BR
Markus

Moriarty · January 30, 2018, 8:29pm

Hi,

i deleted chache an temp but the issue ist still there.

My System: Pi3, openHAB 2.2.0 Release Build, Binding 2.2.0.

EcoTemp (Spartemperatur) set to “off” (aus)
Comfort is on

The log:

2018-01-22 17:26:10.234 [ome.event.ItemCommandEvent] - Item 'avmfritz_Comet_DECT_192_168_178_1_119600716704_set_temp' received command 20

2018-01-22 17:26:10.249 [vent.ItemStateChangedEvent] - avmfritz_Comet_DECT_192_168_178_1_119600716704_set_temp changed from 18.5 to 20

2018-01-22 17:26:11.487 [hingStatusInfoChangedEvent] - 'avmfritz:fritzbox:192_168_178_1' changed from ONLINE: FRITZ!Box online to ONLINE: Resuming FRITZ!Box connection with SID 9564f362ef455caf

2018-01-22 17:26:22.980 [vent.ItemStateChangedEvent] - avmfritz_Comet_DECT_192_168_178_1_119600716704_set_temp changed from 20 to 18.5

2018-01-22 17:26:22.989 [hingStatusInfoChangedEvent] - 'avmfritz:fritzbox:192_168_178_1' changed from ONLINE: Resuming FRITZ!Box connection with SID 9564f362ef455caf to ONLINE: FRITZ!Box online

What should i do?

Moriarty · February 2, 2018, 10:27am

When i set the Temperature via Button like its configured in the Fritz box ist works. But the Thermostat sets the temp ONLY when i manually wake up the Thermostat.

cweitkamp · February 2, 2018, 6:47pm

Hi Peter,

Maybe that is the root problem. After changing the settings in the FRITZ!OS you always receive a message that the data transfer to the device lasts up to 15min. Maybe the AVM API itself has a bug setting a new temperature if the device is in sleep mode. Should we hand over this case to their support and ask for help?

StvR · February 3, 2018, 8:19am

Hi Christoph,

Is it possible that there is a same difference between “item update” and "item command"
controlling via Openhab as controlling via Node Red ? The effect itself sounds quite similar to me.

BR Stefan

cweitkamp · February 3, 2018, 8:27am

Hi Stefan,

There is a difference between postUpdate and sendCommand. The first one updates the state of an item. The latter one updates the state AND sends a command to linked channels. See here for a more detailed description https://docs.openhab.org/configuration/rules-dsl.html#manipulating-item-states.