MTS 215 - external sensor not updating in latest version

[astirling01]

Not sure if anyone else is seeing this? I updated to the recent release and the external sensor is not updating automatically. It reports the correct temperature when the integration loads or when the manual refresh is pressed but it doesn't update without this.

I tried the previous beta and that was just the same so I've rolled back to the previous full release in the meantime.

[krahabb]

Some polling mechanics were reviewd..I'll check specifically if that query went broken in some way

[astirling01]

Thank you. Let me know if there’s anything I can send in terms of diagnostics. On 3 Dec 2025, at 06:29, krahabb ***@***.***> wrote: Some polling mechanics were reviewd..I'll check specifically if that query went broken in some way —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[krahabb]

I've now reverted a specific optimization done in 5.7.0 which was skipping polling for data that 'should' be sent over MQTT (when connected to a cloud MQTT broker). I strongly suspect my 'database' of message features (i.e. if they supports querying/setting/pushing) is not totally correct.
I usually collect these info from diagnostic/debug traces posted by users but they might be not exhaustive depending on the context of collection.
For the matter it would be nice to have a device diagnostic collected after some time of operation (1/2 days) so that I can check which data are effectively published over MQTT (async push) and refine my message database with more reliable data.
Thank you.

[astirling01]

No problem. I’ve updated to 5.7.1 and will update with the info in a couple of days On 3 Dec 2025, at 09:50, krahabb ***@***.***> wrote: I've now reverted a specific optimization done in 5.7.0 which was skipping polling for data that 'should' be sent over MQTT (when connected to a cloud MQTT broker). I strongly suspect my 'database' of message features (i.e. if they supports querying/setting/pushing) is not totally correct. I usually collect these info from diagnostic/debug traces posted by users but they might be not exhaustive depending on the context of collection. For the matter it would be nice to have a device diagnostic collected after some time of operation (1/2 days) so that I can check which data are effectively published over MQTT (async push) and refine my message database with more reliable data. Thank you. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>