- This topic has 2 replies, 2 voices, and was last updated 5 days, 2 hours ago by
.
-
Posts
-
When I look at my logs (timeline), I noticed that if I do a “Run-once Program” then it shows on the log-timeline as expected. However, if I do a “Run-once Program” and use the repeat feature then the first run shows on the timeline as expected with a green bar and ‘Run-once’ label. However the subsequent repeated run shows a blue bar with a label of whatever the the name of my first Program is (or if I don’t have any Programs defined then it just has a ‘Program1’ label). Shouldn’t the subsequent repeated runs of a “Run-once Program” still show a green bar with “Run-once Program #2” or something? I’ve attached a picture that has my Run-once Program and 2 repeats.
Or am I misunderstanding something?
Attachments:
To implement Run-once with repeat, the firmware has to create a temporary (one-time) program so it can store the water times to support repeats. The log currently only stores the program index and not the program name itself (due to limited storage). As a result, when you view logs, it will end up pulling the name of the wrong program because the temporary program is already deleted. So yes this is a bug/glitch, due to the way the log data is stored. In a similar way, if you run a regular program a few times but then delete that program, then when you view logs, it will end up showing the wrong program name because the correct program name is already deleted.
One work-around is to set up a notification method, like Email, MQTT, or IFTTT, and enable at least the Program Start event. This way, when a program starts, you will get a notification with the correct program name. Because the notification is sent in real-time when a program starts, it always carries the correct program name, so that eliminates the issue of storing a program index and later pulling a stale program name if that program is deleted.
The first run of a Run-Once program is handled separately – it stores a special program index so the log knows it’s a run-once program. But the subsequent runs all rely on the temporary program that’s created and stored in flash. I think one way to address this issue is to check the program name when the program starts – if it’s named “Run-once with Repeat”, then when it’s logged, use the special program index to mark it as a run-once program. This way it will always be shown as Run-once instead of the incorrect program name. I will put this on the todo list.
- You must be logged in to reply to this topic.