TRV Controller Discussion Thread

... Tried it and it does not seem to work. The setpoint set at the trv is not taken over by the TRV controller. Instead it seems that the old setpoint is lost and set to minimum temperature (4°C).

What is the custom state controllerModeUi set to after you do this?

Hi, sorry, my Z-wave network died and I had to rebuilt it... now picking up this point: where do i find this property? I have no property list at the device as sometimes seen here in screenshots.

Hi.... yes I found it .

When I change manually the temperature at the device the parameter variable changes from:
controllerModeUi = UI Control
controllerModeUi = TRV UI Control


I have some more issues/questions.
Some of the controlled thermostats show strange behavior. They almost t continuously open en close the valve. I think it has something to do with switching around the set point maybe does to the fact that the temperature measurement arbitrary gives values with small changes with trigger the valve(?). Any parameters I could set to improve it?

The strangest is actually that the target TRVs are switched off even when the target temperature was never reached.

Not sure what to suggest with this.

I probably need more data from the log but that will produce a lot of output - you could PM me with the info. Turn on debugging for General & TRV Handler (not Method Trace) - reload the plugin and then try and produce the scenarios you are describing. I can look at the log and see what I can spot.

You get to the log by clicking on Show Event Logs Folder in the Indigo Event Log window. The log is plugin.log in the com.autologplugin.indigoplugin.trvcontroller folder.

Anyone found a way to get the Spirit to report true battery level after you have replaced the batteries.

I had put the ones shipped with the Spirit and after a prolonged period of heavy monitoring the batteries dropped to 20%.

Looks like it only reports battery levels once every 24 hours.

Anyway to expedite that?

I have put a trigger in place that sets an alert if any of the batteries drops below 21%, but cannot silence the alert while the the Spirit continues to report 20% battery despite having new batteries.

Any ideas?

Thanks

Yes - try restarting the Indigo server as it is Indigo requesting the battery state which I think it will do when it restarts.

Been wondering how to do that as well! Thanks


Sent from my iPhone using Tapatalk

Not so much .......

Restarting Indigo did not refresh battery level.

Unless the new batteries I put in are at 20% also, a possibility but unlikely.

Are you looking at the battery level of the actual Spirit TRV device i.e. not the TRV Controller device?

Both

Did you see your battery finally report? Mine seems to have the day after replacing them. Fresh rechargeables showed 76%

Did you see your battery finally report? Mine seems to have the day after replacing them. Fresh rechargeables showed 76%

You are using rechargeables - I thought that was a major no no for these as the needed the full 1.5v and not the usual 1.2v given by rechargeables.

Has anyone sen the battery drain on these yet?

I am a bit concerned, anadotically, they appear to go down quite fast - I have put a graph on them all so can track usage better., and dating when I put fresh ones in.

@autolog - anyway you could reduce the valve activity - particularly the forced up and downing at midnight and the 10 min gap between schedules ?

May not be an issue - just a thought.

Only since I changed then first time last week. Testing and seems to work but not sure how long they will last.
My guess to improve battery life is to turn off valve reporting or at least only report at 10 or 20% changes. Not 1% that I guess most of us do.


Sent from my iPhone using Tapatalk

... @autolog - anyway you could reduce the valve activity - particularly the forced up and downing at midnight and the 10 min gap between schedules ? ...

It's possible and something that is on my list to look at.

I am thinking that there might be two modes of scheduling: 1) the current implementation i.e. with up to four on/off times and 2) a new scheduling mode: just specify times and Heat Setpoints, say a list of up to 8 or 10. This second option would mean there wasn't a gap. It's do-able but not a high priority for me at the moment. I'll add it to the list.

I doubt a single valve movement does much when the valve is constantly changing whenever heat is required?



Sent from my iPhone using Tapatalk

Ok did some graphing on the Spirit TRVs.

Battery is reported at midnight daily, well most days sometimes it gets 'lost'

Now set up a graph that records all the Spirit TRVs for 240 days one reading a day, that should gibe us some stats.

TRVs are setup as-

Polling Minutes [Schedule Active] 5
Polling minutes [Schedule Inactive] 20
Polling Minutes [Schedules Not Enabled] 30

Following enabled
Exclude requesting thermostat mode during poll
Exclude Requesting set point during poll
Hide temperature message broadcasts in Event log

Following disabled
Exclude requesting temperature sensor during poll


Auto - off LCD 5 Seconds
Temp Sensitivity 2
Valve reporting 10

@autolog any other recommended changes/config?