Please disregard the post. I was premature. It is late tonight and I forgot that the fix will be coming out in the next beta or full release of the core HS3 program. It is not Z-Wave specific, it will be for all devices. It should be out soon.
I just wasn't thinking clearly.
I probably should have deleted this post, but then it messes up the context of the next post.
There will be a workaround for this in the next update to the core HS3 program. In the device Configuration tab. The very bottom checkbox will be "Do not update last change time if device value does not change". That will stop the date from changing with polling.
The reason for the problem began when the program was updated to to properly report a "set" action when the value isn't changed several months ago. The unintended consequence is that some devices report as if they have been set even when just polled. That is why it will be a user selectable option. If you want a device to report a change when set but not changed then don't select the option.
I just wasn't thinking clearly.
I probably should have deleted this post, but then it messes up the context of the next post.
There will be a workaround for this in the next update to the core HS3 program. In the device Configuration tab. The very bottom checkbox will be "Do not update last change time if device value does not change". That will stop the date from changing with polling.
The reason for the problem began when the program was updated to to properly report a "set" action when the value isn't changed several months ago. The unintended consequence is that some devices report as if they have been set even when just polled. That is why it will be a user selectable option. If you want a device to report a change when set but not changed then don't select the option.
Comment