v0.50.6 in beta and production

v0.50.3 was in beta for quite a while. It has a lot of backend changes so I wanted to give the community a chance to check it out. Its been two months and there are not any comments, so here we go.

v0.50.4 is just a docs change. Added to the README the formats which are expected by the plugin by device. Its a question which comes up every so often, not needed for regular config, just if you are going deeper. There is a link in the configuration to it.

v0.50.5/6 are install minor fixes

Let me know if you have any unintended consequences.

## 0.50.5/6 install.sh minor changes

## 0.50.4

- Add MQTT payload format examples to README for all sensor types

- Link POLYGLOT_CONFIG sensor section to README payload reference

## 0.50.3

- Restructure POLYGLOT_CONFIG for devfile-first setup with upload and SSH paths

- Add starter data/mqtt-devices.yaml template

- Trim README to capability and installation overview only

## 0.50.2

- Extract device discovery and topic registration into discovery module

- Unwrap Tasmota StatusSNS payloads once in Controller before routing to nodes

- Skip duplicate status topic registration on re-discovery

- Remove dead pass stubs from node modules

- Fix disconnect handler exception path

## 0.50.1

- Fix startup handler gate when CUSTOMPARAMS arrives last

- Fix poll heartbeat guard to respect controller ready state

- Accept documented devlist JSON arrays alongside legacy dict upserts

- Merge devfile and devlist configuration as documented

- Resubscribe MQTT topics after DISCOVER when already connected

- Add MQTT connect timeout instead of infinite wait

- Fix sensor message routing to use two-argument updateInfo

- Refactor config loading, device registry, and MQTT bridge modules

- Add MQTasmotaSensor base class for shared Tasmota sensor behavior

- Unsubscribe MQTT topics when nodes are removed

- Add legacy config regression test suite

Edited 4 hours ago4 hr by sjenkins