ricott / homey-no.easee

Easee app for Homey
GNU General Public License v3.0
5 stars 5 forks source link

Schedule vs Deleted start #36

Closed mackewigren closed 1 year ago

mackewigren commented 2 years ago

I have a question about “Create schedule”-functionality. When I use the Create Schedule Card the time is set as “Delayed start” in Easee-app, not as a schedule. It doesn’t matter if I use Repeat Yes or No. As I see it this only means that the charging will start at a time but not stop. Am I doing wrong?

ricott commented 2 years ago

The basic charge plan is what is in the app, https://developer.easee.cloud/docs/scheduling#basic-charge-plan. The description for the start and stop time is the same as for the (new) weekly schedule. I haven't used it so don't know if it will stop charging at the stop time for any of the schedule types. Guess we would need to test it out.

mackewigren commented 1 year ago

Hi

I checked and started to test about this Basic Charge Plan. Would it be possible to set the Starttime and Stoptime with variables instead? Now it is hard to create a good automation. For example by using Tibber (or princess from others) I know that I should charge between for example 02:00 and 07:00 But then flow would be extremely complex if I would need to do all this in several ”threads”. But by storing for example 02:00 and 07:00 in two different variables in Logic I could the call this card to create schedule.

Off course the other way could be to let homey control it completely but it takes more commands at that time.

Best regards Marcus


Marcus Wigren 0733-983138 Rosenvägen 5
23735 Bjärred @.***

15 sep. 2022 kl. 22:11 skrev Richard Barkestam @.***>:

The basic charge plan is what is in the app, https://developer.easee.cloud/docs/scheduling#basic-charge-plan. The description for the start and stop time is the same as for the (new) weekly schedule. I haven't used it so don't know if it will stop charging at the stop time for any of the schedule types. Guess we would need to test it out.

— Reply to this email directly, view it on GitHub https://github.com/ricott/homey-no.easee/issues/36#issuecomment-1248564073, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZQJIJDBZNI6GTYYMQVGLLV6N7HVANCNFSM6AAAAAAQIP3FKU. You are receiving this because you authored the thread.

ricott commented 1 year ago

There are quite a few changes in the current test version of the app, will ship to live some time end of this week beginning next I think. You can install the test version already now, or wait until live. It has improved on/off actions amongst other things.

If you want to control charging and charge when energy prices are low I would not use the schedule action.

  1. Set access to locked using the easee mobile app
  2. Use new turn on/off actions to start and stop charging.

By setting access to locked you prevent the car from starting to charge when you plug it in. You have to issue a start command (turn on in test version) to start charging.

mackewigren commented 1 year ago

I can wait until it is shipped then. Will be interesting. Then I can let Homey start charging as soon as my house battery is empty for the evening and the car is plugged in.

Do I have to set locked every day? Or is it in locked state ”forever”.

Best regards

Marcus

9 nov. 2022 kl. 18:17 skrev Richard Barkestam @.***>:

There are quite a few changes in the current test version of the app, will ship to live some time end of this week beginning next I think. You can install the test version already now, or wait until live. It has improved on/off actions amongst other things.

If you want to control charging and charge when energy prices are low I would not use the schedule action.

Set access to locked using the easee mobile app Use new turn on/off actions to start and stop charging. By setting access to locked you prevent the car from starting to charge when you plug it in. You have to issue a start command (turn on in test version) to start charging.

— Reply to this email directly, view it on GitHub https://github.com/ricott/homey-no.easee/issues/36#issuecomment-1309083796, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZQJIOB3TPMXYW7X2NPY4DWHPMD7ANCNFSM6AAAAAAQIP3FKU. You are receiving this because you authored the thread.

ricott commented 1 year ago

You set locked once, and then it stays. In order to charge when access=locked you need to "authorize" the charger and this can be done via the Easee mobile app or by turning on the charger in the Homey app.

mackewigren commented 1 year ago

Hi

(Keep this in English so others can read, even if I found out that we are almost neighbors…)

Two questions 1) I installed the TEST version 1.5.5. Not sure what you mean by LOCKED. Is it the ÅTKOMST (ACCESS) on the start screen what you mean? And should I then select ENDAST NYCKEL (ONLY KEY).

And after this I will be able to start the charging from Homey. And the only commands to use is Start and stop? So maybe I build a flow saying

Car connected I price less than X House battery not charging (no power for the car otherwise and better to charge house battery with cheap electricity and use Tibber Price Guarantee for car

This would make it a lot simpler off course.

2) Will the app automatically update when you release the app or will I manually need to update my TEST to the stable version?

Best regards Marcus

9 nov. 2022 kl. 19:38 skrev Richard Barkestam @.***>:

You set locked once, and then it stays. In order to charge when access=locked you need to "authorize" the charger and this can be done via the Easee mobile app or by turning on the charger in the Homey app.

— Reply to this email directly, view it on GitHub https://github.com/ricott/homey-no.easee/issues/36#issuecomment-1309202076, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZQJIKTHHA7I6VRHRRSSQ3WHPVUHANCNFSM6AAAAAAQIP3FKU. You are receiving this because you authored the thread.

ricott commented 1 year ago

Hi!

  1. Correct, "key only". Then use turn-on and off actions that will issue start and stop commands.

  2. If you have installed the test version once, I think you automatically get the next test version when I issue one. You can install the live version over the test version I believe, to make sure you don't get test versions.