# Honeywell Evohome 2020 device handler update **URL:** \ **Category:** Writing Device Types\ **Created:** [November 18, 2020, 5:16pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832 "2020-11-18T17:16:27Z")\ **Posts on this page:** 20\ **Page:** 4
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 29, 2021, 6:02pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/61 "2021-01-29T18:02:42Z")
Ok nayelyz thanks a lot, i will try it and let you know. I tried using just one also but i got the same thing. Maybe i am missing something else. Did you take a look at my device presentation file? ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [January 29, 2021, 6:07pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/62 "2021-01-29T18:07:26Z")
I see you added this `label` property, did you try to change the label of the capability? > ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 29, 2021, 6:12pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/63 "2021-01-29T18:12:37Z")
Yeah i was getting the same issue where the device in the dashboard showed checking status, so i copied this from the evohome zone presentatation when we had the same issue. In an unrelated note, the the temperature history in evohome used to work great. Is there something wrong with the dht or is it the smartthings app? One more thing. Since the rules api replaced the old one, i see the refresh capability in automations. What does it do and is it deprecated as well? ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [January 29, 2021, 6:34pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/64 "2021-01-29T18:34:54Z")
ooh, I see. Well, the error before was because the temperature unit wasn’t included in sendEvent. If you check the VID once it’s generated you see this label because it automatically gets the configuration of temperatureMeasurement in dashboard View, it shouldn’t be included when the device config is created. > [@Andremain](#): > > the the temperature history in evohome used to work great Can you describe the problem, please? > [@Andremain](#): > > What does it do and is it deprecated as well? The `refresh` capability has one command with the same name. If you create a function in the DTH for this command, the actions there should be executed, it is used mostly to refresh the capabilities’ value. > [@Andremain](#): > > rules api replaced the old one What do you mean by this? ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 29, 2021, 6:44pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/65 "2021-01-29T18:44:40Z")
> [@nayelyz](#): > > I see. Well, the error before was because the temperature unit wasn’t included in sendEvent. If you check the VID once it’s generated you see this label because it automatically gets the configuration of temperatureMeasurement in dashboard View, it shouldn’t be included when the device config is created. Oh ok, so i just need to remove that and it should work. > [@nayelyz](#): > > Can you describe the problem, please? Yeap. Here is an old screenshot of the evohome thermostat with the history being updated every 5 mins. ![Screenshot_20201219-000331_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/5/d/5d8efd4d20d1149b6574d8420a9caae3509ca54c.jpeg) And here is one now: ![Screenshot_20210129-203958_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/2/f/2fffa8210bc09cc33ef5c6cb8582ac07f8f4d889.png) The temperature history is not saved.. > [@nayelyz](#): > > What do you mean by this? Well the last smartthings update started using the new rules api for scenes and automations where prior to that it whas using i think the old smartthings api. It messed a lot of people’s scenes and automations in the process. There is a whole threat if you are interested. Also, did you ever go about that issue with alexa not being able to set a temperature in its application? ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [January 29, 2021, 7:57pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/66 "2021-01-29T19:57:13Z")
> [@Andremain](#): > > Here is an old screenshot of the evohome thermostat with the history being updated every 5 mins. Mmm…let me check this part. > [@Andremain](#): > > Oh ok, so i just need to remove that and it should work. Yes, and remove the switch from states too > [@Andremain](#): > > Also, did you ever go about that issue with alexa not being able to set a temperature in its application? I believe this error is because of the unit’s compatibility, for example, I created another device that only uses the `thermostatHeatingSetpoint` capability, and in the ST app, the temperature appears as Celsius, but in Alexa, it appears as Fahrenheit. When I change to Fahrenheit on the ST side, now both show the same value, but I start receiving this error. How is it on your side? ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 29, 2021, 8:14pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/67 "2021-01-29T20:14:23Z")
> [@nayelyz](#): > > Yes, and remove the switch from states too Oh i didn’t do that but it works (kinda). If you think i should remove it, i will. As you can see in the screenshots bellow the switch icon appeared. ![Screenshot_20210129-221232_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/2/5/252b8fb6c8a4665d83a38f90f3a470dd8ceb3d66.jpeg) ![Screenshot_20210129-221252_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/c/a/ca94a27acb0fecfd037e5dd8023484d08db70811.png) However i get a weird bug. When i press the switch button, lets say from the off position to on, it switches to on for a few seconds, the evohome platform turns the hot water on, but the switch in smartthings goes back to off. Evohome however has hot water on without switching to off. Same goes for the other way around. Here is a video showing it in action bellow in google drive. [https://drive.google.com/file/d/11vAvbjCnStkUa8EkW4EzxKndmlaqN6hw/view?usp=drivesdk](https://drive.google.com/file/d/11vAvbjCnStkUa8EkW4EzxKndmlaqN6hw/view?usp=drivesdk) Can you please help me fix this? Not sure about this but i copied this from the heating dht, do you think it plays a part in this? def initialize() { sendEvent(name:“temperature”, value:“5”, unit:“C”) sendEvent(name:“thermostatMode”, value:“auto”) sendEvent(name:“supportedThermostatModes”, value:[“auto”,“off”,“eco”,“away”,“dayoff”,“custom”]) } > [@nayelyz](#): > > I believe this error is because of the unit’s compatibility, for example, I created another device that only uses the `thermostatHeatingSetpoint` capability, and in the ST app, the temperature appears as Celsius, but in Alexa, it appears as Fahrenheit. When I change to Fahrenheit on the ST side, now both show the same value, but I start receiving this error. How is it on your side? I was able to change the values when the dht used to have the thermostat capability in the old integration. Also, assuming you may not know, in the alexa app, you can go to devices, echo and alexa, select alexa on this phone, and change the measurement units from there. My impression is that this issue comes from the fact that my device handler can’t accept values of 0.5, and sinse alexa does not allow entering the values directly, we get this error. Could also be something else though as i tried using a routine for setting the value, and it still doesn’t work… ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 29, 2021, 11:19pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/68 "2021-01-29T23:19:59Z")
And now we are back to checking status ![Screenshot_20210130-011944_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/a/4/a4e35dced8cc1ec546c11c965dfcb312c9d76e10.jpeg) ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [January 30, 2021, 12:12am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/69 "2021-01-30T00:12:29Z")
> [@Andremain](#): > > And now we are back to checking status It is because of the `unit` property is not included when the events are generated in this function: [https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R1.8%20(not%20working%20yet)#L184](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R1.8%20(not%20working%20yet)#L184) You need to do the same as with Evohome: > [@nayelyz](#): > > For the checking status, was solved after sending the temperature event with the unit, because the dashboard view expects this value. That’s why I added this [condition](https://gist.github.com/nayelyzarazua-bluetrail/7fd9ff595fc898f7b8cc905267ac90b9#file-dthevohome-groovy-L361) in the DTH. > [@Andremain](#): > > My impression is that this issue comes from the fact that my device handler can’t accept values of 0.5 You’re right, but to allow the increase of 0.5 it’s simple. You need to include something like this in your device configuration. ```auto "detailView": [ { "component": "main", "capability": "thermostatHeatingSetpoint", "version": 1, "values": [ { "key": "heatingSetpoint.value", "range": [ 15, 75 ], "step": 0.5 } ], "patch": [] } ] ``` Thanks for the configuration hack BTW, now I don’t receive errors and the value is correct. > [@Andremain](#): > > When i press the switch button, lets say from the off position to on, it switches to on for a few seconds, the evohome platform turns the hot water on, but the switch in smartthings goes back to off If you don’t receive a `network error` it can be due to the several conditions in [setSwitchState](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R1.8%20(not%20working%20yet)#L304). I’ll try to find out what’s going on. ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 30, 2021, 12:00pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/70 "2021-01-30T12:00:58Z")
@nayelyz as always, thank you SO MUCH for your help! > [@nayelyz](#): > > You need to do the same as with Evohome: I did this and got the dashboard icons to work properly. thanks. > [@nayelyz](#): > > You’re right, but to allow the increase of 0.5 it’s simple. You need to include something like this in your device configuration. I did this as well and got the 0.5 temp change to work. Sorry to be a pain but, is there a faster way to set a specific temperature, like a slider or something? As every time i tap to change a degree up or down, it takes a couple of seconds to apply. A slider which could select the temperature needed would be much faster. If not, i’ m just happy it works anyway 🙂 > [@nayelyz](#): > > Thanks for the configuration hack BTW, now I don’t receive errors and the value is correct. As for Alexa, i still get the same error when setting the temperature from the app… > [@nayelyz](#): > > If you don’t receive a `network error` it can be due to the several conditions in [setSwitchState](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R1.8%20(not%20working%20yet)#L304). I’ll try to find out what’s going on. I am not getting a network error. I do believe this is something in the dht as it behaved like this before updating it to display correctly in the new smartthings app using the device presentation. Btw i added the check health capability in the dht. Dont know if it matters. I am sorry for not being much help in this regard, as i don’t really have any skills in programming… Oh and never mind for the temperature history.. It decided to work day 🙂 ![Screenshot_20210130-143954_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/7/7/77a25fd780b8fc3eb7a44a1042c0a97add57f15e.png) ![Screenshot_20210130-143946_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/6/3/6395ebabe53df4e4c154955ef568beaf0c0214bb.png) ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [January 31, 2021, 1:42pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/71 "2021-01-31T13:42:18Z")
@nayelyz something i also noticed is that it shows that the hot water is on in the dashboard while in the device details it shows as off. ![Screenshot_20210131-124041_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/a/e/ae3b9a10e414131c0e0dc7bf4cf2b8cb51ba5fba.jpeg) ![Screenshot_20210131-124059_SmartThings](https://global.discourse-cdn.com/smartthings/original/3X/d/d/dddcc58f18f0397ea25387b41b6b77ffbad2b860.png) ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [February 3, 2021, 12:57am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/72 "2021-02-03T00:57:16Z")
> [@Andremain](#): > > Sorry to be a pain but, is there a faster way to set a specific temperature, like a slider or something? Do you mean to change the `Heating Temperature` in the SmartThings app? If so, when you click on the numbers (temperature) it shows a pop-up where you can write a value directly. > [@Andremain](#): > > when setting the temperature from the app That’s odd, I’ll install your latest DTH version and check it (and also the `switch` behavior) because I used a virtual device that only had the `Heating Temperature` capability. > [@Andremain](#): > > Oh and never mind for the temperature history… It decided to work day 🙂 Awesome news! > [@Andremain](#): > > something i also noticed is that it shows that the hot water is on in the dashboard while in the device details it shows as off. Yes, this is because the icon active/inactive changes according to the alternatives of the capability used in _dashboard_ \> _states_. As you’re using `temperature` in that section and it doesn’t have alternatives, the icon won’t change. ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [February 3, 2021, 6:37am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/73 "2021-02-03T06:37:04Z")
> [@nayelyz](#): > > If so, when you click on the numbers (temperature) it shows a pop-up where you can write a value directly. Oh ok thanks! I didn’t know that! > [@nayelyz](#): > > That’s odd, I’ll install your latest DTH version and check it (and also the `switch` behavior) because I used a virtual device that only had the `Heating Temperature` capability. Thank you for doing this. I will be a big help if i can tell the temperature i want to alexa instead of doing custom voice automations to get heating to turn on. > [@nayelyz](#): > > Yes, this is because the icon active/inactive changes according to the alternatives of the capability used in _dashboard_ \> _states_ . As you’re using `temperature` in that section and it doesn’t have alternatives, the icon won’t change. If i can add alternatives to make this work, that would be great. But for now i believe top priority is if you can please help me fix the bug where i turn the device on, hot water turns on, but in smartthings it switches back to off on its own. Please. please help me solve this.. ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [February 3, 2021, 10:04am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/74 "2021-02-03T10:04:45Z")
@nayelyz some good news regarding the hot water. I have found that while i change the state of the on/off switch for the water and it returns to its previous state, it actually needs some time to get the actual state. So if from the off position, i switch it to ON, the device will switch back to Off almost immediately and will switch back to the ON position after a few minutes, showing the correct switch state. This is also true on the other way around. Please find the video bellow on google drive, which shows this behavior in action. > **[smartthings evohome water slow to return to set state.mp4 (video)](https://drive.google.com/file/d/13ripKMIpzOMgeMLG6T0STxTXMx9tRYgJ/view?usp=drivesdk)** > > Google Drive file. I believe this is something to do with the polling time or refresh time being either too fast or too slow. Any chance you can take a look it ? When i switched it to off, it took 3 minutes and 25 seconds to set the correct state back. Here are some logs when switching it on: ![2](https://global.discourse-cdn.com/smartthings/original/3X/e/0/e05c6c2cd81f488bc930b8ede318f684e44643ab.png) Also by setting the polling interval inside the app to 1 minute, it switches to the correct state after about 30 seconds. ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [February 4, 2021, 8:26am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/75 "2021-02-04T08:26:10Z")
@nayelyz any luck with the hot water switch issue? ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [February 4, 2021, 11:45pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/76 "2021-02-04T23:45:06Z")
> [@Andremain](#): > > When i switched it to off, it took 3 minutes and 25 seconds to set the correct state back. Ok, for this part, I need to confirm the following: - In settings \> until, the value selected is `Permanent`. You need to select it again (changing to another setting and then going back) each time you install or update the device. - The `generateEvent` values in the logs is called in the SmartApp (poll), so this is the information it receives from Evohome. - If you want to show the on/off state in the app right after you send it, you need to add the following in the functions `on()` and `off()`: ```auto void on() { if (state.debug) log.debug "${device.label}: on()" sendEvent(name:"switch", value:"on") //This line setSwitchState('on',until=-1) } ``` Originally, the sendEvent() is executed until a response from the Parent (SmartApp - Evohome) is received. While the request is being completed, there can be a poll that generates the event with the opposite value, that’s why we see this behavior. ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [February 5, 2021, 6:34am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/77 "2021-02-05T06:34:54Z")
@nayelyz Yes this is definitely true. > [@nayelyz](#): > > In settings \> until, the value selected is `Permanent` . You need to select it again (changing to another setting and then going back) each time you install or update the device. Yes i believe this is also true. > [@nayelyz](#): > > The `generateEvent` values in the logs is called in the SmartApp (poll), so this is the information it receives from Evohome. Sorry where exactly i am supposed to add this? > [@nayelyz](#): > > ```auto > void on() { > if (state.debug) log.debug "${device.label}: on()" > sendEvent(name:"switch", value:"on") //This line > setSwitchState('on',until=-1) > } > > ``` > [@nayelyz](#): > > Originally, the sendEvent() is executed until a response from the Parent (SmartApp - Evohome) is received. While the request is being completed, there can be a poll that generates the event with the opposite value, that’s why we see this behavior. This is also what i think but i cannot figure this out. I was playing around with the code in the last few days, but honestly this is quite complex for me. Maybe if i keep updating old integrations, i will catchup at some point 😛 ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [February 13, 2021, 12:58am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/78 "2021-02-13T00:58:02Z")
Hi, @Andremain. Sorry for the delay, I was checking the issue of the Evohome device using Alexa and finally, I’ve found the root cause. Using the `thermostatMode` capability, and initializing the `supportedThermostatModes` attribute [here](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20dht%202020%20Release2.5.txt#L195), another control is added on the Alexa side (`Cool temperature`) which doesn’t exist. This is causing the error when using the `heatingSetPoint` capability. If I omit this capability, the error is not received. As this capability is only used on the ST side, I suggest you create a similar capability and there you can directly configure the available modes. > > [@Andremain](#): > > Sorry where exactly i am supposed to add this? Sorry, I meant adding the `sendEvent`(with the corresponding value on/off), in these two functions: [https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R2.5%20(BETA)#L465](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R2.5%20(BETA)#L465) [https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R2.5%20(BETA)#L470](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20Hot%20Water%20Zone%20R2.5%20(BETA)#L470) ---
**Author:** ![Andremain](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/andremain/32/91463_2.png) [@Andremain](https://community.smartthings.com/u/Andremain)\ **Post date:** [February 15, 2021, 9:26am UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/79 "2021-02-15T09:26:04Z")
> [@nayelyz](#): > > Sorry for the delay, I was checking the issue of the Evohome device using Alexa and finally, I’ve found the root cause. > Using the `thermostatMode` capability, and initializing the `supportedThermostatModes` attribute [here](https://github.com/andremain/EvohomeSmartthings2020/blob/main/Evohome%20dht%202020%20Release2.5.txt#L195), another control is added on the Alexa side ( `Cool temperature` ) which doesn’t exist. This is causing the error when using the `heatingSetPoint` capability. > If I omit this capability, the error is not received. As this capability is only used on the ST side, I suggest you create a similar capability and there you can directly configure the available modes. No worries @nayelyz and as always thanks a lot for helping me out. How exactly do i do that? Do i need to add a new capability called customthermostatmode and remove the thermostat mode one? Wont that break the smartapp’s functionality? What if i modify the thermostat mode capability and change every instance of it to customthermostatmode and add the ones you sent to the jason file. Will that work? Also the hot water mode still doesn’t work. It switches back again until it polls the api. As this works, i don’t think it is that important. This can stay as it is. The issues i would like to have resolved would be: 1. The issue with Alexa as i think it is a must. 2. If possible to have the switch of the hot water on the dashboard to display the correct state. The rest can wait a bit. I have also heard that groovy is going away. Does this mean that all the work we have done here will be useless in a few months? It will need to be recreated from scratch? ---
**Author:** ![nayelyz](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nayelyz](https://community.smartthings.com/u/nayelyz)\ **Post date:** [February 15, 2021, 11:12pm UTC](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832/80 "2021-02-15T23:12:13Z")
> [@Andremain](#): > > How exactly do i do that? This post has the steps to create a Custom Capability: > [@Custom Capability and CLI Developer Preview](https://community.smartthings.com/t/custom-capability-and-cli-developer-preview/197296): > > Overview At SmartThings we want to provide tooling to allow developers to get their device integrations working in the SmartThings app. These changes will allow an integrator to move from using custom commands and attributes to custom capabilities. DTH Migration For Custom Capabilities In order to follow along with the example set forth in this guide, you will want to have the CLI set up, so make sure that you take this step first. You can download the CLI here from the [releases tab](https://github.com/SmartThingsCommunity/smartthings-cli/releases) and read more about it in the [README](https://github.com/SmartThingsCommunity/smartthings-cli/blob/master/packages/cli/README.md). It is also recommended that you familiarize yourself with the concepts: [Custom Capabilities](https://developer.smartthings.com/docs/devices/capabilities/custom-capabilities)[Capability Presentations](https://developer.smartthings.com/docs/devices/capabilities/capability-presentations)Walkthrough We are going to walk through a simple example of updating our Device Type Handler (DTH) so that devices installed with the DTH will be … You can take my configuration and use it as input for the commands, for example, to create the capability: ```auto smartthings capabilities:create -j -i customCapability.json ``` And, yeah, you would need to remove the capability “thermostatMode” and replace it with the new one. (this will require a new VID as the capabilities list has changed) It wouldn’t cause a conflict because the SmartApp makes reference to the attribute name and the new one can use the same value. > [@Andremain](#): > > The issue with Alexa as i think it is a must. The custom capability and removal of the `supportedThermostatModes`event should solve this issue. > [@Andremain](#): > > If possible to have the switch of the hot water on the dashboard to display the correct state. Adding the new lines in the on/off functions, the switch value keeps changing as before? > [@Andremain](#): > > Does this mean that all the work we have done here will be useless in a few months? It will need to be recreated from scratch? The migration was the fastest way to make this integration work. It’s not official the remaining time for the Groovy IDE tool. However, you start learning about the recent tools and the [Developer Workspace](https://smartthings.developer.samsung.com/workspace/). This would be a cloud-connected device and I think it would be better to use a [SmartApp Connector](https://smartthings.developer.samsung.com/docs/devices/smartapp/smartapp-connector.html) to create it. [Previous page](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832.md?page=3) [Next page](https://community.smartthings.com/t/honeywell-evohome-2020-device-handler-update/211832.md?page=5)