# \[APP\]\[PRO\] VThermo

**URL:** <https://community.homey.app/t/app-pro-vthermo/36442>\
**Category:** Apps\
**Tags:** app\
**Created:** [October 24, 2020, 12:28pm UTC](https://community.homey.app/t/app-pro-vthermo/36442 "2020-10-24T12:28:56Z")\
**Posts on this page:** 20\
**Page:** 11

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [December 19, 2022, 7:35am UTC](https://community.homey.app/t/app-pro-vthermo/36442/203 "2022-12-19T07:35:48Z")

</div>

> [@Gullars](#):
>
> VThermo doesn’t seem to be compatible with the Gree HVAC app(?). Do you know if there’s an easy fix either on my side, your side or the Gree HVAC app side in order to get this working?

VThermo can be used to control other physical thermostats by setting the set point up and down, but for that it needs the temperature reading from the physical thermostat.

In your case it doesn’t find that temperature, I guess.

But you can use VThermo with a temp sensor, and add two flows to control the Gree HVAC.

1. WHEN: VThermo “Heating turned on”, THEN: control Gree HVAS (turn on).

2. WHEN: VThermo “Heating turned off”, THEN: control Gree HVAS (turn off).

---

<div class="post-metadata">

**Author:** ![Gullars](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@Gullars](https://community.homey.app/u/Gullars)\
**Post date:** [December 23, 2022, 7:34am UTC](https://community.homey.app/t/app-pro-vthermo/36442/204 "2022-12-23T07:34:35Z")

</div>

Thanks! I will try that. Will that method also support Tibber controlling?

---

<div class="post-metadata">

**Author:** ![Gullars](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@Gullars](https://community.homey.app/u/Gullars)\
**Post date:** [December 23, 2022, 7:51am UTC](https://community.homey.app/t/app-pro-vthermo/36442/205 "2022-12-23T07:51:37Z")

</div>

@balmli : There seem to be a bug with the «heating turned off» card. When I select it, my Homey app goes all black… I have tried with two different Homeys, and get the same bug on both.

---

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [December 29, 2022, 5:38am UTC](https://community.homey.app/t/app-pro-vthermo/36442/206 "2022-12-29T05:38:22Z")

</div>

> [@Gullars](#):
>
> There seem to be a bug with the «heating turned off» card. When I select it, my Homey app goes all black… I have tried with two different Homeys, and get the same bug on both.

Yes, the mobile app goes black. But the web app ([https://my.homey.app/](https://my.homey.app/)) works fine, so there’s something wrong with the mobile app.

Try using the webapp until Athom fixes the mobile app.

---

<div class="post-metadata">

**Author:** ![Finnsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/finnsen/32/23691_2.png) [@Finnsen](https://community.homey.app/u/Finnsen)\
**Post date:** [January 20, 2023, 9:17am UTC](https://community.homey.app/t/app-pro-vthermo/36442/207 "2023-01-20T09:17:26Z")

</div>

@balmli I use the VThermo to control my Mill ovens where I have set “Thermostat” under “Control devices in the same zone”. This works mostly fine. As this is in my cabin, I reduce the temperature down to 8 degC when we are not there.

What I observe is that some times the setpoint VThermo sets for my Mill ovens are to low for the Mill oven, resulting in that the oven setpoint is not reduced hence the oven steers towards the previous setpoint. Typical example is that the room temp (measured with a Aqara Temp and Humid sensor) is below the setpoint, 8 degC, the setpoint set on the Mill oven might be set as low as 4 degC. It seems that the lowest temp that Mill accepts is 5 degC.

So to the question, is it possible to set a low (and maybe high) level for the temperature VThermo set for the thermostats is steers?

---

<div class="post-metadata">

**Author:** ![AsgeirK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asgeirk/32/45216_2.png) [@AsgeirK](https://community.homey.app/u/AsgeirK)\
**Post date:** [February 17, 2023, 11:26pm UTC](https://community.homey.app/t/app-pro-vthermo/36442/208 "2023-02-17T23:26:29Z")

</div>

I have been using vThermo for more than a year now, almost working perfectly. My primary usage is controlling cables in concrete floor where I don’t have sensor. Instead I am using a Aqara close to the floor and vThermo to control the switch. The only issue I have discovered during the use is it sometimes get “out of sync”, sometimes very warm or sometimes cold. This happens if there is a manual action on the switch. I think the solution to this is to introduce an extra check on temp every x minutes/hours. Please consider this @balmli

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [March 15, 2023, 7:03am UTC](https://community.homey.app/t/app-pro-vthermo/36442/209 "2023-03-15T07:03:23Z")

</div>

Moving to Homey Pro '23. Created a new VThermo device but cannot save any settings because an error is thrown “Invalid Capability: target\_temperature”.

Steps to reproduce:

- create new VTHermo device
- open settings
- press save immediately: no error message.
- open settings
- change 'Temperature calculation method" from “Average” to “Newest” and press Save
- Error: “Invalid Capability: target\_temperature”

---

<div class="post-metadata">

**Author:** ![Otter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/otter/32/11467_2.png) [@Otter](https://community.homey.app/u/Otter)\
**Post date:** [March 15, 2023, 3:07pm UTC](https://community.homey.app/t/app-pro-vthermo/36442/210 "2023-03-15T15:07:35Z")

</div>

VHumidity isn’t registering my aqara temp/humidity sensor. it is in the same room but isn’t reading its properties. any suggestions? I had this working for years but with the new Homey Pro install it broke.

---

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [March 16, 2023, 6:19am UTC](https://community.homey.app/t/app-pro-vthermo/36442/211 "2023-03-16T06:19:25Z")

</div>

> [@RogerSt](#):
>
> Moving to Homey Pro '23.

You must use the test-version v. 1.10.x for HP23,

> **[VThermo](https://homey.app/en-us/app/no.almli.thermostat/VThermo/)**
>
> Virtual thermostat and humidity controller

It’s still work in progress, but I’m running v. 1.10.2 on two HP19s and one HP23, and it’s working fine for me.

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [March 16, 2023, 6:22am UTC](https://community.homey.app/t/app-pro-vthermo/36442/212 "2023-03-16T06:22:14Z")

</div>

v1.10.2 TEST - same issue ☺

---

<div class="post-metadata">

**Author:** ![bwa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bwa/32/17852_2.png) [@bwa](https://community.homey.app/u/bwa)\
**Post date:** [March 16, 2023, 3:39pm UTC](https://community.homey.app/t/app-pro-vthermo/36442/213 "2023-03-16T15:39:53Z")

</div>

Using 1.10.2 with Homey Pro 2023 I discovered one of my zones where heating, even if the temperature was way above the set point.

From the event on the VThermo I can see it’s entering Idle state at 10.32 today  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/0/802ee89ed8906611727f6b64c198687ea433346b.jpeg)

From the event on the Wall Switch I can see it was turned on at 10:25, matching the Active state, but the Idle state seems to got lost, so I dicovered it and manually shut off the swich at 14:37

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/d/bd1ed46d2812dd63027e0805c136a867e8a63908.png)

Maybe the VThermo should discover this and repeating to turn off the Switch ? The Insigth from the Temp sensor is getting the increased temperature, and VThermo should be able to try a little harder to turn off the switch …

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/9/69dd01f008e73c576ae1e1619a5ef072a44482c4.png)

---

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [March 19, 2023, 7:13am UTC](https://community.homey.app/t/app-pro-vthermo/36442/214 "2023-03-19T07:13:11Z")

</div>

> [@RogerSt](#):
>
> v1.10.2 TEST - same issue

On -rc.61 I’m not able to recreate this issue

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [March 19, 2023, 10:05am UTC](https://community.homey.app/t/app-pro-vthermo/36442/215 "2023-03-19T10:05:49Z")

</div>

Hi @balmli ,  
This is weird, I add a VThermo thermostat device, open settings, change the first parameter from average to newest, press save,… boom… Invalid capability: target\_temperature…  
I am also on rc61

---

<div class="post-metadata">

**Author:** ![bwa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bwa/32/17852_2.png) [@bwa](https://community.homey.app/u/bwa)\
**Post date:** [March 21, 2023, 9:30am UTC](https://community.homey.app/t/app-pro-vthermo/36442/216 "2023-03-21T09:30:22Z")

</div>

Got an another incident where the VTherm is not able to turn off the power switch in current zone

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/3/434abf9b1ad48d16692ec303fbefe6b526f4ba8c.png)

When desired temperature is lowered, the switch is not turned on …

diag : fe524410-8a42-4511-a8a0-0911b222c452

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [March 29, 2023, 6:30am UTC](https://community.homey.app/t/app-pro-vthermo/36442/217 "2023-03-29T06:30:10Z")

</div>

Hi Bjørnar,  
On v10-rc65 I have the same issue.  
Would it help if I sent you a diag report? Would you have time to investigate?  
Roger

---

<div class="post-metadata">

**Author:** ![Svein\_Arne\_Eggen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/svein_arne_eggen/32/16491_2.png) [@Svein\_Arne\_Eggen](https://community.homey.app/u/Svein_Arne_Eggen)\
**Post date:** [March 29, 2023, 6:01pm UTC](https://community.homey.app/t/app-pro-vthermo/36442/218 "2023-03-29T18:01:13Z")

</div>

Hi, After switching to homey 2023 VThermo does not get any temperature readings from any Fibaro devices. Is that a problem with new version ore did I miss something?

---

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [March 30, 2023, 6:45am UTC](https://community.homey.app/t/app-pro-vthermo/36442/219 "2023-03-30T06:45:25Z")

</div>

Yes, I see that this is an issue. Will have a look at it.

---

<div class="post-metadata">

**Author:** ![balmli](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/balmli/32/1308_2.png) [@balmli](https://community.homey.app/u/balmli)\
**Post date:** [March 30, 2023, 6:46am UTC](https://community.homey.app/t/app-pro-vthermo/36442/220 "2023-03-30T06:46:25Z")

</div>

> [@Svein\_Arne\_Eggen](#):
>
> homey 2023

For HP 2023, you must use the test-version.

> **[VThermo](https://homey.app/en-us/app/no.almli.thermostat/VThermo/)**
>
> Virtual thermostat and humidity controller

There’s and issue with it, but please be patient. Will be fixed.

---

<div class="post-metadata">

**Author:** ![Svein\_Arne\_Eggen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/svein_arne_eggen/32/16491_2.png) [@Svein\_Arne\_Eggen](https://community.homey.app/u/Svein_Arne_Eggen)\
**Post date:** [March 30, 2023, 8:45am UTC](https://community.homey.app/t/app-pro-vthermo/36442/221 "2023-03-30T08:45:48Z")

</div>

Thanks, works perfectly.

Mvh  
Svein Arne Eggen

---

<div class="post-metadata">

**Author:** ![RogerSt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rogerst/32/12432_2.png) [@RogerSt](https://community.homey.app/u/RogerSt)\
**Post date:** [March 30, 2023, 2:05pm UTC](https://community.homey.app/t/app-pro-vthermo/36442/222 "2023-03-30T14:05:24Z")

</div>

Hi Bjørnar,

Process before this diag was created:

- reboot
- wait a while 5-10 mins
- remove old vthermo device
- add a new vthermo device
- in settings, tried to enable ‘Temperature sensors in the same zone’ - other thermostats in the same zone.
- press save, then error:
- ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/3/836142326286f829a27a2ed2ce1f2f6448dacd39.png)

Created Diagnostics ID: adc4f213-8b29-41f9-85d4-996c084ef1c6  
on HP23 - v1.0.0.-rc65  
using _test_ version Vthermo: v1.10.2

[Previous page](https://community.homey.app/t/app-pro-vthermo/36442.md?page=10)

[Next page](https://community.homey.app/t/app-pro-vthermo/36442.md?page=12)
