# Node-red-contrib-simpletime enhancement

**URL:** <https://discourse.nodered.org/t/node-red-contrib-simpletime-enhancement/29069>\
**Category:** Developing Nodes\
**Created:** [23 June 2020 12:38 UTC](https://discourse.nodered.org/t/node-red-contrib-simpletime-enhancement/29069 "2020-06-23T12:38:30Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [30 June 2020 20:15 UTC](https://discourse.nodered.org/t/node-red-contrib-simpletime-enhancement/29069/49 "2020-06-30T20:15:24Z")

</div>

I think that the 'backwards compatibility' issue has been resurrected.

In the flow below, I have an existing v2.9.1 `simpletime` flow, and have then updated `simpletime` [to the 'tickboxes' branch](https://github.com/Paul-Reed/node-red-contrib-simpletime/tree/tickboxes), and restarted node-RED.  
You'll notice that the debug shows no data, yet the now updated node shows all of the options ticked.  
Even 'deselecting' and then 'selecting all' does not prompt a deploy request, or change the blank output msg.

Adding a fresh `simpletime` node from the sidebar, does however work as expected.

 ![simpletime](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/c/bc6efa919a810143fc718593b78f8cec8d8c18b4.gif)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-contrib-simpletime-enhancement/29069)._
