TRV Controller Discussion Thread

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 9:00 am

Jon

Absolutely!!!

They were observations not problems

I’ll get into it further over the weekend.

I have an external temp sensor in every room, it has allowed me to tweak the non controllable TRV until they are hitting the right temp - they are largely rooms not used very often, or small rooms I don’t mind over heating a little - en-suite / bathroom etc.

I really like your idea on using the TRV Controller to overset setpoint and use external temp sensor.

Will get more into it this weekend

Mike

Sent from my iPhone using Tapatalk

superholz · Post by **superholz** » Fri Feb 08, 2019 10:17 am

autolog wrote:Hi @superholz,

superholz wrote:... Should I adjust temperature in the TRV controller or the original TRV. ...
You should alter the temperature of the TRV Controller not the TRV. The TRV Controller will most likely ignore any setpoint adjustments made to the TRV.

superholz wrote:... I get several errors from different TRVs like this one:
TRV Error Z-Wave wakeup missed for TRV device '136 - Thermostat (Devolo 09356) Schlafzimmer', controlled by 'TRV Schlafzimmer'. Last Z-wave command received: 2019-02-08 06:41:30

I also see that temperature is not updated at the TRV. Anything I should do about it?
The TRV Controller monitors the wakeup schedule of the battery based TRVs being controlled. If a wakeup is missed then it warns you . This is important as if you had wanted the TRV setpoint to change and the TRV misses a wakeup, your setpoint change won't happen until the next wakeup.

... I would like to understand what is the technical difficulty that causes that the TRV controller misses the wake up. Furhter just curious: what happens onder the hood of you plugin when the heating is switched off. In other words, which variable/property you use to decide that the setpoint is reached?

autolog · Post by **autolog** » Fri Feb 08, 2019 10:43 am

superholz wrote:... I would like to understand what is the technical difficulty that causes that the TRV controller misses the wake up. Furhter just curious: what happens onder the hood of you plugin when the heating is switched off. In other words, which variable/property you use to decide that the setpoint is reached?

It is not a problem with the TRV Controller. It is just letting you know that the controlled TRV hasn't woken up as it should do according to its wakeup time set in its device settings.

This can happen regardless as to whether the TRV is being controlled or not. It is just that the TRV Controller is monitoring the wakeups and can therefore tell you that one has been missed.
You likely wouldn't know otherwise because Indigo doesn't warn you that it is happening.

The significance is that if for example you have a 15 minute wakeup period , then to make sure that the heating is on at 17:00, you would have to turn on the heating (i.e set the setpoint) at 16:45 just in case a wakeup happens at 16:58 in which case the next wakeup is 17:13. If this wakeup was missed then the next one is 17:28 which is almost half an hour late.

What wakeup period have you set for your TRV?

The plugin will switch off the TRV (set to minimum setpoint) once the measured temperature from the Remote (if defined) or TRV is reached. So the property is the measured temperature. This is shown in the Indigo UI and also in the custom states.

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 11:24 am

@autolog

Added New TRV Controller for Lounge Back Radiator TRV and set it up as..

: TRV2.jpeg (268.39 KiB) Viewed 3315 times

: TRV3.jpeg (152.84 KiB) Viewed 3315 times

And it immediately changed the set point 8C

: TRV1.jpeg (399.7 KiB) Viewed 3315 times

: TRV4.jpeg (169.35 KiB) Viewed 3312 times

What am I missing here?

Any ideas - how do I get it to use the set point for the current time period?

Any ideas? Thanks

autolog · Post by **autolog** » Fri Feb 08, 2019 11:42 am

It is working OK but I can see it could be / is confusing.

Thanks for providing all the screenshots - makes it easy to see what is going on.

The Remote is reading 20.2 which is above the desired setpoint of 20.0. The plugin has therefore reset the setpoint to 8 as it has turned the TRV off. and replicates this in the TRV Controller.

I will take a look at this and see what I can do to make this clearer but it probably won't be until towards the end of next week at the earliest.

It is using the setpoint for the current period because Schedule2Active is true and the schedule2SetpointHeat is 20.

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 11:43 am

How do I add a Hue Motion Detector - Temperature Sensor to the Remote Thermostat?

They are actually really good them sensors and I have them all over the house pretty much every room except bedrooms/lounge - so a good source for overall room temp.

Very reliable too, run for a couple of years without any issues on a 2 AAA batteries.

The Hue Plugin collects any changes very quickly near realtime.

siclark · Post by **siclark** » Fri Feb 08, 2019 11:43 am

Busta999 wrote:
2. Radiator Behaviour.

I have been tracking the Spirit TRV - not under TRV Controller
IMG_1138.jpg
The Valve closes as it gets near the SetPoint, meaning it can take an hour or two to hit the set point to move 1 degree.

This results in non controlled TRVs (i.e. hallway near house thermostat) in massively over running and over heating spaces i.e. running the heating system for an hour or more longer than is required.

Again - not fully into TRV Controller, yet - will it address this issue?

Less of an issue if you have a controlled TRV on every radiator - ( I currently have 8 controlled TRVs, and 20 Radiators all together)

My theory was that the toilets/bathrooms/ensuites can overheat if not on controlled TRVs, but I don't mind as I have never had anyone complain about a warm bathroom and they are usually quite small.

Yes, with the spirits you end up with a more controlled heating in each room, ie a warm radiator for 5 hours to maintain temp rather than alternating hot/cold as normal.
However as you say, this causes problems for any radiator not doing the same. Standard TRVs eliminates much of this , ie 0-5 and are cheap to fit but towel rails end up being on for a lot longer than usual. However as you say, over warm bathrooms are not a bad thing.

I used a part set up for a month until realising I needed a spirit per radiator (all except one tiny one) however I think the energy savings will cover that cost.

Sent from my iPhone using Tapatalk

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 11:45 am

autolog wrote:It is working OK but I can see it could be / is confusing.

Thanks for providing all the screenshots - makes it easy to see what is going on.

The Remote is reading 20.2 which is above the desired setpoint of 20.0. The plugin has therefore reset the setpoint to 8 as it has turned the TRV off. and replicates this in the TRV Controller.

I will take a look at this and see what I can do to make this clearer but it probably won't be until towards the end of next week at the earliest.

It is using the setpoint for the current period because Schedule2Active is true and the schedule2SetpointHeat is 20.

Excellent - I get it - the SetPoint is set low to achieve an Off - ok

Spooked me there

siclark · Post by **siclark** » Fri Feb 08, 2019 11:46 am

Yes, ignore the TRV setpoint most of the time. Just ensure the plugin thermostat device is on the right setting.

Sent from my iPhone using Tapatalk

autolog · Post by **autolog** » Fri Feb 08, 2019 11:49 am

Busta999 wrote:How do I add a Hue Motion Detector - Temperature Sensor to the Remote Thermostat?

I presume from your question that the Hue Temperature device doesn't appear in the list of remote stats? Is it a plugin device?

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 11:54 am

Hue Temp Sensors not showing up.

They are coming from the Hue Plugin.

Some of the Temp Sensors

: TRV5.jpeg (63.35 KiB) Viewed 3299 times

autolog · Post by **autolog** » Fri Feb 08, 2019 12:12 pm

Can you print out a device definition via the main plugin menu > open scripting shell. Then try:

Code: Select all

dev = indigo.devices[<ID OF SENSOR>]
indigo.server.log(u'SENSOR:\n{}'.format(dev))

This should, if I have got the code right, dump the device details to the Indigo log. I can then take a look at what needs to be done to support them.

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 12:23 pm

Code: Select all

Python 2.7.10 (default, Feb  7 2017, 00:08:15) 
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]
Connected to Indigo Server v7.2.0, api v2.0 (localhost:1176)
>>> dev = indigo.devices[<377643688>]
  File "<console>", line 1
    dev = indigo.devices[<377643688>]
                         ^
