Announcement
Collapse
No announcement yet.
Filter Change Needed Has Bizarre Date
Collapse
X
-
Yes, there is a HS script function to change the "Last Change Date" (if that's what it is). Look in the help doc under Scripting.
Parms are device reference id and date-time.
ex:
hs.SetDeviceLastChange(5678, Now)
hs.SetDeviceLastChange(5678, Convert.ToDateTime("1/1/13 4:00 PM"))Regards,
Michael
HS3, W10 Home, HSTouch, W800, Z-Stick+
-
Originally posted by mmn View PostYes, there is a HS script function to change the "Last Change Date" (if that's what it is). Look in the help doc under Scripting.
Parms are device reference id and date-time.
ex:
hs.SetDeviceLastChange(5678, Now)
hs.SetDeviceLastChange(5678, Convert.ToDateTime("1/1/13 4:00 PM"))
Comment
-
Originally posted by cowinger View Post
I am not sure that is what it is. In the pic those are child devices of the BLStat plug-in that automatically come in when you check the box in settings to create HS devices. So not sure.Regards,
Michael
HS3, W10 Home, HSTouch, W800, Z-Stick+
Comment
-
Thanks Blade. Also when I set the number of days to a different number other than 30 (60) and save it does not change the child device. How do I get this to change? thanks
EDIT: I just ran the script in Setup, Control Panel and no change. Is that the right place? Don't know much about scripts.
Comment
-
Originally posted by Blade View PostIf you run it from the Control Panel run it like this:
Code:&nhs.PluginFunction("BLStat", "", "ResetFilterDateToNow", Nothing)
Comment
-
OK turn on debug logging and then set the value and save it
Once done turn off debug logging and attach the debug log zipped
Make sure you run this first
https://forums.homeseer.com/forum/3r...-debug-logging
Comment
-
That is not the date a filter change is needed, it is the last date/time the virtual device was controlled by HomeSeer. Since it has never been set, that date lingers from when the plug-in created it. It is likely just an anomaly in how Blade’s plug-in created the device. Just disregard it. Mine has the same date. I don’t use filters, so I set the filter change interval at 365 days and have reset it several times. Mine is currently showing 102 days until a filter change is due. Yours shows to be due on 11/28/18 (25 days). I would expect the device to change from “not set” to something else on the 28th. Why don’t you wait until then and see what happens. Alternately you could change the “Number of days for filter change” to 1 and see if it changes tomorrow or Tuesday. The virtual device has no status text assigned, so it is likely the plug-in will set the string when a change is due. It also may change the value of the device to 1 or 100. It appears Blade wants you to assign an Event or script to be run when the filter change is due, so the virtual device is only for informational purposes.
As I wrote, I have no need for that feature, because we have radiant heat and no air handler.
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by Blade View PostOK turn on debug logging and then set the value and save it
Once done turn off debug logging and attach the debug log zipped
Make sure you run this first
https://forums.homeseer.com/forum/3r...-debug-logging
BLStat-Detailed.zipAttached Files
Comment
-
Originally posted by Blade View PostI do not see any errors updating the number of days
Can you post your BLStat.xml zipped
Comment
-
Originally posted by cowinger View Post
Thanks Randy. I will put the file here anyway for Blade to look at. There is still one issue not resolved and that is the number of days remaining is not changing in the child device when you change it in settings.
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
Comment