Help needed creating an issue on github - AVM Fritzbox DECT 302 problem with temperature limits

pmh · March 3, 2025, 8:18pm

Hi all,

I found a minor inconsistency with the Fritzbox integration when creating a scene that is supposed to set a group of thermostats to certain temperatures.

I am not sure if this is HA core or anything else and how exactly to create an issue (although I am familiar with github and I am an active contributor to multiple open source projects). The link “not sure where to go” or similar leads to Discord - where I did not get any reaction since Friday.

So I am posting again on this platform. Hope this is OK.

My posting on Discord:
----------- snip -----------
difficult to describe. The thermostat has got a setting that goes up to 28 Celsius. And the HA UI won’t let me save a scene defining a higher value. So far so reasonable.

But it looks like there is one additional step internally coded as 30 Celsius for which the e-ink display on the device then shows “MAX”. And whenever I try to save a scene with 28 Celsius it somehow magically jumps to 30/MAX and I get the error that 30 is out of bounds.

When I edit the YAML back to 28 the scene works fine. The dashboard widget for the thermostat shows 30, though.

So there’s some inconsistency here.

Why do I need this? In our appartment all the heaters share a single pipe and if I do not crank the small one in the bath room to “MAX”, the other rooms stay cold. So that’s that

Help appreciated - unsure how to file a proper bug report. Is this HA core? Or something different? If I am not mistaken one could simply raise the limit for that thermostat to 30 C and be done with it?
----------- snip -----------

So how do I go about getting somebody’s attention?

Thanks and best regards,
Patrick

tom_l · March 3, 2025, 9:59pm

Press the green “New Issue” button here: GitHub · Where software is built and follow the instructions.

Please make it clear in your issue that the integration only supports a maximum temperature setting of 28°C while the device itself supports up to 30°C.

pmh · March 8, 2025, 9:22pm

Sorry for not responding earlier - I know Github. The question is when I click on that should I go to:

Report an issue with Home Assistant Core
Report a bug with the UI, Frontend or Dashboards
I have a question or need support

And what lead me to create this thread here is that clicking on “I’m unsure where to go” takes you to Discord where I did not get this question answered either.

I don’t know if integrations like Fritzbox are “Core” or “UI, Frontend or Dashboards” …

Thanks and kind regards,
Patrick

tom_l · March 8, 2025, 10:34pm

Core issue.

pmh · March 14, 2025, 10:21pm

Thanks!

github.com/home-assistant/core

Change upper temperature limit for Fritz! DECT thermostats to 30 Celsius

opened 10:13PM - 14 Mar 25 UTC

pmhausen

### The problem Hi all, the upper temperature limit of FRITZ!Smart Thermo 302 …formerly known as DECT 302 is 28 degrees Celsius. But there is one more step that leads to the thermostat e-ink display showing "MAX" and the Fritzbox UI showing what is displayed in the attached screen shot meaning "full throttle". You can also reach the "MAX" setting by using the "+" and "-" keys on the device itself. This is as far as I can see internally coded as 30 C. Because if you switch to that setting in the Fritzbox UI the Home Assistant widget follows suit and displays "30" - see second screen shot. While you never can actively set "30" in HA, it's displayed as 30 if you set it to "MAX" in some other way. So for interactive use as well as scenes IMHO the maximum permitted value for these thermostats should be 30. About my motivation: in our apartment we have a "single pipe" heating system. All the radiators are daisy chained. And if we do not crank up the small one in the bath room to "MAX", then two other rooms are not heated at all. It's not that we prefer to actually have 30 C in our rooms ;-) But ignoring the question if it makes sense in real life, HA should allow the user to use the full range of settings of any actuator. Kind regards, Patrick ### What version of Home Assistant Core has the issue? core-2025.3.2 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Container ### Integration causing the issue AVM FRITZ!SmartHome ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_ ![Image](https://github.com/user-attachments/assets/2aaef033-3cb0-4a3e-8435-39717c7b0a0d) ![Image](https://github.com/user-attachments/assets/dfa375fe-a0ed-451a-9ec5-d0a5aa24fbf1)