TRV Beta Feedback Thread
Re: TRV Beta Feedback Thread
Still to load the latest version but it's it possible to turn all the messages off in the log? With 7 Spirits now the log is getting filled get quickly. I have the config debug box unticked.
Cheers.
Sent from my iPhone using Tapatalk
Cheers.
Sent from my iPhone using Tapatalk
Re: TRV Beta Feedback Thread
Looks like a bug.siclark wrote:Still to load the latest version but it's it possible to turn all the messages off in the log? With 7 Spirits now the log is getting filled get quickly. I have the config debug box unticked.
On grandson duty today but will take a look at it tomorrow.
Re: TRV Beta Feedback Thread
Hi Simon,
Turning the Debugging [Enable debugging options.] off i.e. unchecked, results in a message in the log of 'No debugging requested for TRV plugin' and no debug messages are produced.
Can you double check what your log says when you perform the same action i.e. turn it off?
Thanks.
I have just tried to reproduce this problem and failed which is another way of saying it works OK for me.autolog wrote:Looks like a bug.siclark wrote:Still to load the latest version but it's it possible to turn all the messages off in the log? With 7 Spirits now the log is getting filled get quickly. I have the config debug box unticked.
Turning the Debugging [Enable debugging options.] off i.e. unchecked, results in a message in the log of 'No debugging requested for TRV plugin' and no debug messages are produced.
Can you double check what your log says when you perform the same action i.e. turn it off?
Thanks.
Re: TRV Beta Feedback Thread
First update of the new year, I have uploaded BETA V1.1.11
This is the list of changes:
This is the list of changes:
- CSV Files were being restricted to one entry as the truncating by number of hours wasn't working correctly - now corrected!

Re: TRV Beta Feedback Thread
Evening I upgraded to 11 anf tried ticking and unticking the box but still get log entries.
Any ideas?
Sent from my iPhone using Tapatalk
Any ideas?

Sent from my iPhone using Tapatalk
Re: TRV Beta Feedback Thread
The messages are coming from Indigo (ZWave) when it sends and receives z-wave commands to the Spirits. The messages are not being output by the TRV plugin logging. Obviously, the TRV plugin is issuing the ZWave commands either directly via raw z-wave commands or indirectly by Indigo thermostat commands in order to monitor and control the Spirits.siclark wrote:Evening I upgraded to 11 anf tried ticking and unticking the box but still get log entries.
Any ideas?
I am not sure that they can be suppressed. In the Spirit device settings, you could try ticking/checking the Hide temperature message broadcasts in Event log which may help.
However, it looks like there needs to be another option to suppress Valve Messages added to the Indigo definition for a Spirit.
btw - Looks like your iPhone needs charging
Re: TRV Beta Feedback Thread
Morning, or is it still night?
It's not just the valve received status is all the status requests as well.

All adds up to a lot of rows every few minutes.
Is this an indigo change to stop logging these messages?
I do have the hide temperature messages broadcast from log ticked but do we need option to hide more?
Cheers.
Sent from my iPhone using Tapatalk
It's not just the valve received status is all the status requests as well.

