[Feat]: Sensors for ecoMax360

[dschense]

The request

These are my sensors I get on econet

Iam not that good in the API Stuff, but maybe this one helps to get some of these into the project

These 2 are for controlling Temp of Circuit 3 (floor heating) and DHW (hot water)

Circuit 3 Set Temp in Celcius:

Edit: /service/newParam
https://www.econet24.com/service/newParam?uid=XYZ&newParamName=361&newParamValue=32&_=UID
http://IP-OF-econet/econet/newParam?newParamName=361&newParamValue=32&_=UID

{
    "paramName": "361",
    "paramValue": 32,
    "result": "OK"
}

DHW set Temp in Celcius:

Edit: /service/newParam
https://www.econet24.com/service/newParam?uid=XYZ&newParamName=103&newParamValue=45&_=UID
http://IP-OF-econet/econet/newParam?newParamName=103&newParamValue=45&_=UID

{
    "paramName": "103",
    "paramValue": 45,
    "result": "OK"
}

Maybe someone can help me to find more to get the other ones included.

Additional information

No response

[Rumb0ldt]

In the older integration for FoxAir (https://github.com/zaapp/foxair-ha/tree/master) there are further controls with their keys: https://github.com/zaapp/foxair-ha/blob/master/custom_components/econet300/number.py.

Temperature circuit 1 – NIGHT - {"paramName": "239", "paramValue":18, "result":"OK"}

Temperature circuit 1 – TAG - {"paramName": "238", "paramValue":24, "result":"OK"}

Buffer target temperature - {"paramName": "183", "paramValue":39, "result":"OK"}

Temperature circuit 2 - night - {"paramName": "289", "paramValue":15, "result":"OK"}

Temperature circuit 2 - day - {"paramName": "288", "paramValue":21.5, "result":"OK"}

My aim is to extract also the other attributes and keys from the older code for the FoxAir heatpumps.

[jontofront]

Whet model ecomax you have?

[Rumb0ldt]

Whet model ecomax you have?

I am using a ecoMAX360i.

[jontofront]

Whet model ecomax you have?

I am using a ecoMAX360i.

We need to find the API endpoint for editable parameters.
For example, I have the following endpoints:

http://econet_local_ip/econet/regParams
http://econet_local_ip/econet/regParamsData
http://econet_local_ip/econet/sysParams
http://econet_local_ip/econet/rmCurrentDataParams
http://econet_local_ip/econet/rmCurrentDataParamsEdits

The endpoint for editable values appears to be:

http://econet_local_ip/econet/rmCurrentDataParamsEdits

Let me know if you need help explaining what each endpoint does or how to use them.

[Rumb0ldt]

http://econet_local_ip/econet/regParams ✔️ 
http://econet_local_ip/econet/regParamsData ❌ `{"error":"'CommThread' object has no attribute 'getCurrentParamsValues'"}`
http://econet_local_ip/econet/sysParams ✔️ 
http://econet_local_ip/econet/rmCurrentDataParams ❌  `{"error":"'CommThread' object has no attribute 'getRemoteMenuParams'"}`
http://econet_local_ip/econet/rmCurrentDataParamsEdits ❌ `{"error":"'CommThread' object has no attribute 'getCurrentParamsEdits'"}`

The endpoint for editable values appears to be:

http://econet_local_ip/econet/rmCurrentDataParamsEdits

Let me know if you need help explaining what each endpoint does or how to use them.

Do you need the results of both Params-endpoints too?
I don't know how to use the rm endpoints properly. Maybe which attributes I have to add.

Temporarily, I am using this script to change some simple parameters on the econet360i device in HA:
rest_command: set_new_econet_param: url: "http://_econet_local_ip_/econet/newParam?newParamName={{ key }}&newParamValue={{ value }}&_=UID" method: GET username: _un_ password: _pw_

[arni077r]

When this http://econet_local_ip/econet/rmCurrentDataParamsEdits
is throwing error, try this
http://econet_local_ip/econet/editParams

[Rumb0ldt]

econet/editParams ✔️

Nice! This command replies also a JSON with a lot of values.

[jontofront]

http://econet_local_ip/econet/regParams ✔️ 
http://econet_local_ip/econet/regParamsData ❌ `{"error":"'CommThread' object has no attribute 'getCurrentParamsValues'"}`
http://econet_local_ip/econet/sysParams ✔️ 
http://econet_local_ip/econet/rmCurrentDataParams ❌  `{"error":"'CommThread' object has no attribute 'getRemoteMenuParams'"}`
http://econet_local_ip/econet/rmCurrentDataParamsEdits ❌ `{"error":"'CommThread' object has no attribute 'getCurrentParamsEdits'"}`

The endpoint for editable values appears to be:
http://econet_local_ip/econet/rmCurrentDataParamsEdits
Let me know if you need help explaining what each endpoint does or how to use them.

Do you need the results of both Params-endpoints too? I don't know how to use the rm endpoints properly. Maybe which attributes I have to add.

Temporarily, I am using this script to change some simple parameters on the econet360i device in HA: rest_command: set_new_econet_param: url: "http://_econet_local_ip_/econet/newParam?newParamName={{ key }}&newParamValue={{ value }}&_=UID" method: GET username: _un_ password: _pw_

IF you give me script write post parameters I try implement it to code

[jontofront]

When this http://econet_local_ip/econet/rmCurrentDataParamsEdits is throwing error, try this http://econet_local_ip/econet/editParams

so this link http://econet_local_ip/econet/editParams work? If works we can try make one of the feature

[Rumb0ldt]

When this http://econet_local_ip/econet/rmCurrentDataParamsEdits is throwing error, try this http://econet_local_ip/econet/editParams

so this link http://econet_local_ip/econet/editParams work? If works we can try make one of the feature

Yes. JSON is attached.

editParams.json

[Rumb0ldt]

Do you need the results of both Params-endpoints too? I don't know how to use the rm endpoints properly. Maybe which attributes I have to add.
Temporarily, I am using this script to change some simple parameters on the econet360i device in HA: rest_command: set_new_econet_param: url: "http://_econet_local_ip_/econet/newParam?newParamName={{ key }}&newParamValue={{ value }}&_=UID" method: GET username: _un_ password: _pw_

IF you give me script write post parameters I try implement it to code

Set Buffer Target Temp
key: 183
value: [value]

Set DHW Temp
key: 103
value: [value]

Edit Work function (Mode working)
key: 162
value: 6 (Auto)
value: 2 (Winter)
value: 1 (Summer)

Heat pump work mode (Mode working)
key: 1231 (name: HP_work_state_set)
value: 1 (On)
value: 2 (Schedule)
value: 0 (Off)

Did you mean such combinations?

regParams.json
sysParams.json

[cashford8]

Hello all

Firstly, great work on this integration @jontofront. I'm following it with interest!

I realise I'm tagging onto an existing feature request, but I believe it is the same device... however happy to open another ticket if you want.

I also have an ecomax360i connected to an air source heat pump. Home assistant grabs some of the temperatures but none of the other parameters:

I would particularly be interested in the power sensors (electrical input and heat output - which only shows when the pump is running), COP efficiency, and also being able to run a hot water boost - all of these can be done via econet24.

I can provide the json for regParams etc. - let me know what you need.

[jontofront]

Hello all

Firstly, great work on this integration @jontofront. I'm following it with interest!

I realise I'm tagging onto an existing feature request, but I believe it is the same device... however happy to open another ticket if you want.

I also have an ecomax360i connected to an air source heat pump. Home assistant grabs some of the temperatures but none of the other parameters:

I would particularly be interested in the power sensors (electrical input and heat output - which only shows when the pump is running), COP efficiency, and also being able to run a hot water boost - all of these can be done via econet24. I can provide the json for regParams etc. - let me know what you need.

Hi,

check these exaples if the json https://github.com/jontofront/ecoNET-300-Home-Assistant-Integration/tree/master/tests/fixtures/ecoMAX360 like ours please register new task sensors key. If no sensors in example please give me your http://econet_local_ip/econet/regParams and http://econet_local_ip/econet/sysParams