hmm - might be a bug.
I will check that out ASAP.
Could you provide a little more info though please?
Are you meaning when you send a input to remove a schedule or from the node-red editor (clicking the X button next to a schedule)
A screenshot of the issue would help.
Thanks
This is the error message.
The error only appears when I remove it by sending an input.
This is an example flow where I get the error:
[{"id":"23215510.964f8a","type":"inject","z":"94636032.af22e","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":600,"y":1560,"wires":[["1a32bcfc.783c13"]]},{"id":"1a32bcfc.783c13","type":"function","z":"94636032.af22e","name":"remove","func":"\nmsg.topic = \"remove-all\"\nreturn msg;","outputs":1,"noerr":0,"x":740,"y":1560,"wires":[["9feedc46.48d26"]]},{"id":"9feedc46.48d26","type":"cronplus","z":"94636032.af22e","name":"","outputField":"payload","timeZone":"","persistDynamic":true,"commandResponseMsgOutput":"output1","outputs":1,"options":[],"x":920,"y":1560,"wires":[["90acf197.65bd5"]]},{"id":"8a67e9f2.d734f8","type":"inject","z":"94636032.af22e","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":600,"y":1520,"wires":[["95c54991.dde7a8"]]},{"id":"95c54991.dde7a8","type":"function","z":"94636032.af22e","name":"add","func":"msg.payload= [\n {\n \"command\": \"add\",\n \"name\": \"every 6\",\n \"expression\": \"*/6 * * * * * *\",\n \"expressionType\": \"cron\",\n \"payloadType\": \"default\",\n \"limit\": 3\n },\n {\n \"command\": \"add\",\n \"name\": \"alarm1\",\n \"expressionType\": \"solar\",\n \"solarType\": \"selected\",\n \"solarEvents\": \"sunset\",\n \"location\": \"54.999320540937035 -1.417407989501953\",\n \"offset\": \"-60\",\n \"payloadType\": \"str\",\n \"payload\": \"In 60 mins, it will be a great time to take photographs\",\n \"limit\": null\n }\n]\nreturn msg;\n","outputs":1,"noerr":0,"x":730,"y":1520,"wires":[["9feedc46.48d26"]]},{"id":"208694cc.79be2c","type":"function","z":"94636032.af22e","name":"status","func":"\nmsg.topic = \"status-all\"\nreturn msg;","outputs":1,"noerr":0,"x":730,"y":1600,"wires":[["9feedc46.48d26"]]},{"id":"7a664441.4f8f6c","type":"inject","z":"94636032.af22e","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":600,"y":1600,"wires":[["208694cc.79be2c"]]},{"id":"90acf197.65bd5","type":"debug","z":"94636032.af22e","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":1070,"y":1560,"wires":[]}]
Thanks for the info - it is now fixed and published 
Fortunately, the bug was cosmetic (for updating node status) so operationally, there was no problem.
PS, your test flow can be simplified to this (apologies if i'm teaching you to suck eggs)...
[{"id":"bcda75bf.c394a8","type":"inject","z":"21106466.70e60c","name":"remove-all","topic":"remove-all","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":980,"y":280,"wires":[["a2299126.371a3"]]},{"id":"a2299126.371a3","type":"cronplus","z":"21106466.70e60c","name":"","outputField":"payload","timeZone":"","persistDynamic":true,"commandResponseMsgOutput":"output1","outputs":1,"options":[],"x":1200,"y":280,"wires":[["9aacf955.869d18"]]},{"id":"b4d98f36.29cea","type":"inject","z":"21106466.70e60c","name":"add 2 schedules","topic":"","payload":"[{\"command\":\"add\",\"name\":\"every 6\",\"expression\":\"*/6 * * * * * *\",\"expressionType\":\"cron\",\"payloadType\":\"default\",\"limit\":3},{\"command\":\"add\",\"name\":\"alarm1\",\"expressionType\":\"solar\",\"solarType\":\"selected\",\"solarEvents\":\"sunset\",\"location\":\"54.999320540937035 -1.417407989501953\",\"offset\":\"-60\",\"payloadType\":\"str\",\"payload\":\"In 60 mins, it will be a great time to take photographs\",\"limit\":null}]","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":1000,"y":240,"wires":[["a2299126.371a3"]]},{"id":"85038c59.6f9e3","type":"inject","z":"21106466.70e60c","name":"status-all","topic":"status-all","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":980,"y":320,"wires":[["a2299126.371a3"]]},{"id":"9aacf955.869d18","type":"debug","z":"21106466.70e60c","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":1330,"y":280,"wires":[]}]
Thanks a lot for the quick fix.
Yeah for some reason I use function nodes far more often than necessary, always happy about tips to simplify stuff 
@Steve-Mcl Hi Steve, I just upgraded to latest cron+ from pre 1.0, and I should have written down the previous version but obviously didn't... Viewing the editor on Firefox 76 (I know, I should update to latest firefox) on macbook pro, resolution about 1400xsomething I forgot what exactly. Tried to do a couple quick updates to a flow so it could better support me during my sickness. Turns out that was too easily thought...
Redacting the schedule names, here's the misbehaving node instance:
[{"id":"a104913f.0bb62","type":"cronplus","z":"d83aa04f.39ec3","name":"Reminders","outputField":"payload","timeZone":"Europe/Amsterdam","persistDynamic":false,"commandResponseMsgOutput":"output1","outputs":1,"options":[{"name":"drink_water","topic":"drink_water","payloadType":"json","payload":"{\"notificationName\":\"DrinkWater\",\"status\":\"NEW\"}","expressionType":"cron","expression":"0 0 9,11,13,15,17,19,21 * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"medication_foo","topic":"medication_foo","payloadType":"json","payload":"{\"notificationName\":\"medication\",\"status\":\"NEW\"}","expressionType":"cron","expression":"0 0 9 * * 3 *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"medication_foo","topic":"medication_foo","payloadType":"json","payload":"{\"notificationName\":\"medication\",\"status\":\"NEW\"}","expressionType":"cron","expression":"0 0 19 * * 6 *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"schedule4","topic":"medication_bar","payloadType":"json","payload":"{\"notificationName\":\"medication\",\"status\":\"NEW\"}","expressionType":"cron","expression":"0 0 9 * * * * ","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}],"x":150,"y":180,"wires":[["4e0abfe4.031448"]]}]
Only thing I can think of is that there's two schedules with the same name and topic in there, with a different cron schedule. It's for a set of medication that has to be taken at two moments a week, one day in the morning, the other in the evening. I seem to remember that in the first versions of this flow I had the names marked with a day-of-week suffix, but I don't see them in this export nor in the flow. As for the last one, the name showing up in the editor is not schedule4, but medication_bar, so that's odd too. Otherwise I don't know what's going on.
Oh, running on NR 1.1.2, Node v10 LTS, Pi 3B+ Buster
After fixing the scheme names to have them back at the dow suffix the error is gone, but nothing showed in the editor that there was an error in the first place.
Hi Lena.
Yeah, its on my todo list 
- well, actually, its OK on my installation so I might have it resolved already. Please just close your eyes and pretend you didnt see it 
Close - its the names on multiple schedules that must be unique. This uniqueness is required for permitting a dynamic modification (NOTE: the topic can be duplicated). It was actually a long standing bug (you could have 2 names the same but not addresses the 2nd one via dynamic control) so it was necessary to have name and topic separate things (separate name/topic was also a request by xxx (i forget))
Yeah - not ideal (there is a console warning) but I haven't found a nice easy way of marking the editableList items as having validation issues.
Will try to remember this next time I am amongst the code (or if you could raise an issue?)
Lena, I have pushed an update (V1.0.7) to the flows library that slightly improves the situation.
There are a few other UI tweaks to try and be more in line with core nodes.
EDIT: Note the cron expression widget is now fixed too (must go back and check node-red version before the typedInput resizing method was changed as this now looks OK in V1 - but suspect it might be messed up in older node-red versions)
Just published Update V1.2.1
Notable additions since last publish...
So amazing!!!!
Is there a way to have cron plus start on a date range from sunrise to sunset? I see that I can choose cron or solar. What I would like to do is create holiday lights. So, for Christmas, have my lights only be active from say 12/1/2020 to 1/1/2021 but actually turn on from sunset to sunrise during this time.
Any help is greatly appreciated.
How I handle that is to add another global variable based on Seasons (I change mine manually but you could do it based on date). My flows then have season checkpoints so I can have different timing for Christmas vs. summer vs other specific times of the year.
That is quite simple in many different ways. Here is a very basic way...
[{"id":"d84f7031.2e962","type":"cronplus","z":"c40b7683.6e65e8","name":"","outputField":"payload","timeZone":"","persistDynamic":false,"commandResponseMsgOutput":"output1","outputs":1,"options":[{"name":"schedule1","topic":"schedule1","payloadType":"default","payload":"","expressionType":"solar","expression":"0 * * * * * *","location":"54.99911630747018 -1.4171075820922852","offset":"0","solarType":"selected","solarEvents":"sunrise,sunset"}],"x":230,"y":160,"wires":[["ce8af392.f8ffb"]]},{"id":"ce8af392.f8ffb","type":"function","z":"c40b7683.6e65e8","name":"is december?","func":"var now = new Date();\nif(now.getMonth() == 11) {\n return msg;\n}\n","outputs":1,"noerr":0,"initialize":"","finalize":"","x":440,"y":160,"wires":[["557a65c9.a5c49c"]]},{"id":"557a65c9.a5c49c","type":"debug","z":"c40b7683.6e65e8","name":"do stuff with xmas lights","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":690,"y":160,"wires":[]}]
Thank you for your help. I am new to node red and coding. I never thought to use a function node. I used your function node to learn a little more about Javascript. I have also learned more about function nodes too. I was able to get it to work. Out of curiosity, why are you not able to use the cron settings and solar selections at the same time?
I have been playing with that in my head for some time however, i always ends up at the same conclusion...
Late to the party, but if you need another vote, for the @sunrise and @sunset logic or feature... I could really use that for some of the stuff I am doing with various sensors. Just as capturing the light level locally at the actual projected sunrise and sunset. Also, triggering irrigation at sunrise and/or sunset for example.
Thats entirely possible as is though isnt it?
OR if a sensor value can be requested...
I dont doubt there are improvements to be made but as it stands there is very little you cannot do & I dont want to add even more complexity.
Just to mention, if the need is to do everything in one single node, we also have the BigTimer able to do what was originally requested. In the settings you can configure actions for sunset/sunrise and in addition configure the active months. As well as week days and much more
But as you say, over-reaching is no good
I am not suggesting that cron plus read any sensors.... not sure how that was introduced, it was just an example of how such could be done, and is often done, in some projects.
May intent was to have cron-plus have a defined trigger for @sunset and @sunrise. It would be nice to just have the feature, @sunrise do Y, and @sunset do X type of thing as part of the cron plus. Thus the operator would not have to develop any flow logic or such on their own to have such triggers, or even pull in yet another node, i.e. big timer, when cron-plus is already desired..
I solved the need by doing a query to weather report source, which I already had logic for already, grabbed the sunrise and sunset values from said report, was easy to do... but not as easy as if cron plus node did it, hiding the complexity of such.
Since you asked for input, that was what I thought would be useful, as a future feature of cron-plus, at least to me, if not others.
There are already several suncalc specific nodes. Why does this need to be added to this one ? You would need to configure it with location adding yet more ui.
I'm not sure who misunderstood who here but just for clarity, there is already sunse, sunset, dusk, dawn etc that can trigger whatever you want. And it doesn't need to go out to the internet as it is calculated internally, and my response was based on your question about "triggering irrigation at sunrise and/or sunset for example."
The prior poster was asking about the ability to limit solar events between dates and asked for it to be built in to which I said I was open to suggestions.
So either I misunderstood you (and thus suggested what you suggested was already possible) or you misunderstood that solar events are already entirely possible.
Either way, I hope you don't miss the point that I am grateful of your input and suggestions regardless of who is misunderstanding who 
Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy
