" TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '524' has error=''zwaveWakeupIntervalRemote''
TRV Error StandardError detected in TRV Plugin [deviceUpdated] for device 'Conservatory Temperature 2']. Line '1145' has error=''remoteTempOffset''
Z-Wave received "Conservatory Humidity 2" sensor update to 24%
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '524' has error=''zwaveWakeupIntervalRemote''
Z-Wave received "Conservatory Luminance 2" sensor update to 107 lux
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '524' has error=''zwaveWakeupIntervalRemote''
Z-Wave received "Conservatory Ultraviolet" sensor update to 0
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '524' has error=''zwaveWakeupIntervalRemote''"
Looks like related to the external temp sensor used as a temp reading source
I'll take a look at that error. What sort of device/model is it?
EDIT Further Questions:
How have you defined the device in the TRV Controller, as looking at the code I can't immediately see how this can happen (though obviously it has!).
Also, the errors above are from version 1.4.3 not 1.5.0 (although that shouldn't make any difference).
It seems to be it was a mix of a partially upgraded plugin.
Made a clean install.
Now the issue is
" TRV Error StandardError detected in TRV Plugin [deviceStartComm of device 'Conservatory TRV']. Line '3136' has error='list index out of range'"
...
Z-Wave received "Conservatory Temperature 2" sensor update to 29.4 °C
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '525' has error=''zwaveWakeupIntervalRemote''
Z-Wave received "Conservatory Humidity 2" sensor update to 18%
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '525' has error=''zwaveWakeupIntervalRemote''
Z-Wave received "Conservatory Luminance 2" sensor update to 50 lux
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '525' has error=''zwaveWakeupIntervalRemote''
Z-Wave received "Conservatory Ultraviolet" sensor update to 0
TRV Error StandardError detected in TRV Plugin [zwaveCommandReceived]. Line '525' has error=''zwaveWakeupIntervalRemote''
All seems to work OK as far as my system is concerned.
If you have the delay set to 15 seconds and valve delay set to 5 seconds then to start each TRV will take 20 seconds. If you have 12 TRVs, it is going to take 12 x 20 seconds = ~ 4 minutes to complete and any new changes (e.g. turn on a TRV) will be queued up behind the initial start.
I will do a more general announcement once I am happy it appears to be working OK.
Hi Jon, not sure I entirely understand the second time but used your example times and it is all working, and I seem to have less zwave delays when all are reporting status, but will keep an eye on it over the next few days.
siclark wrote:... not sure I entirely understand the second time but used your example times and it is all working, ...
When the the TRV is off and not calling for heat, the plugin only ask the TRV for temperature. In heating mode it asks for Temperature and Valve percentage open state. So the second time is just a mechanism to get the results back quicker as a pair for each TRV if that makes sense?
The Thermostat - zwave Secure - was working and reporting temp correctly
The TRV controller was not reading the external thermostat and keeping both heat demand keeping the control heating on.
I will work on a trigger where the actual Thermostat is different from where the TRV Controller is showing a different remote temp and see how often this is occuring.
I think there is a bug using a pibeacon one wire sensor as the TRV remote control. That device has Temperature as the state, as well as some max and min values.
The current temp on my pibeacon device is 23.5 but with a max of 28.6.
Screenshot 2020-05-22 at 14.30.26.png (32.48 KiB) Viewed 6177 times
The TRV temp is 24.5 degrees at the moment (they are other sides of the room)
Screenshot 2020-05-22 at 14.31.50.png (166.85 KiB) Viewed 6177 times
However when I set the TRV controller to use the pibeacon as the TRV remove control, the TRV reports the temperature as>28. Except now I repeat for taking screenshots it has done the opposite, and is showing a TRV temperature of 20.3, I have no idea where its getting that from.
Screenshot 2020-05-22 at 14.35.33.png (167.99 KiB) Viewed 6177 times
In this case, the wrong TRV temperature is not a problem, as the used temp of the remote is correct.
However I was seeing the reported temperature of the TRV controller, ie using the TRV remote of 28 degrees which is clearly wrong.
UPDATE - turns out the temperature of the TRV really did drop 4.2 degrees inbetween the snapshots as the window was opened.
I cant get it to replicate the behaviour now but below is my plot of the temperatures.
Orange is the reported TRV controller temp with the pi beacon as TRV remote uo the point it drops from 29 degrees.
Red line is the pibeacon temperature.
At approx 14:18 I stoped it using the TRV remote and it dropped to 20c. When I then put it back to using the TRV remote it reports a temperature almost inline., (exactly after 14:30).
Screenshot 2020-05-22 at 14.45.15.png (76.22 KiB) Viewed 6175 times
I dont have debugging turned on, so not sure there is anything you could get for this without it occuring again, but wondered if you had seen this before?