TRV Controller Discussion Thread

[Busta999]

Good morning

This is a useful bit of testing, can check that your Spirit device settings are setup as follows:

spirit_device_settings.png

I suspect what is happening is that when the Spirit returns the Setpoint (which isn't needed by the plugin), the plugin can't tell whether that is the result of a poll or whether a physical button has been pressed. I suspect that is why it is showing it as being in TRV Hardware Mode.

Won't this block my graphing it if the Thermostat and Setpoint are not in the poll?

Also, On the first Spirit fw 0.15 if I set the Poll Device to Only When Activity is detected I stop getting TRV Temperature.

The one with 0.16 don't have this problem.

[autolog]

Do your graphing from the TRV Controller custom state values. The TRV Controller polls according to the poll settings you define in the TRV Controller device settings.

Interesting regarding 0.15 vs 0.16 - you learn something new everyday.

You should still be OK as the TRV Controller will poll for you.

I am going to try setting Status Polling unchecked i.e. no polling by Indigo (the TRV Controller will still do it).

[autolog]

... This is how it is setup now.

That confirms what I thought, it is sending back the setpoint so the plugin thinks it is a hardware change as it can't differentiate between the two.

[Busta999]

Making changes now.

For the Graphs...

Which Setpoint/Temp to collect ?

Looks like it should be:

SetPointHeatTrv
TemperatureTrv

[autolog]

Correct - as documented here: https://github.com/autolog/TRV_Controller/wiki/usage#custom-states

[Busta999]

OK

RTFM

[autolog]

OK

RTFM

I didn't mean it like that - I was just pointing you at the info in case I wasn't immediately around to answer.

[Busta999]

No problem at all

Appreciate your time working this through.

Popping out for a couple of hours updated everything and added 4th Radiator to TRV Controller
and restarted TRV Controller

Will see how it all settles down now

[Busta999]

Enhancement Request

Can you add a new state

setpointcurrent

i.e. the current setpoint the TRV Controller is aiming for

This will allow graphing to chart current target temp against actual temp

I know this exists in the schedulexSetpointHeat but switching between four sources per radiator is difficult to achieve in MatPlotLib

No rush at all - Nice to have so you can track how it is doing

[autolog]

Consider it (already) done.

It is a standard Indigo state named setpointHeat

Now that could be missing from the documentation.

[superholz]

Can I use the local Hardware switches of the thermostate to adjust the setpoint which is then relevant for the TRV controller?

[autolog]

Can I use the local Hardware switches of the thermostate to adjust the setpoint which is then relevant for the TRV controller?

Do you mean by pressing the PLUS and MINUS buttons on the Spirit TRV?

If so, then that should work and the TRV will go into TRV Hardware Control mode - see custom state controllerModeUi The setpoint on the TRV will then be reflected in the TRV Controller as its setpoint.

The Boost button isn't guaranteed to work at the moment but may do?

[superholz]

Yes, I mean the PLUS and MINUS Buttons. As a TRV I'm using the Devolo 09356, it should also work for this one?

[autolog]

... As a TRV I'm using the Devolo 09356, it should also work for this one?

Should do, Just tested with a Popp (similar) and that works OK.

Best thing is to try it and see.

[Busta999]

Any thoughts on what is happening here?



Looks like the valve is reporting 0% but temp is rising on the trv and the room thermostat.




Sent from my iPad using Tapatalk