All adds up to a lot of rows every few minutes.
Is this an indigo change to stop logging these messages?
I do have the hide temperature messages broadcast from log ticked but do we need option to hide more?
Cheers.
Sent from my iPhone using Tapatalk
Re: TRV Beta Feedback Thread
Just posted a BETA update - Version 1.1.12
This version has the following changes:
) that is displaying the CSV data produced by the plugin for a TRV Controller device:
My Control panel setup has a list of rooms and selecting (in this example) the Dining Room links to a specific Control panel page giving details of the dining room and displaying the graph as a refreshing image. On the parent control page, I set two server actions: the first to update All the CSV files for the device and the second to redraw the Matplotlib graph with a delay of three seconds.
Hope this might be a useful use case.
This version has the following changes:
- In the TRV Controller device settings a new option to Update All CSV Files. When this option is checked all the relevant CSV files for the device will be updated when any one of the states being output to the CSV file changes. This can help create a consistent graph.
- A new Action: Device Actions > TRV Controls > Update All CSV Files - This will force an update of the CSV files for the device with current state values. This can be useful when displaying a graph in a Control Panel as it will make sure the data is up-to-date.
- In the TRV Controller device settings a new option to define Device Start Heat Setpoint Method - This can be one of three values:
- Device Setpoint Minimum - will set the Heat Setpoint to the minimum off temperature [Default if not previously set]
- Leave As Is - will leave the Heat Setpoint at whatever the value is at the moment
- Specify Setpoint - Enable you to enter a specific temperature for the Heat set point in the Default Device Start Setpoint field.
- In the TRV Controller device settings a new option to specify Valve Assistance - If the TRV supports Valve Commands, selecting this option can help expedite the response of the TRV to a setpoint change and also help ameliorate the situation where the TRV sometimes gets into a false state e.g. says it is off when the valve is still open. The plugin default setting is ON.
My Control panel setup has a list of rooms and selecting (in this example) the Dining Room links to a specific Control panel page giving details of the dining room and displaying the graph as a refreshing image. On the parent control page, I set two server actions: the first to update All the CSV files for the device and the second to redraw the Matplotlib graph with a delay of three seconds.
Hope this might be a useful use case.
Re: TRV Beta Feedback Thread
Hi Jon,
Any chance I could test your new plugin? I'm down to my last two Stella-Zs, and one of them is starting to miss updates. They've been my worst purchase. I've one Spirit that has been in its box for a year that I could replace it with.
I think our house knows that we plan to move - it's killing the Stella-Zs, and I've had a Fibaro dimmer relay fail and randomly turn on and off. Not fun at three in the morning. Had rip it out before the other half return from the US.
Thanks,
Simon
Any chance I could test your new plugin? I'm down to my last two Stella-Zs, and one of them is starting to miss updates. They've been my worst purchase. I've one Spirit that has been in its box for a year that I could replace it with.
I think our house knows that we plan to move - it's killing the Stella-Zs, and I've had a Fibaro dimmer relay fail and randomly turn on and off. Not fun at three in the morning. Had rip it out before the other half return from the US.
Thanks,
Simon
Re: TRV Beta Feedback Thread
Yes, no problem - PM sent.Shutter wrote:... Any chance I could test your new plugin? ...
Re: TRV Beta Feedback Thread
Thanks Jon.
Simon
Simon
Re: TRV Beta Feedback Thread
New version (v1.1.14) uploaded to normal location.
Minor changes in this version:
Minor changes in this version:
- Modified the CSV retention process to create an entry for the start of the period based on the last entry dropped off. This is done to ensure that there is a data value for a state at the start of the period being graphed.
- Minor code enhancements.
Re: TRV Beta Feedback Thread
Just a quick update on the next version that I hope to upload by the end of the week.
I have been hard at work on the documentation.
I have discovered that doing this is a really good way of ironing out idiosyncrasies and bugs in the plugin.
I also got sidetracked on adding a new feature which is to create CSV output files from the PostgreSQL Indigo device history log.
This new feature works in a different manner to the existing CSV creation. The existing CSV processing updates the CSV file whenever one of the five monitored states changes.
The additional PostgreSQL CSV feature creates the CSV files from scratch and on demand. This is potentially more efficient as you don't need to create the CSV files until you actually need them. The Action to do this also allows you to override the default retention period. So you could create data for example 24, 12, 6 and 3 hours.
I drive this processing from Control Pages. I have a master page with the list of thermostats and clicking on one of the thermostats links to the relevant thermostat page with a server action to create the CSV files and then 3 seconds later to create the Matplotlib chart. This is displayed on the individual thermostat page as a refreshing image. I haven't done this yet but you could have buttons underneath the chart with say 24 / 12 / 6 / 3 and clicking on these buttons would recreate the CSV data accordingly.
I haven't done any of the processing to support SQLite as I am not using it but I could add that in due course.
To support this new CSV processing, I have had to change the plugin config and the TRV Controller device settings. So these will need to be edited and saved when the new version is installed in order to select the appropriate options (even if you intend to leave as is).
I just need to add this to the documentation and then complete a final bit of testing and I will then make it available.
I have been hard at work on the documentation.
I have discovered that doing this is a really good way of ironing out idiosyncrasies and bugs in the plugin.
I also got sidetracked on adding a new feature which is to create CSV output files from the PostgreSQL Indigo device history log.
This new feature works in a different manner to the existing CSV creation. The existing CSV processing updates the CSV file whenever one of the five monitored states changes.
The additional PostgreSQL CSV feature creates the CSV files from scratch and on demand. This is potentially more efficient as you don't need to create the CSV files until you actually need them. The Action to do this also allows you to override the default retention period. So you could create data for example 24, 12, 6 and 3 hours.
I drive this processing from Control Pages. I have a master page with the list of thermostats and clicking on one of the thermostats links to the relevant thermostat page with a server action to create the CSV files and then 3 seconds later to create the Matplotlib chart. This is displayed on the individual thermostat page as a refreshing image. I haven't done this yet but you could have buttons underneath the chart with say 24 / 12 / 6 / 3 and clicking on these buttons would recreate the CSV data accordingly.
I haven't done any of the processing to support SQLite as I am not using it but I could add that in due course.
To support this new CSV processing, I have had to change the plugin config and the TRV Controller device settings. So these will need to be edited and saved when the new version is installed in order to select the appropriate options (even if you intend to leave as is).
I just need to add this to the documentation and then complete a final bit of testing and I will then make it available.
Re: TRV Beta Feedback Thread
Jon
Sent you a PM a couple of hours ago, not too sure how this works as it is still sitting in Outbox and not sent yet so not sure if it has gone through.
Can you add me to the Beta list for this I am using 6 Spirit TRVs right now.
Thanks
Mike
Sent you a PM a couple of hours ago, not too sure how this works as it is still sitting in Outbox and not sent yet so not sure if it has gone through.
Can you add me to the Beta list for this I am using 6 Spirit TRVs right now.
Thanks
Mike
Last edited by Busta999 on Sun Feb 03, 2019 9:41 am, edited 1 time in total.
Re: TRV Beta Feedback Thread
I setup graphing on how the Spirits performed three of the TRVs.
I thought it was quite enlightening about how they work.
Only the first 24 hrs of report so far.
** These are designed for display on a black background so legend doesn't show up well on this.
Red is setpoint, yellow actual temp in room, pink purple at the top is reported TRV Temp, pic/purple at bottom is Radiator Valve %
This is using DaveL's Matplotlib plugin
I was struggling to understand why the valve was changing when the temp had not been reached, but with the graphs you can see what it is doing.
I'm impressed
I thought it was quite enlightening about how they work.
Only the first 24 hrs of report so far.
** These are designed for display on a black background so legend doesn't show up well on this.
Red is setpoint, yellow actual temp in room, pink purple at the top is reported TRV Temp, pic/purple at bottom is Radiator Valve %
This is using DaveL's Matplotlib plugin
I was struggling to understand why the valve was changing when the temp had not been reached, but with the graphs you can see what it is doing.
I'm impressed