search

jontofront / ecoNET-300-Home-Assistant-Integration

ecoNET 300 integration to HA
8 stars 3 forks source link

Future. Change summer or winter mode #27

Open jontofront opened 9 months ago

jontofront commented 9 months ago

Summer/Winter mode API URL /rmNewParam?newParamIndex=55&newParamValue=0 NewParamIndex = 55

newParamValue=0 - Summer mode newParamValue=1 - Winter mode newParamValue=2 - Auto mode

Check the available parameters (Max min value ..) of the parameter NewParamIndex API [/econet/rmParamsData]()

image

translations: EN "summer_winter": "Summer / winter", "winter": "Winter", "summer": "Summer",

PL "summer_winter": "Lato / zima", "winter": "Zima", "summer": "Lato",

SUMMER mode act. temperature: paramName: "56", paramValue: temp_C

SUMMER mode deact. temperature: "paramName": "57" "paramValue": temp_C image

zaapp commented 9 months ago

Use /econet/newParam?newParamName=55&newParamValue=0 instead of rmNewParam

To use this settings implement new entity -> select. Then define available values. Second way is using number entity wrapped by template sensor.

jontofront commented 9 months ago

Thanks @zaapp I am only beginer in it :) I can do only analitic tasks/issuse

zaapp commented 9 months ago

@jontofront Just like me. I change one line and debug what happens in home assistant. I am very happy that my previous changes works. I plan add more entities to make possible mapping data enum value.

jontofront commented 9 months ago

@zaapp actualy I investigate these edit keys is static o generated in endpoint rmParamsData, becouse in rmCurrentDataParamsEdits I have only 3 keys

Use /econet/newParam?newParamName=55&newParamValue=0 instead of rmNewParam

To use this settings implement new entity -> select. Then define available values. Second way is using number entity wrapped by template sensor.