Andreas Hochsteger

@joscha82 here's a PR to your great work to extend it with an interactive shell that allows inspecting of all available Wattpilot properties and changing them as well: https://github.com/joscha82/wattpilot/pull/1

@okoohler, have you tried using `set cae true` (lower-case) instead? There's a difference between Python and JSON (`True` vs. `true`) that may not be so obvious.

@okoohler thanks for reporting it was indeed a bug in setting boolean values. It's already fixed here: https://github.com/joscha82/wattpilot/pull/5

@joscha82, @okoohler and this PR adds simple MQTT support - so initial integration with Home Assistant using it's MQTT support might already be possible with a bit of tweaking: https://github.com/joscha82/wattpilot/pull/6...

In addition to enums the handling of default values is broken for constants too. While this produces the default value in the schema: ```typescript class Test { num = 10;...

The PR #600 implements support for referencing enums and constants as default values, would be great if I could get some feedback on it. See `test/programs/default-properties-ref` for a test case.

@YousefED it would be great if you could give me some feedback, if I took the right way to implement this feature. AFAICS it should be a bit more generic,...

I have the same requirement and expected properties with default values not be required. Any chance, that may be solved?

No, it uses websockets - see here for more details: https://github.com/safepay/sensor.fronius/issues/48#issuecomment-932501077

@gazoodle this already looks very good using v0.1.23. :-) The pumps are working as expected as well as the new keys and many other new entities show correct values (although...