Feature request: support for calling services/more flexibility?

[ThorAlex87]

Hi, just found this and so far it's the closest I have come to find what I'm looking for. Bust for my use-case there are a couple of issues. I've not been able to test anything yet as I'm missing the PV power entity, but hopefully that should be sorted soon. I'll also say that I have no idea how blueprints are made, so i don't really know how hard this would be or if it's possible at all.

1. I'd like to be able to set the temperature of a climate entity, one temperature replaces "on" and one temperature replaces "off". For example my bathroom thermostat should not be turned off. Instead i would like to increase the temperature setpoint to heat up the concrete and thus "store" solar power in the floor.

2. I control my heat pump with a IR blaster, so it does not has it's own entity. It's also unusually stupid and has no auto setting, so it has to be set to heat or cool when turned on.

If one could call a service (one for on and one for off maybe?) it would solve 1. and make 2. easier to control by allowing to trigger an automation to chose modes.

Now, I think I can work around this with some booleans and more automations, but it would be nice to have more flexibility in how the blueprint controlls devices.

Thanks, and keep up the good work!

[InventoCasa]

Hello, I will include the possibility to pass service calls for the "On action" and "Off action" of the appliance in the next release of the script.

[kesaloh13]

Hello, I will include the possibility to pass service calls for the "On action" and "Off action" of the appliance in the next release of the script.

That would be very helpful. Thank you very much for your work. I would like to control my heat pump with it. But the only option is to set the desired room temperature to a higher level and store the energy in the underfloor heating. However, it is not good for the compressor to be constantly switched on and off. Therefore, an intelligent control system via service calls would definitely be a good solution.

[techydude]

My EVSE (Fronius Wattpilot) doesn't have an on/off entity, it has start & stop button entities, so I had to make a template to do the conversion (see code below). It would be great if PV-excess-control could accommodate both methods of control.

`switch:

• platform: template switches: wattpilot_enable: friendly_name: "Wattpilot Enable" turn_on: service: button.press target: entity_id: button.wattpilot_start_charging turn_off: service: button.press target: entity_id: button.wattpilot_stop_charging`