-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify "follow underlying changes" behavior - Transform 'Auto' hvac_mode to 'Heating' #903
Comments
I will have a look if something is possible quickly. |
Please try this and let me know if it ok for you: https://github.com/jmcollin78/versatile_thermostat/releases/tag/7.2.2.beta2 |
@jmcollin78 : thank you, just tested it. Found some issues : (Case 2) case with several underlyings: I have 2 TRVZB in the living room, under the same VTherm: Will retry immediately with target > current temp |
Yes you are right. I need to force Heat again on all underlying devices. I'm afraid it oculd generates loop. This is the main risk when doing some hacks like that. But I will try this to see. |
New try with target > temp. I have :
I’’be tried same scenario as above, and same issue, Heat mode is not pushed back from VTherm to the underlying, as you confirmed Another issue I’ve seen : I thin it is a tricky situation, we should need more time to think about this, you’re right, I’m afraid we’ll run into a lot of edge cases and loops. … |
Salut JM, Est-il possible que ce changement provoque une détection erronée des modifications de l'underlying ? Je ne pense pas que ça me soit arrivé avant, mais aujourd'hui, trois de mes vtherms ont signalé un changement de l'underlying et sont sortis du mode confort. Hi JM is it possible that this change can cause false detection of changes to underlying? I don't think I've had it before, but today I had 3 vtherms claim that the underlying had changed and dropped out of comfort mode - Voici un exemple
|
would it not be safer to use an automation to detect the trv going to auto and change it back to heat? |
Hello @doubledrat , Did you install the beta 2 ?
I'm confident, I will find a solution. You will have to wait this week-end. |
No, beta 3.
…On Thu, 13 Feb 2025, 21:01 Jean-Marc Collin, ***@***.***> wrote:
Hello @doubledrat <https://github.com/doubledrat> ,
Did you install the beta 2 ?
would it not be safer to use an automation to detect the trv going to auto
and change it back to heat?
I'm confident, I will find a solution. You will have to wait this week-end.
—
Reply to this email directly, view it on GitHub
<#903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZMGBMGVMZ5ZKS5Q6K5GY32PUBZFAVCNFSM6AAAAABW3DG3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXG4YDAMZUGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: jmcollin78]*jmcollin78* left a comment
(jmcollin78/versatile_thermostat#903)
<#903 (comment)>
Hello @doubledrat <https://github.com/doubledrat> ,
Did you install the beta 2 ?
would it not be safer to use an automation to detect the trv going to auto
and change it back to heat?
I'm confident, I will find a solution. You will have to wait this week-end.
—
Reply to this email directly, view it on GitHub
<#903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZMGBMGVMZ5ZKS5Q6K5GY32PUBZFAVCNFSM6AAAAABW3DG3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXG4YDAMZUGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta3 don't have the code of beta2 😉 |
Oh.
I wonder where the phantom underlying changes are coming from then?
…On Thu, 13 Feb 2025, 21:17 Jean-Marc Collin, ***@***.***> wrote:
Beta3 don't have the code of beta2 😉
—
Reply to this email directly, view it on GitHub
<#903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZMGBPMVZDBSVRAHRX5F7L2PUDXXAVCNFSM6AAAAABW3DG3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXG4ZDSMRSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: jmcollin78]*jmcollin78* left a comment
(jmcollin78/versatile_thermostat#903)
<#903 (comment)>
Beta3 don't have the code of beta2 😉
—
Reply to this email directly, view it on GitHub
<#903 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZMGBPMVZDBSVRAHRX5F7L2PUDXXAVCNFSM6AAAAABW3DG3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXG4ZDSMRSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Discussed in #901
Originally posted by mcornillon February 10, 2025
Hey !
So far so good, my installation works great, I've activated the "Follow underlying changes" option on my TRVs (TRVZB by the way).
I have one Vtherm per room, all "connected" to a central one that activates the boiler.
With the option "Follow underlying changes" activated, I have the following behavior :
--> Would it be possible to restrict / or configure / the items we want to "synchronize" from the TRV to the Vtherm ?
In my case, I would like to :
Please give your comments on this idea/feature ?
This could probably be achieved in the current situation with an automation that monitors if the TRV Auto mode gets activated, and makes the modification on the Vtherm so that it is set back on the TRV. But could be much cleaner if implemented directly in Vtherm, isn't it ?
The text was updated successfully, but these errors were encountered: