Hmm, that might be the start of your issue I'm afraid. The library is generated automatically by and large. Just because a package exists doesn't mean that it works or that it works well.
Clearly there are not many people in this forum using it. The library has a star rating and you could raise an issue on the github repo.
I've seen worse reasons
Woah there cowboy, steady on. There are a lot of us here who have spent countless hours of our personal time helping others of all abilities and knowledge levels.
But we all have limited time and energy so have to pick and choose what to spend time on. That you wish to expand your knowledge by working with this node is great - but that doesn't mean that we wish to do the same.
I have not looked at that node as a primary criteria is it must be done via the UI. My wife has to be able to set the schedule and I had used another node in my first program (I can't recall the node now) that also couldn't use a UI. Needless to say the wife absolutely threw a fit about having to use a programmer and all. The sad part of it is she was absolutely right. Because I couldn't or wouldn't make it a user friendly interface was no reason for her to have to put up with it. So, I'm having to modify the program to make it user friendly.
I was thinking of something that would pass the family-friendly test However, that is a starting point. I think that Lena was saying she had something that might be wrangled to usability.
I have indeed, though itās more like a sketch on paper I still have to turn into an interface. From there on itās usually a day or two before Iāve something working. Wonāt be today that I can show a rough example; working on food experiments in the kitchen rather than node-red experiments today.
No need. One of the functions of the node is "describe". You can send a control message to cron-plus node and get back a human readable description. It's all there in the built in help and importable example flow.
I did a sample back home where a text input "on change" triggered a control msg to "describe" the expression and fed that back to a ui_text. All fairly simple.
I think what @bakman2 was suggesting was to use something like that for a configurable interface on dashboard level so you wonāt have to dive into the flow/node configuration to edit the schedule when cron-plus already allows you to send schedule changes through a command
This however makes that even better. Amazing node, once again!
However, that is a starting point. I think that Lena was saying she had something that might be wrangled to usability.