User's choice of status indicator doesn't work


I’m trying to build my first Homey app. I’ve successfully added capabilities that show up on the list of “Status indicator” in the Settings for the device. However, even though I change the setting, the icon still just shows a black circle with a dash, and not the value for the capability that I chose.


Any tips what I might be doing wrong?

1: thermostat devices show the target temperature by default as special status indicator, not user settable

You seem to have built half a thermostat, you probably have to add the target temperature to the device, then it’ll show the value in the black circle:

1 Like

Thanks Peter for your quick reply!

That’s sad that (1) Athom has limited this possibility for Thermostats, (2) they do not inform the developer about this limitation, and (3) they haven’t then also disabled the setting of choosing status indicator for thermostats. This breaks the user experience as well as the developer experience in my opinion :frowning: . Maybe I’ll have to not make it a thermostat then, even though it is (we’ll, it’s a heat pump…)

Either way, I actually have implemented the target temperature also. The values show together in the thermostat UI component, but the number doesn’t show up in the status indicator. So even this expected behavior doesn’t seem to work for some reason. However, writing my reply to your reply made me go back and look at the device class reference and it seems like they have actually added a device class for heat pumps now! That’s great, I’m going to try this and see if it solves my problem! Thank you so much @Peter_Kawa!

Still…if anyone from Athom reads this…I would love for the documentation to be a bit more thorough so that these kinds of limitations/consequences were transparent.

1 Like

Hmm…except of course…that my Homey Pro cannot update to 12.0.0, and thus does not support the heatpump class :frowning:

It does support thermostat !
Not the heatpump >=12.0.0

That would be an improvement for the next gen firmware for Homey…

1 Like

Exactly! Sorry, I had made a typo… I am currently using thermostat, but then the status indicator doesn’t work correctly. So my thought was to try to use heatpump (since the app I’m building is for a heat pump :slight_smile:), but then I noticed that 12.0.0 hasn’t been released yet. So now I just have to wait for it I guess…which is frustrating since I can’t find any info on when it will be released. Will it take days or months? Or years?

YW, Johnny!

(1) Yes, probably it’s because of the vision. A thermostat is recognizable, the circle colors red/black/blue for heating/off/cooling.
They did not want “everything” to be adjustable for the users apparently.
Imho they should for instance release the status indicator lock, when “Power User” is enabled, to give one the freedom of owning a Homey.
(2) I’m no developer and I knew somehow. But after 4 years of ‘Homeying’ I’m under the impression there’s many loose ends in the documentation.
You can report improvements @ github, but I see you’ve found it already

I’d report this to the issue tracker as well, and to support:
(Don’t expect too much)

From a user’s POV it’s disabled:

Usually Athom says: soon™

Thanks a gain @Peter_Kawa for giving me a quick intro into the Homey culture and how to (perhaps) get progress on things :slight_smile: . Do you know if GitHub is the place to also suggest new/improved features?

Only that it’s not in the Web App…which led to my countless number of hours trying to understand what I’m doing wrong…but I’ve reached the conclusion that it’s a bug in the Web App unfortunately…hopefully if/when they fix that bug the status indicator will at least show what it’s intended to show - the target temperature…

The Status indicator only allows numeric or alarm capabilities.
Some built in indicators like Thermostate (based on capabilities measure_temperature and target_temperature, not based on device class!) or Lights (dim capability) are used automatically.

YW again.

Ah, now I see! I didn’t know about this new web app functionality, thought is was something from your app you wrote :rofl:

As far as I knew, the status indicator (and icon) never could be edited through the web app, only mobile app.
That’s why I didn’t get it.
Now I see it’s indeed possible to edit these item per web app as well.
Yeah for thermostats we can change anything for status indicator, but indeed it doesn’t change, and no warning whatsoever. A bit typical for Athom: we’re ought to find the errors & bugs, and so you did :woozy_face::grimacing:
As I noticed @ github issues, this behaviour is indeed marked as “bug” already.

1 Like

Yeah, it’s only that

  1. I can’t seem to find any documentation around these automatic behaviors, so how am I supposed to know about them?
  2. In the app I’m trying to build, the automatic number isn’t shown, I just get a dash, as can be seen in my original post. And since the automatic behavior isn’t described anywhere (at least that I’ve been able to find), I have no idea what is wrong, and thus how to fix it :frowning:

Can you show the devices’ capabilities, when you search for it here:

I’m looking for an overview like:

Was Support able to point to the information you’d like to find?

You can also ask in the developer channel at Slack. Join the Homey channel,

and look for #developers
(And you’re not the only one:)

If you added both capabilities, do they have a numeric value?
If one of measure_temperature or target_temperature has no value, the Thermostate state keeps Black because Homey can’t compare to show Orange or blue.
And the dash seems to be an empty capability.

Cool! Thanks for pointing me to this! I hadn’t found this page yet :slight_smile:

Here you go!

I guess my issue with the dash could be that I’m only using sub-capabilities and the number might only use the main capability? [3 min later] Yep, that was it! The status indicator will only show the main capability target_temperature. So Athom is basically forcing me to write code that is difficult to understand, since I have a bunch of temperatures to measure and set in my heat pump. Let’s see how this new heatpump class turns out…

Thanks (again) @Peter_Kawa for pointing me in the right direction to figure this out! You’re a star, and you should be paid by Athom because in my opinion you’re doing their job :wink:

Nope! Support only replies that it seems to be a dev question and support doesn’t give support on dev questions. They referred to GitHub, and also mentioned the Slack channel.

Oh no! So not even the class other will work? :frowning:

I’ll see how this plays out…maybe I’ll go back to Hubitat where the devs are engaged in the community forums and would totally fix these kind of things .

1 Like

Thanks for the ideas @RonnyW ! It could definitely have been the case, but actually I figured it out. The dash was due to the fact that I only had sub capabilities. I didn’t use the actual target_temperature main capability. Your comment, in combination with Peter’s comment below helped me figure this out! So thanks a lot!!

The colors actually worked, I just didn’t know what they meant (since again, I believer they are not documented anywhere…)

No problem, Johnny, and you’re too kind.

Sounds logical, for class thermostat.

But, hold tight:
I took a peek at OTGW MQTT app by Robin, it’s just possible to use multiple thermostats using only sub-capabilities.
But, you’d use the class other, and now you can use the status indicator as you wish (now it’s not trying to ‘be’ a thermostat class)

Screenshot from 2024-07-10 00-20-57