Device handler preferences

[wogapat (Patrick)]

@krlaframboise

They have a 600+ page Application Command Class Specifications document that should include all the command classes you’ll be using.

I’ll look forward to that.

@krlaframboise

I wouldn’t get hung up on trying to understand my code…

No, but I’m sure it may show me things I didn’t know you could do, which will help me be better.

I do need to go through my code and remove some duplications as well.

[krlaframboise (Kevin)]

@wogapat

I’m sure it may show me things I didn’t know you could do, which will help me be better.

I think the most complex DTH I’ve written is the Aeotec Doorbell 6 because it uses the Sound Switch command class which isn’t supported by SmartThings and I had to manually build those commands and manually parse those reports.

It also needs to set multichannel associations which I’ve never been able to get to work with ST using the built-in command class as-is so I had to manually build part of those commands too.

The z-wave specs show that you should be able to specify the list of endpoints for multichannel association set v2 so either ST didn’t fully implement that command class, they didn’t include that attribute in the ST documentation, or the set command is meant to be used in some other way that I haven’t been able to figure out…

[krlaframboise (Kevin)]

@tpmanley

Here are the different formats for options and the results of my testing:

They just broke these again!!!

Examples 1 and 2 you previously posted dislay as expected, but you can’t select anything.

Boolean settings that have a default value can’t be changed either, but that started a couple of weeks ago.

[wogapat (Patrick)]

I feel your pain. My v2 hub gave up about a month ago. I seriously considered replacing it but I went with Hubitat in the end. I finished moving my devices last week.

I’ve been lucky. The only integration, for me, that didn’t have a solution out of the box was lightwave and I’ve just released a beta app for lightwave in the Hubitat community. It’s been the right move for me.

[aonghusmor]

I am struggling with preferences, which I believe worked previously:

1. previously set preferences often get lost, revert to null.
2. set preferences don’t appear as such in the settings tile, so it’s hard to tell which is set.
3. bool preferences seem to be very broken. The slider just goes straight back to where it was and the preference may, or may not, have been set.

Am I alone, or are others struggling with the same issues?

[Brad_ST (Brad)]

@krlaframboise and @aonghusmor It sounds like you are impacted by this issue which has been patched as of this afternoon.

Cannot update device preferences / settings

Hi, I got a lot of devices on my hub and they have worked fine. But suddenly i can no longer update preferences/settings of each device. It is the same no matter what device i select. Have tried several different. I also tried to update the preferences through the IDE Webpage, but here it shows “500 Internal server error” when clicking “save” It happened after i played with an aeotec siren 6 where i changed back and forth with device handlers, deleted this device and installed and played wirh webcore. Do not know if any of these things have made the error. But i could device preferences a couple of days ago. Anyone experienced this issue or have a solution?

[krlaframboise (Kevin)]

@Brad_ST

It sounds like you are impacted by this issue which has been patched as of this afternoon.

It looks like the enum settings are working again so thank you for getting that fixed so quickly, but boolean preferences with default values still can’t be changed…

If the default value is false then it works as expected, but if the default value is true then you can’t change it to false.