custom-components
Update attributes on newest timestamp
The attributes/fields from polling "state" have timestamp included in the message. The service bus is delivering messages using state events which also contains a timestamp.
It have been observed that a service bus message with the newest timestamp have been overwritten by a state poll that returns older data, and thus result in the value jumping back and forth. This is suspected to be due to latencies in the Zaptec cloud.
The new polling setup in v0.8 with "triggered polling" will mitigate this, since it polls at several instances after a change. This will pick up the final stable value eventually.
It should be considered if we should keep a record of the timestamps for each state variable and only update if the timestamp is newer. This will require a considerable change to api.py, so this is not in scope for the v0.8 release.
Also doesn't really make sense to put much effort into this until Zaptec has decided what kind of push functionality to offer for smaller integrators when deprecating the installation/{id}/messagingConnectionDetails-api (ref https://github.com/custom-components/zaptec/issues/176#issuecomment-3062637738)
