Bretton Wade

@FutureGUIs I haven't submitted a pull request to this repos on my changes because I rewrote a lot of it to work the way I wanted and it's not backwards...

I understand the conceptual organization you want, but it’s not really consistent with the way HA works. Each one of these things is a sensor, and that value is its...

For reference, here is my yaml (rename according to your entities): ```` template: sensor: - name: "Aquarium Power" unique_id: "aquarium_power_w" unit_of_measurement: "W" device_class: "power" state: > {% set w1 =...

[status.json.txt](https://github.com/itchannel/apex-ha/files/9419880/status.json.txt) Not strict JSON, but should do. It is a control value as well.

I think TBL is the schedule indicator. I’ll see what else I can set, but 75 is the pump setting (75%). > On Aug 24, 2022, at 7:03 PM, itchannel...

I changed it to not use the wizard, just a "Set 75". The status changed too (I also changed the pump name). `{ status: [ "AON", "75", "OK", "" ],...

I never got IOTA to work. HA removed the "official" integration and I haven't found another. I was really hoping for it to be exposed here. ;) I think it...

Request URL: http://apex.local/rest/config/oconf/3_1 Request Method: PUT Payload: `{ "name": "Sicce_Return", "icon": "Up/Down Arrows", "ctype": "Advanced", "log": false, "inuse": true, "type": "iotaPump|Sicce|Syncra", "did": "3_1", "gid": "", "gtype": "0", "ID": "19", "prog":...

The "extra" part doesn't seem to actually be applicable to the settings unless you are trying to send a schedule. The screen in apex fusion is like this:

but switching back to advanced mode, just like a variable: