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
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
A hash that maps to a device is created and stored as a device property. The device data is saved with that hash property. The hash is then removed from that in-memory representation so it doesn't appear in API responses.
When device.save is called anytime in the future, such as when updating the device data after initialization, that hash property is not included.
When the server is restarted, it looks for that hash. When the hash isn't found, it creates a new device, providing the illusion that updated device data did not persist.
The text was updated successfully, but these errors were encountered:
A hash that maps to a device is created and stored as a device property. The device data is saved with that hash property. The hash is then removed from that in-memory representation so it doesn't appear in API responses.
When
device.save
is called anytime in the future, such as when updating the device data after initialization, that hash property is not included.When the server is restarted, it looks for that hash. When the hash isn't found, it creates a new device, providing the illusion that updated device data did not persist.
The text was updated successfully, but these errors were encountered: