Supported_features

No, supported features tells the system that it supports a feature. Think of a vacation package. Package A is just your room. Package B is your plane flight and your room. Package C is plane flight, your room, and free booze. Package D is a room and free booze.

a room is represented as 1 in the system.
a flight is represented as 2 in the system.
free booze is represented as 4 in the system.

So package A’s supported feature is 1. Package B’s supported features is 3 (1 + 2). Package C’s supported features is 7 (1+2+4). Package D’s supported features is 5 (1 + 4). Now a computer can quickly look at a value of any customer who purchased packages and immediately know what options they got or what package they purchased just by looking at the supported features number.

Your question about brightness and supported_features would be like if you asked: Do I have 7 free drinks in package c?

So No. There is no relation to brightness value and supported_features value.

1 Like

Well, what about this lamp then, which - according to “supported_features” isn’t capable of anything (‘0’) !! But I can assure you it is capable. Much more than nothing. (It’s an IKEA lamp, but the way)

image

where is it coming from? Whatever integration is creating it isn’t properly setting the supported features.

That one is coming from IKEA.
Here’s another device that has a lot of attributes that can be manipulated, but according to the “supported_features” it can only be turned on/off. Again of course this is not correct.

image

Are you equating what you can do with it physically to what you can do with it in HA? If yes, then sadly, that’s not how it works. If the API only allows you to do certain things, then only certain things can be done from HA. Either way, I’d start by inquiring in a IKEA thread or whatever integration is bringing the IKEA devices into HA.

You lost me.
I can ‘do’ everything listed, and more - especially if I turn to the REST API (but let’s leave that out for now). Everything listed in the picture I posted, can be ‘done’. I’m just puzzled as to why then the Supported_features = 1

Again, it’s based on whoever created the integration. If they decided to set your supported_features equal to 23423432 to allow baking cookies, then that’s what you’d get. Please consult the creators of the integration or ask in a thread with people who have the devices. For all we know, it could just be poorly coded.

Also, the ikea integration doesn’t even have a climate device… Are you mistaken on what integration it comes from? If it’s a custom integration, all bets are off. They don’t have to follow the rules if they don’t want to.

No, no - the climate device is an ELKO Thermostat - through the deConz integration. The Ligth was an IKEA device. Sorry for the confusion.

Found this thread in hopes I can get some answer or reasoning to why/what is happening.
A couple HA updates ago, my geeni filament (edison) bulbs would turn on/off, dim (brightness) and change temperature. Now they only change temperature and turn on/off.

Not sure how the brightness got removed as I haven’t messed with anything on the cards that interact with them. I do know the Tuya app has gone through a lot of changes (maybe something in there?)

As for supported features, my bulbs look like this: supported_features = 0

No matter what value I attempt to update, the bulbs do not dim.
However if I use the SmartLife app or Alexa, they do.

Is there a way to see all the supported features?

Only by looking at the code