1.2.2-release

What’s New

Sensor support (Smart home)

1. Smart sensor notification rules stay in sync with monitor behavior: threshold rules use the same value keys as on sensor cards (values on REST/BLE), including REST duplicate-key handling (temperature, temperature_2, …) aligned with server polling logic.
2. REST hints come from enabled fields with a path; BLE hints follow metric vs custom label rules, matching how readings are stored.
3. The threshold field control supports choosing from configured keys (datalist) or typing a custom key; the list narrows to sensors selected in the rule, or falls back to all enabled sensors if none are selected.
4. Changing the target sensors multiselect refreshes the field hints for threshold rules.

Refactoring & internals

1. Telegram ↔ smart sensors: Client helpers centralize REST key derivation so the UI and backend agree on key names without duplicating fragile logic.
2. Telegram Bot API: Chat discovery is structured around getUpdates, with follow-up getChat / getForumTopic enrichment separated from update parsing for clearer flow and errors (e.g. webhook conflicts).

Telegram notifications (recap)

1. Load chats & forum topics from the bot token; datalists for Chat / Thread in rules; manual IDs still allowed.
2. Caveats: Chats must appear in recent updates; webhooks block getUpdates; avoid parallel long polling on the same bot.