SyntaxError: invalid syntax
>>> indigo.server.log(u'SENSOR:\n{}'.format(dev))

I've got something wrong somewhere but cannot see it

autolog · Post by **autolog** » Fri Feb 08, 2019 12:32 pm

Get rid of the < and > either side of the device ID

Busta999 · Post by **Busta999** » Fri Feb 08, 2019 12:34 pm

Palm Face - Doh - my bad...

Code: Select all

address : 192.168.1.11 (SID 37)
allowOnStateChange : False
allowSensorValueChange : False
batteryLevel : 100
buttonGroupCount : 0
configured : True
description : Calibrated 22/1/19
deviceTypeId : hueMotionTemperatureSensor
displayStateId : sensorValue
displayStateImageSel : TemperatureSensor
displayStateValRaw : 23.1
displayStateValUi : 23.1 ºC
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState : 
folderId : 1455867288
globalProps : MetaProps : (dict)
     com.nathansheldon.indigoplugin.HueLights : (dict)
          SupportsBatteryLevel : true (bool)
          SupportsOnState : false (bool)
          SupportsSensorValue : true (bool)
          address : 192.168.1.11 (SID 37) (string)
          enabledOnHub : true (bool)
          manufacturerName : Philips (string)
          modelId : SML001 (string)
          nameOnHub : Hue temperature sensor 11 (string)
          productId :  (string)
          sensorId : 37 (string)
          sensorOffset : +2.6 (string)
          swVersion : 6.1.0.18912 (string)
          temperatureScale : c (string)
          type : ZLLTemperature (string)
          uniqueId : 00:17:88:01:03:2a:27:1f-02-0402 (string)
id : 377643688
lastChanged : 2019-02-08 18:31:04
lastSuccessfulComm : 2019-02-08 18:31:04
model : Hue Motion Sensor (Temperature)
name : Temp: Kitchen (Hue) - Calibrated
onState : None
ownerProps : com.nathansheldon.indigoplugin.HueLights : (dict)
     SupportsBatteryLevel : true (bool)
     SupportsOnState : false (bool)
     SupportsSensorValue : true (bool)
     address : 192.168.1.11 (SID 37) (string)
     enabledOnHub : true (bool)
     manufacturerName : Philips (string)
     modelId : SML001 (string)
     nameOnHub : Hue temperature sensor 11 (string)
     productId :  (string)
     sensorId : 37 (string)
     sensorOffset : +2.6 (string)
     swVersion : 6.1.0.18912 (string)
     temperatureScale : c (string)
     type : ZLLTemperature (string)
     uniqueId : 00:17:88:01:03:2a:27:1f-02-0402 (string)
pluginId : com.nathansheldon.indigoplugin.HueLights
pluginProps : emptyDict : (dict)
protocol : Plugin
remoteDisplay : True
sensorValue : 23.1
states : States : (dict)
     alertMode : none (string)
     alertMode.ui : none (string)
     batteryLevel : 100 (integer)
     batteryLevel.ui : 100 (string)
     lastUpdated : 2019-02-08T18:31:03 (string)
     lastUpdated.ui : 2019-02-08T18:31:03 (string)
     ledEnabled : false (bool)
     online : true (bool)
     online.ui : True (string)
     sensorValue : 23.100000 (real)
     sensorValue.ui : 23.1 ºC (string)
     temperatureC : 23.1 (real)
     temperatureC.ui : 23.1 (string)
     temperatureF : 73.6 (real)
     temperatureF.ui : 73.6 (string)
     testMode : false (bool)
     testMode.ui : False (string)
subModel : 
supportsAllLightsOnOff : False
supportsAllOff : False
supportsOnState : False
supportsSensorValue : True
supportsStatusRequest : True
version : None

Indigo Domotics

TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread

Re: TRV Controller Discussion Thread