[APP][Pro] Piggy Bank

[bfisk]

Hello there, and thanks for a great app. I have a few questions and comments, I hop you don’t mind them all in one post (I will try to write clearly).

I set up the app last night, and have a bunch of different heaters in. Mill panel ovens, Z-TRM3 thermostats, Z-temp2 thermostats and MELcloud heat pumps. I control the waterborne floor heating via switching the circulation pump off/on for load shedding.
I have an Easee charger (but have not included that for now) and I control the water boiler via a VThermo linked to two temp sensors and a Heavy Duty relay.

1. How to prevent a device from being load-shed
   Under Enheter → Modus og Prioritet, I have set many of them to Alltid På, and some of them to Styrt. For instance, during the night program, I don´t want the ovens in our bedroom to ever turn off. Same goes for the heat pumps - I want to control the temperature but I never want them to be load shed.
   However, overnight, ALL devices, both the ones marked as «always on» and the ones marked as «styrt» have been switched off and on and off and on by Sparegris.
   Under Enheter->Prisstsyring I have them set to «endre temp» in all price ranges.

This seems to have happened with all the devices, but see screenshots below. I suspect I have misunderstood the settings…?

2. Easee and cars incompatible with smart charging
   My Peugeot unfortunately has a know bug in the onboard charger, where the charger will fail if current is not available within a certain time (a few minutes) after connecting. Thus, «smart charging» will not work, so I have to set a start time from the car itself, and only regulate current draw up and down. I can i.e. set the car to start charging at 22:00, and it will start then. But - if at any time less than 6A is available, the onboard charger will fail, charging will stop, and the car will have to be reconnected.
   While waiting for Peugeot to fix this, is there a way of just letting Sparegris control the available current (6A-32A), but not use start/stop/pause commands?

3. Minimum temp setting on VThermo
   Since I use a VThermo for my water heater, I would like to control the temperature in the range 40-75 degrees, but Sparegris seems to cap the max allowed temperature at 35.

4. Allow an initial overage
   I essentially had this coded up with flows before, but it is cumbersome to maintain and not very flexible so that is why I want to use your app instead!
   In my solution I am aiming for 10kwh energy limit pr hour, minus a little margin, so say 9500wh. But, when calculating the power level at which to start shedding, I allow an initial allowed overage, that reduces to 0 as the hour ends. After some experimentation, about 2000wh works for me. So, that means at the beginning of a new hour, the target max energy for the hour is 11500wh - almost like a «reverse power reserve».
   This prevents a cycling situation where a lot of load is shed in the beginning of the hour - then powered on again in the middle of the hour - and everything powered on and blasting at full force at xx:59, just to be all shed again at the turn of the hour. In fact, with this kind of setup, it runs pretty smoothly - it has some «ice in the stomach» early on when there is still room for recovery, but sheds hard as the hour ends, instead of the opposite.
   This strategy probably works better when you have many devices to control.
   Maybe a solution could be to allow a negative power reserve?

[frodeheg]

Hi, sorry all for the long response time, but I have been sick for the last few days.

@Arunav_Mandal

The debugging option would be nice to have as I want to see what command Piggy is sending to Easee as at this moment piggy only switches on and off.

This will be added in the next version.

@Arunav_Mandal

Piggy to charge the cheapest 40kwh before 07:00, it makes a plan for 6hrs starting at 0000hrs even if 5% charge can be done much faster

Yes, as the Easee app cannot provide the % -status from the battery I cannot give this as an option…

But… if you have access to the % from elsewhere I can probably make a charge until %-full flow that will only work as long as you continuously push the %-full status to Piggy with another flow. It’s a bit messy but I guess it’s the best I can do as long as the Easee app doesn’t provide this…

Did you figure out the remaining issues to start the charging?

@thomase

• Setting Price Kind to External under Advanced, to use prices from the “Strømregning” app

You don’t have to, you can use “spotpris” as well, but if you already use the Strømregning app I guess it may be more convenient.

@thomase

Has anyone managed to fetch the battery status from a Tesla, to get a more precisely ordering of kWh’s in the flow?

Ideally this should have been available in the Easee app, if anyone knows if it is available in the Easee API (@dooniem do you know?), then maybe it’s possible to get it added to that app too. Otherwise I could add the flow cards for it as mentioned above.

@bfisk

This seems to have happened with all the devices, but see screenshots below. I suspect I have misunderstood the settings…?

So… “Always On” might be a bit misleading as it is now. The difference between “Always On” and “Controlled” is that it will Turn off all the “Controllable” devices first, then if it is not enough it will try to power off the “Always On” devices as a last resort to be able to meet the power tariff. Thus what you have experienced is that at the start of the hour there was an immense big load that needed to be corrected… as this is related to your idea about correcting exactly this you’ll find my answer to that below in this thread.

@bfisk

While waiting for Peugeot to fix this, is there a way of just letting Sparegris control the available current (6A-32A), but not use start/stop/pause commands?

Actually, Piggy is not using any start/stop/pause commands at all. It’s only changing the dynamic current offered. It will be similar to if you use the Easee app directly and just draw the slider up and down. What happens in this case if you draw it below 6A? will it still disconnect? Because the Easee app never sends any start/stop/pause commands in this case…

You can probably use the flow card option to control the charging. In this case you can make your own cap on the minimum current in order to work around the issue… (however, I have not gotten feedback from anyone about the flow-card charging feature so I don’t know how well it works, so it would be good to get feedback if anything is broken - I don’t have a charger myself so testing these things is kind of awkward…)

@bfisk

VThermo for my water heater, I would like to control the temperature in the range 40-75 degrees

Ah, yeah, the Vthermo is a bit special… Ok, I’ll fix it

@bfisk

Maybe a solution could be to allow a negative power reserve?

Awesome idea. I have had this ticket open for some time to resolve this kind of issues, but your idea about negative power reserve sounds like a better option…, and if I default the reserve to a low value then it should be relatively safe too as no one would overshoot because of this without wittingly changing it.

Though… it’s kind of already supported. You can do this now by going to “Adwanced settings” and changing “Reserved power” to a negative value. Although, you would have to change this with a flow by yourself to get the dynamic behaviour you suggest.

[dooniem]

@frodeheg

is available in the Easee API

I can’t find any SOC related data in their API. Let’s just say, if it was available, then Tibber would have it.

[Arunav_Mandal]

@frodeheg For Tesla cars battery % can be fetched from [APP][Pro] Tesla Smart Charger

@frodeheg The charging won’t start and I created a flow as @dooniem advised

[frodeheg]

@Arunav_Mandal

For Tesla cars battery % can be fetched from [APP][Pro] Tesla Smart Charger

Great, then I will provide you with a flow to stop charging at x %. It is being followed up here. Meanwhile you have to create a flow that does the math yourself and calculates how many kWh you need to charge per %.

@Arunav_Mandal

The charging won’t start

What if you use a simpler flow like this?

Shared Flow | Homey

…or

Shared Flow | Homey

then you can start it manually by just running the flow

[dooniem]

@frodeheg

Great, then I will provide you with a flow to stop charging at x %

This is an option in lots of cars already. If a Tesla car is set to stop charging at 80%, Easee can’t charge more than 80 and charging/Piggy stops. He can easily change this through his Tesla app. I have a Nissan Leaf, this is not possible through app, but inside the car I think it’s possible to do.

@frodeheg

Meanwhile you have to create a flow that does the math yourself and calculates how many kWh you need to charge per %.

I read your post like this calculation is temporary until you implement the new flow card.
So then the question is, how will Piggy decide what number of kWh to plan for the upcoming charge session, just by knowing the current battery%?

I mean in order to save money, the number of ordered kWh in (or by?) Piggy is crucial. The less hours Piggy needs to schedule charging, the easier picking cheap hours gets. That’s why you should experiment with making your own flow to calculate the needed kWh for the charge anyway, is my opinion…Unless @frodeheg has remarkable plan to share with us?

Piggy will need to know your specific car’s battery coefficient, what 1% battery equals in kWh. So this must be inputted somehow? Or do you think Piggy will be able to learn this over time, making the first few charge sessions “badly planned” until it learns?
When it’s winter, you need to add 5-10% on this coefficient because the battery is to cold to grab onto all of the received kWh…
So you need to add a temperature algorithm. Automatic or default values that can be tweaked by the user?
I don’t have a battery status in Homey, but if I had, that would only make my own “calculate needed kWh”-flow easier. Now I input my battery status through Siri before charging.

I use the YR weather integration to decide on how much to add to my coefficient.
Right now 5% is perfect. If I want to stop at 80%, adding 5% to my coefficient actually stops the charger at 80%. And Homey doesn’t know my battery status. I currently stop at 80% just for testing my calculations, battery health isn’t affected by charging to 100% on a home charger anyway is what I’ve been told.

Not sure if it’s enough with 3 steps (0%, 5% and 8% is what I have currently). But that’s what’s fun to test out during this winter.

[frodeheg]

@dooniem

how will Piggy decide what number of kWh to plan for the upcoming charge session, just by knowing the current battery%

You know… magic

@dooniem

Unless @frodeheg has remarkable plan

Nah, just magic

Ok, point taken. Maybe I’ll just put This ticket on hold.

[bfisk]

On a sidenote, Easee (and any other AC charging station) will never know the car´s battery percentage, as this is not communicated during AC charging (it is not part of the protocol, unlike for DC charging). So the car´s state of charge has to come from the car or some other source (manually or inferred)

[dooniem]

For you especially @Arunav_Mandal, it’s easy to google “Usable Capacity” for Tesla. I easily found one for Model 3 Performance as an example:

That means 1% = 0,76kWh – Theoretically, without wear and tear.

It’s best to measure your actual “coefficient” during summer. But since it’s winter, use what you find for your model online as a starting point. Let’s say you have your car set to stop at 80%.I would turn that setting off temporarily for this first test. Just in case the coefficient you are using all of a sudden is too high.

Now if your car is at 55%, take aim at for instance 90%. So 90–55 => 35% to charge. The higher the charging-% the better precision your output will have. Now you order 35*<your coefficient> kWh in Piggy. Then you check what temperatures is predicted during your charge. Let’s say it’s maximum 7° and at lowest 2°C.

When charging is done, you will see either you are spot on, below or over 90% battery. If it’s 100% the test is useless Let’s say you have 82% battery when charging is done.
You now know that you missed your target with (1-(82/90))*100 = 8,9%.
So at least for the temperature range 7°C–>2°C, you should assume you need to add 8,9% to your coefficient. You can make assumptions for lower temperatures already. But now you have a OK function to calculate what kWh to order through Piggy!

Now you can enable your limit again, if you need one. If you always go for 100% or set a limit, you can adjust your 8,9% to 10% and be sure that you planned for enough kWh, but not way too much, making Piggy schedule your session “more optimal”. Though it’s more fun to try and order only what your calculations say you need, and then tweak for each temperature

Next time you want to charge and Tesla reports 37% battery you can make a logic card that calculates:

(Updated picture to be more precise)
And use this as input to your Piggy charging card.
You can use a variable for the “temperature percent” if you’d like…

When summer arrives, you can decide to redo your test to get a “more accurate” coefficient, and also redo your temperature percentages.

That’s one way to do it. You can also rely on the “remaining charge” inside Piggy for doing your calculations or visit a supercharger that tells you how much kWh was given to the car.

[frodeheg]

New in the test version 0.19.12:

• Devices added to the supported list:
  • com.xiaomi-mi:plug.maeu01
  • no.connecte:puck_relay
• Vthermo devices will now fetch their min/max temp from the device capabilities
• Added device troubleshooting/logging - Available from the Help menu
• New Override features for charging (tickets #92 and #94)

[Arunav_Mandal]

I created this flow Shared Flow | Homey and the charge plan showed it is going to start at 03:00 but it didn’t start and there are no logs in Easee charger. The debug logs are given below.

+9:4:27.579: Device: 1 2a4468e3-0932-4dd7-9f8f-a9e85f1fdf53 Outside Lights socket

+9:4:27.633: Device: 0 172a16cc-bc82-43b1-bbef-8769063671c4 Stairs LED socket

+9:4:27.644: Device: 0 0ff09447-3869-4b63-9c2f-5f7d087a7035 Balcony LED 2 socket

+9:4:27.649: Device: 0 ddab9d55-4fa5-4c2b-84d7-54b2c2a9355f Balcony LED 1 socket

+9:4:27.659: ignoring: Electricity Bill

+9:4:27.666: ignoring: 3-Phase Smart Meter (ZMNHXD)

+9:4:27.672: ignoring: 3-Phase Smart Meter (ZMNHXD) - Total

+9:4:27.678: ignoring: 3-Phase Smart Meter (ZMNHXD) - ph1

+9:4:27.686: ignoring: 3-Phase Smart Meter (ZMNHXD) - ph2

+9:4:27.691: ignoring: 3-Phase Smart Meter (ZMNHXD) - ph3

+9:4:27.697: ignoring: Electricity Bill Hybel

+9:4:27.714: ignoring: Tesla Model Y

+9:4:27.716: ignoring: Piggy Bank Insights

+9:4:27.718: ignoring: Power of the hour

+9:4:27.740: Device: 1 8c28d322-e09a-4c23-b2cd-c4d176562945 Easee Charger other

+9:4:27.746: Device: 2 bc9c666c-047c-4401-9d7b-a105425897de H60 [192.168.3.163] socket

+9:4:27.752: Device: 1 ac04958a-f214-4609-a982-3cc6a5410f57 AC 2nd Floor socket

+9:4:27.758: Device: 1 c8bc69d7-d59d-4a81-a0ff-7c33afc6e74d AC 1st Floor socket

+9:4:27.824: Electricity price api version 1.5.3 installed and version is ok. Device is installed and ok. Data was returned.

+9:4:28.856: onPowerUpdate: Using: 1803W, Accum: 130.95 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1799.30)

+9:4:28.858: Below power Limit: 12955.591617296755

+9:4:28.860: Can use 12956W more power

+9:4:28.916: Requested power change: 12956

+9:4:28.972: attempt changeDevicePower(12956) for Easee Charger

+9:4:28.977: Wait more: 180 - 14.659 = 165.341 sec left

+9:4:28.981: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:28.984: Reached end without anything to turn on

+9:4:36.696: onPowerUpdate: Using: 1844W, Accum: 134.88 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1837.15)

+9:4:36.698: Below power Limit: 12946.33466774792

+9:4:36.701: Can use 12946W more power

+9:4:36.704: Requested power change: 12946

+9:4:36.857: attempt changeDevicePower(12946) for Easee Charger

+9:4:36.860: Wait more: 180 - 22.542 = 157.458 sec left

+9:4:36.874: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:36.925: Reached end without anything to turn on

+9:4:43.122: onPowerUpdate: Using: 1889W, Accum: 138.16 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1878.61)

+9:4:43.167: Below power Limit: 12927.303869668627

+9:4:43.170: Can use 12927W more power

+9:4:43.197: Requested power change: 12927

+9:4:43.278: attempt changeDevicePower(12927) for Easee Charger

+9:4:43.287: Wait more: 180 - 28.969 = 151.031 sec left

+9:4:43.304: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:43.307: Reached end without anything to turn on

+9:4:48.475: onPowerUpdate: Using: 1891W, Accum: 140.97 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1880.45)

+9:4:48.506: Below power Limit: 12947.037072491068

+9:4:48.509: Can use 12947W more power

+9:4:48.526: Requested power change: 12947

+9:4:48.607: attempt changeDevicePower(12947) for Easee Charger

+9:4:48.630: Wait more: 180 - 34.311 = 145.689 sec left

+9:4:48.650: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:48.656: Reached end without anything to turn on

+9:4:53.846: onPowerUpdate: Using: 1157W, Accum: 143.80 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1206.36)

+9:4:53.848: Below power Limit: 13702.935273754558

+9:4:53.858: Can use 13703W more power

+9:4:53.870: Requested power change: 13703

+9:4:53.978: attempt changeDevicePower(13703) for Easee Charger

+9:4:53.987: Wait more: 180 - 39.669 = 140.33100000000002 sec left

+9:4:53.997: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:54.022: Reached end without anything to turn on

+9:4:59.154: onPowerUpdate: Using: 1158W, Accum: 145.50 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1207.28)

+9:4:59.157: Below power Limit: 13724.778927584019

+9:4:59.179: Can use 13725W more power

+9:4:59.189: Requested power change: 13725

+9:4:59.288: attempt changeDevicePower(13725) for Easee Charger

+9:4:59.297: Wait more: 180 - 44.979 = 135.02100000000002 sec left

+9:4:59.305: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:4:59.317: Reached end without anything to turn on

+9:5:6.576: onPowerUpdate: Using: 1159W, Accum: 147.89 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1208.19)

+9:5:6.579: Below power Limit: 13755.822642190034

+9:5:6.594: Can use 13756W more power

+9:5:6.602: Requested power change: 13756

+9:5:6.689: attempt changeDevicePower(13756) for Easee Charger

+9:5:6.700: Wait more: 180 - 52.381 = 127.619 sec left

+9:5:6.717: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:6.732: Reached end without anything to turn on

+9:5:12.946: onPowerUpdate: Using: 1158W, Accum: 149.94 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1207.28)

+9:5:12.948: Below power Limit: 13784.457744698522

+9:5:12.950: Can use 13784W more power

+9:5:12.953: Requested power change: 13784

+9:5:13.123: attempt changeDevicePower(13784) for Easee Charger

+9:5:13.133: Wait more: 180 - 58.815 = 121.185 sec left

+9:5:13.144: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:13.162: Reached end without anything to turn on

+9:5:18.865: onPowerUpdate: Using: 1146W, Accum: 151.84 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1196.34)

+9:5:18.893: Below power Limit: 13822.191278407774

+9:5:18.905: Can use 13822W more power

+9:5:18.936: Requested power change: 13822

+9:5:18.983: attempt changeDevicePower(13822) for Easee Charger

+9:5:18.995: Wait more: 180 - 64.677 = 115.323 sec left

+9:5:19.004: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:19.012: Reached end without anything to turn on

+9:5:23.956: onPowerUpdate: Using: 1149W, Accum: 153.47 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1199.07)

+9:5:23.966: Below power Limit: 13841.487430571751

+9:5:23.968: Can use 13841W more power

+9:5:23.983: Requested power change: 13841

+9:5:24.065: attempt changeDevicePower(13841) for Easee Charger

+9:5:24.068: Wait more: 180 - 69.751 = 110.249 sec left

+9:5:24.072: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:24.075: Reached end without anything to turn on

+9:5:29.156: onPowerUpdate: Using: 1145W, Accum: 155.13 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1195.44)

+9:5:29.159: Below power Limit: 13868.283189206459

+9:5:29.161: Can use 13868W more power

+9:5:29.173: Requested power change: 13868

+9:5:29.345: attempt changeDevicePower(13868) for Easee Charger

+9:5:29.352: Wait more: 180 - 75.034 = 104.966 sec left

+9:5:29.356: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:29.361: Reached end without anything to turn on

+9:5:36.791: onPowerUpdate: Using: 1144W, Accum: 157.55 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1194.53)

+9:5:36.831: Below power Limit: 13902.900958871785

+9:5:36.833: Can use 13903W more power

+9:5:36.837: Requested power change: 13903

+9:5:36.913: attempt changeDevicePower(13903) for Easee Charger

+9:5:36.916: Wait more: 180 - 82.598 = 97.402 sec left

+9:5:36.923: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:36.926: Reached end without anything to turn on

+9:5:42.461: onPowerUpdate: Using: 1155W, Accum: 159.36 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1204.48)

+9:5:42.463: Below power Limit: 13916.970320548635

+9:5:42.500: Can use 13917W more power

+9:5:42.503: Requested power change: 13917

+9:5:42.646: attempt changeDevicePower(13917) for Easee Charger

+9:5:42.649: Wait more: 180 - 88.331 = 91.669 sec left

+9:5:42.671: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:42.686: Reached end without anything to turn on

+9:5:48.895: onPowerUpdate: Using: 1163W, Accum: 161.42 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1211.71)

+9:5:48.897: Below power Limit: 13937.46178710996

+9:5:48.900: Can use 13937W more power

+9:5:48.902: Requested power change: 13937

+9:5:49.024: attempt changeDevicePower(13937) for Easee Charger

+9:5:49.027: Wait more: 180 - 94.71 = 85.29 sec left

+9:5:49.029: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:49.032: Reached end without anything to turn on

+9:5:56.201: onPowerUpdate: Using: 1175W, Accum: 163.78 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1222.52)

+9:5:56.230: Below power Limit: 13957.965761887557

+9:5:56.241: Can use 13958W more power

+9:5:56.253: Requested power change: 13958

+9:5:56.321: attempt changeDevicePower(13958) for Easee Charger

+9:5:56.335: Wait more: 180 - 102.016 = 77.984 sec left

+9:5:56.344: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:5:56.355: Reached end without anything to turn on

+9:6:3.326: onPowerUpdate: Using: 1176W, Accum: 166.11 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1223.42)

+9:6:3.335: Below power Limit: 13988.846164350762

+9:6:3.338: Can use 13989W more power

+9:6:3.354: Requested power change: 13989

+9:6:3.581: attempt changeDevicePower(13989) for Easee Charger

+9:6:3.592: Wait more: 180 - 109.275 = 70.725 sec left

+9:6:3.606: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:3.608: Reached end without anything to turn on

+9:6:8.982: onPowerUpdate: Using: 1196W, Accum: 167.95 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1241.37)

+9:6:9.050: Below power Limit: 13994.204851409153

+9:6:9.073: Can use 13994W more power

+9:6:9.088: Requested power change: 13994

+9:6:9.156: attempt changeDevicePower(13994) for Easee Charger

+9:6:9.170: Wait more: 180 - 114.852 = 65.148 sec left

+9:6:9.225: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:9.227: Reached end without anything to turn on

+9:6:16.193: onPowerUpdate: Using: 1259W, Accum: 170.35 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1297.79)

+9:6:16.224: Below power Limit: 13963.629923059934

+9:6:16.279: Can use 13964W more power

+9:6:16.286: Requested power change: 13964

+9:6:16.329: attempt changeDevicePower(13964) for Easee Charger

+9:6:16.345: Wait more: 180 - 122.026 = 57.974000000000004 sec left

+9:6:16.355: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:16.366: Reached end without anything to turn on

+9:6:22.121: onPowerUpdate: Using: 1291W, Accum: 172.41 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1326.39)

+9:6:22.150: Below power Limit: 13958.162343201555

+9:6:22.193: Can use 13958W more power

+9:6:22.259: Requested power change: 13958

+9:6:22.451: attempt changeDevicePower(13958) for Easee Charger

+9:6:22.465: Wait more: 180 - 128.145 = 51.85499999999999 sec left

+9:6:22.474: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:22.493: Reached end without anything to turn on

+9:6:28.995: onPowerUpdate: Using: 1371W, Accum: 174.88 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1397.75)

+9:6:29.044: Below power Limit: 13909.140662249592

+9:6:29.095: Can use 13909W more power

+9:6:29.116: Requested power change: 13909

+9:6:29.163: attempt changeDevicePower(13909) for Easee Charger

+9:6:29.172: Wait more: 180 - 134.853 = 45.14699999999999 sec left

+9:6:29.188: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:29.190: Reached end without anything to turn on

+9:6:34.003: onPowerUpdate: Using: 1461W, Accum: 176.80 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1477.90)

+9:6:34.009: Below power Limit: 13841.738674427956

+9:6:34.017: Can use 13842W more power

+9:6:34.020: Requested power change: 13842

+9:6:34.100: attempt changeDevicePower(13842) for Easee Charger

+9:6:34.108: Wait more: 180 - 139.79 = 40.21000000000001 sec left

+9:6:34.119: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:34.130: Reached end without anything to turn on

+9:6:42.705: onPowerUpdate: Using: 1548W, Accum: 180.33 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1555.16)

+9:6:42.708: Below power Limit: 13793.767737800941

+9:6:42.710: Can use 13794W more power

+9:6:42.727: Requested power change: 13794

+9:6:42.798: attempt changeDevicePower(13794) for Easee Charger

+9:6:42.801: Wait more: 180 - 148.483 = 31.516999999999996 sec left

+9:6:42.803: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:42.826: Reached end without anything to turn on

+9:6:49.048: onPowerUpdate: Using: 1627W, Accum: 183.06 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1625.19)

+9:6:49.072: Below power Limit: 13743.18099514471

+9:6:49.116: Can use 13743W more power

+9:6:49.145: Requested power change: 13743

+9:6:49.200: attempt changeDevicePower(13743) for Easee Charger

+9:6:49.211: Wait more: 180 - 154.892 = 25.108000000000004 sec left

+9:6:49.223: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:49.236: Reached end without anything to turn on

+9:6:54.368: onPowerUpdate: Using: 1678W, Accum: 185.46 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1670.32)

+9:6:54.371: Below power Limit: 13715.967075617311

+9:6:54.373: Can use 13716W more power

+9:6:54.397: Requested power change: 13716

+9:6:54.533: attempt changeDevicePower(13716) for Easee Charger

+9:6:54.555: Wait more: 180 - 160.237 = 19.763000000000005 sec left

+9:6:54.557: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:6:54.560: Reached end without anything to turn on

+9:7:2.538: onPowerUpdate: Using: 1715W, Accum: 189.27 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1702.98)

+9:7:2.557: Below power Limit: 13715.52413498572

+9:7:2.559: Can use 13716W more power

+9:7:2.596: Requested power change: 13716

+9:7:2.690: attempt changeDevicePower(13716) for Easee Charger

+9:7:2.702: Wait more: 180 - 168.384 = 11.616000000000014 sec left

+9:7:2.713: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:2.721: Reached end without anything to turn on

+9:7:8.971: onPowerUpdate: Using: 1752W, Accum: 192.33 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1735.57)

+9:7:8.977: Below power Limit: 13707.362870538238

+9:7:8.996: Can use 13707W more power

+9:7:9.008: Requested power change: 13707

+9:7:9.100: attempt changeDevicePower(13707) for Easee Charger

+9:7:9.103: Wait more: 180 - 174.786 = 5.213999999999999 sec left

+9:7:9.114: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:9.126: Reached end without anything to turn on

+9:7:16.452: onPowerUpdate: Using: 1761W, Accum: 195.97 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1743.48)

+9:7:16.471: Below power Limit: 13731.959731289046

+9:7:16.494: Can use 13732W more power

+9:7:16.497: Requested power change: 13732

+9:7:16.618: attempt changeDevicePower(13732) for Easee Charger

+9:7:16.620: Setting 0 amp, was 0

+9:7:16.622: finished changeDevicePower() for Easee Charger - The new current is the same as the previous

+9:7:16.625: Reached end without anything to turn on

+9:7:22.624: onPowerUpdate: Using: 1767W, Accum: 198.98 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1748.74)

+9:7:22.650: Below power Limit: 13753.635670778056

+9:7:22.658: Can use 13754W more power

+9:7:22.661: Requested power change: 13754

+9:7:22.731: attempt changeDevicePower(13754) for Easee Charger

+9:7:22.734: Wait more: 180 - 6.113 = 173.887 sec left

+9:7:22.738: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:22.750: Reached end without anything to turn on

+9:7:28.986: onPowerUpdate: Using: 1793W, Accum: 202.11 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1771.50)

+9:7:28.988: Below power Limit: 13756.554445472331

+9:7:28.991: Can use 13757W more power

+9:7:29.061: Requested power change: 13757

+9:7:29.130: attempt changeDevicePower(13757) for Easee Charger

+9:7:29.140: Wait more: 180 - 12.519 = 167.481 sec left

+9:7:29.145: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:29.166: Reached end without anything to turn on

+9:7:36.296: onPowerUpdate: Using: 1828W, Accum: 205.76 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1802.06)

+9:7:36.298: Below power Limit: 13754.704951959551

+9:7:36.300: Can use 13755W more power

+9:7:36.303: Requested power change: 13755

+9:7:36.498: attempt changeDevicePower(13755) for Easee Charger

+9:7:36.507: Wait more: 180 - 19.886 = 160.114 sec left

+9:7:36.518: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:36.525: Reached end without anything to turn on

+9:7:42.646: onPowerUpdate: Using: 1846W, Accum: 208.98 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1817.75)

+9:7:42.649: Below power Limit: 13765.560997898228

+9:7:42.651: Can use 13766W more power

+9:7:42.680: Requested power change: 13766

+9:7:42.768: attempt changeDevicePower(13766) for Easee Charger

+9:7:42.777: Wait more: 180 - 26.156 = 153.844 sec left

+9:7:42.780: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:42.782: Reached end without anything to turn on

+9:7:49.026: onPowerUpdate: Using: 1969W, Accum: 212.25 Wh, Limit: 14250 Wh, Reserved: 500W, (Estimated end: 1924.72)

+9:7:49.038: Below power Limit: 13671.625431055822

+9:7:49.061: Can use 13672W more power

+9:7:49.085: Requested power change: 13672

+9:7:49.151: attempt changeDevicePower(13672) for Easee Charger

+9:7:49.160: Wait more: 180 - 32.539 = 147.461 sec left

+9:7:49.171: aborted changeDevicePower() for Easee Charger - Must wait for toggle time to expire

+9:7:49.181: Reached end without anything to turn on

[frodeheg]

The log is shown in UTC-time, which is 1 hour behind CET-time which is the time we use in Norway. That means that the log you show is between 10:04 and 10:07 Norwegian time… so it doesn’t say anything about what happened at 03:00 unless you live around Florida, do you?

[Arunav_Mandal]

I have checked now and now the time is UTC. The previous logs were taken today morning so maybe old logs from 3am got deleted?

[frodeheg]

@bfisk

My Peugeot unfortunately has a know bug

@bfisk , can you please try the new overrides and start a new charging cycle with the current overrides:

• Pause current = 6A
• Stop current = 0A
• Minimum Charge current = 7A

(can you also confirm whether or not 6A offered current will pause the charging or if it will actually charge anything)

so you still have to start the charging cycle before or immediately after connecting the Peugeot to avoid it being disconnected, but the changes above should at least keep the connection alive until the charge cycle is over. (I hope)

[bfisk]

Thank you, I will look at it when I have a chance but I’m pretty busy the next week

[thomase]

@frodeheg

@Arunav_Mandal

Regarding the auto-start charging cycle, I think that would be a great feature. There can be a toggle option under settings. Charger On/off/Auto

1. If charger is On, then start charging immediately
2. If charger is Off, then start charging won’t start
3. If charger is Auto, then start charging during low-cost hours (or as defined in the variable under charger and price settings)

Ok, will be followed up in this ticket.

I am a little unsure of what is intended with this functionality. Maybe it matches my need.

I could imagine making a simplified management of the charging, where you don’t need to set up a charging cycle to charge. All I really need is for the piggy bank to regulate the charging current so that I do not exceed 10kW per hour.

I therefore do not want it to set the charging current to 0A, but just leave it at max all the time when not charging. Piggy bank can then regulate the charging current down if necessary to keep the 10kW limit.

It also means that I can preheat the car before I go out for a drive, without the piggy bank throttling the power to the charger. My car basically wants to have access to electricity all the time, e.g. to be able to temper the battery if necessary.

In practice, I have other apps (Android) to calculate when the car should charge, based on the fact that they know the car’s battery percentage.

[dooniem]

You are basically requesting a charge option that ignore prices, right? So adding an option under “ladestyring” named “ignore price, tariff only” would be your best option

[thomase]

Yes, could be an option if that get rid of the charge cycle planning.

[frodeheg]

@thomase

Maybe it matches my need.

It will. And yes, the current solution is pretty pointless when you have fixed prices, so I totally agree with you it should be added.

[frodeheg]

Looks like the limitation is pretty stable now.
Before anyone starts wondering where the statistics go tomorrow when the graph is reset. It’s still there, I have just not finished the interface for navigating historic statistics yet. It will be available soon though together with some other nice graphs.