[{"data":1,"prerenderedAt":39},["ShallowReactive",2],{"changelog-entry-\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices":3},{"id":4,"title":5,"body":6,"description":26,"extension":27,"meta":28,"navigation":34,"path":35,"seo":36,"stem":37,"__hash__":38},"changelog\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices.md","Managing Node-RED versions on Devices",{"type":7,"value":8,"toc":22},"minimark",[9,13,16,19],[10,11,12],"p",{},"We have added the ability to manage the Node-RED version running on application-assigned\nDevices within FlowFuse.",[10,14,15],{},"Ordinarily, a device will get its Node-RED version from the snapshot deployed to it. However,\nfor an Application-assigned device, you may not yet have a snapshot to deploy.",[10,17,18],{},"The new option, available under Device\u002FSettings\u002FEditor lets you pick what version\nof Node-RED the device should use - overriding what is in the active snapshot.",[10,20,21],{},"For devices running v2.4.1 or later of the Device Agent, Node-RED will get updated\nwhen the setting is saved. For older versions of the Device Agent, it will require\na new snapshot to be deployed to trigger the update.",{"title":23,"searchDepth":24,"depth":24,"links":25},"",2,[],"FlowFuse now allows specifying Node-RED versions for application-assigned devices, overriding active snapshots for greater flexibility.","md",{"date":29,"authors":30,"tags":32},"2024-05-09 13:01:00.0",[31],"nick-oleary",[33],"changelog",true,"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices",{"title":5,"description":26},"changelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","JafCcARCObu0fbq2lHfQaIfl3gHms-w8Uunc6WjzicU",1780132422591]