You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per spec (§8.2.4 + §3.2.14), when a device is factory-reset locally, it sends a `DeviceResetLocallyNotification to its Lifeline destinations. The controller MUST handle this by removing the node from its database.
Scope:
Implement DeviceResetLocallyCommandClass with [CommandClass(CommandClassId.DeviceResetLocally)]:
ProcessCommand override to handle the incoming Notification command
On receipt: log the event, raise a NodeReset event on the Node, then remove the node from the controller's node list
The removal should be graceful: mark the node as failed/removed, clean up any cached state
If persistence (Cache node info #21) is implemented, also clean up persisted data for the node
The notification from the node must be ACKed before removal (the node needs to know it was received)
Design notes: Use the pattern: process the command, raise an event, then asynchronously clean up (do we need a delay?).
Per spec (§8.2.4 + §3.2.14), when a device is factory-reset locally, it sends a `DeviceResetLocallyNotification to its Lifeline destinations. The controller MUST handle this by removing the node from its database.
Scope:
DeviceResetLocallyCommandClasswith[CommandClass(CommandClassId.DeviceResetLocally)]:ProcessCommandoverride to handle the incoming Notification commandNodeResetevent on the Node, then remove the node from the controller's node listDesign notes: Use the pattern: process the command, raise an event, then asynchronously clean up (do we need a delay?).