Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Generic Device Control via HTTP requests i.e. Shelly Plugs by configureable trigger conditions #1310

Open
Andrix82 opened this issue Oct 4, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Andrix82
Copy link

Andrix82 commented Oct 4, 2024

Is your feature request related to a problem? Please describe.

Controlling devices like shelly plugs manually while monitoring openDTUonBattery data is getting exhausting :)

Describe the solution you'd like

OpenDTUonBattery has many informations/intelligence directly avaiblable (Hoymiles, Smart Meter, MPPT, Huawei, Battery ) ( and now plenty ressources for new features.
I feel a very usefull extension would be the possibility to trigger generic http requets based on configureable trigger conditions to control all devices which support http requests like i.e. Shelly Plugs ( http://192.168.X.X/relay/0?turn=on/off )

Feature could look like that:

Define several http requests by IP adress ( like http://192.168.X.X/relay/0?turn=on )

Define for each of them trigger conditions:
Combination of at least 2 maybe 3 trigger conditions with && (AND) OR ||(OR) logic

Trigger Conditions can be:
Smart Meter Value
MPPT actual power
Hoymiles actual power
Huawei actual power
Battery Level ( both SoC or Voltage )

=> larger or smaller threshold

and additional a debounce paramter for each (combined) trigger

With such a feature very powerful smart home control could be done for all devices supporting common http requests!

Someone interested or like to take up ?

I could also start or support but would need following help/infos:

-Reference to an Issue where a new feature "Tab" ( Level like DPL, Huawei... ) has been added to have code changes (mainly UI and scheduler) as reference
-Infos about the scheduling details (how often are tasks on those level executed ) to implement a debouncing counter.
-Triggering http request I would take over from Smart Meter http implementation... ?!

Describe alternatives you've considered

No response

Additional context

No response

@Andrix82 Andrix82 added the enhancement New feature or request label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant