# Bugs in node-red-contrib-huemagic 2.1.0

**URL:** <https://discourse.nodered.org/t/bugs-in-node-red-contrib-huemagic-2-1-0/19576>\
**Category:** General\
**Created:** [25 December 2019 16:38 UTC](https://discourse.nodered.org/t/bugs-in-node-red-contrib-huemagic-2-1-0/19576 "2019-12-25T16:38:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![parasaurolophus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/parasaurolophus/32/18729_2.png) [@parasaurolophus](https://discourse.nodered.org/u/parasaurolophus)\
**Post date:** [25 December 2019 16:38 UTC](https://discourse.nodered.org/t/bugs-in-node-red-contrib-huemagic-2-1-0/19576/1 "2019-12-25T16:38:04Z")

</div>

Latest release caused all my existing hue-related flows to break due to no longer forwarding events.

I was able to fix this for flows that use group nodes by reconfiguring all existing nodes.

Work-around was to check the new "Skip updates..." box in each node's configuration, save the flow, uncheck the box for each node, then save again.

This work-around for the newly introduced bugs that worked for group nodes did not fix the problems with scene nodes. I have found no work-around for scene nodes. With the latest version, scene nodes do recall the scene on the bridge but fire "ReferenceError: message is not defined" errors instead of generating an output event in the flow.

My existing flows use only group and scene nodes so I do not know if there are bugs in other node types, as well.