hombach / ioBroker.tibberlink

links tibber API data to be used in ioBroker
https://github.com/hombach/ioBroker.tibberlink
GNU General Public License v3.0
23 stars 5 forks source link

Smart Battery Buffer #297

Closed maduuto closed 6 months ago

maduuto commented 8 months ago

Describe the bug
Smart battery buffer does not activate

To Reproduce
See logfiles, smart battery buffer is calculating but have not been switched on when cheap times are arrived. It seems that the cheap time for spb is not recalculated on 00:00 for the new day.

Screenshots & Logfiles

2024-01-21 23:22:26.888 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - cheap hours: 0.1878,0.1887 2024-01-21 23:22:26.889 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - normal hours: 0.1899,0.1952,0.1956,0.1971,0.1977,0.1994,0.2007,0.2008,0.2013,0.2022,0.2029,0.2035,0.204,0.2042,0.2054,0.2076,0.2086,0.2103,0.2114,0.2127,0.2161 2024-01-21 23:22:26.889 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - expensive hours: 0.2225 2024-01-21 23:22:26.890 - debug: tibberlink.0 (854331) calculator channel: 0-smart battery buffer; setting first state: 0_userdata.0.Strom.Batterie_Netzladung_guenstigerstrom to false 2024-01-21 23:22:26.890 - debug: tibberlink.0 (854331) calculator channel: 0-smart battery buffer; setting second state: 0_userdata.0.Strom.Batterieentladung_beenden to false

Versions:

hombach commented 8 months ago

sorry, the log of PricesToday and the config of smart battery buffer would be needed to judge the situation. also your log doesn't content anything about 00:00 !?

maduuto commented 8 months ago

2024-01-22 09:42:43.110 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - cheap hours: 0.1489,0.149
2024-01-22 09:42:43.110 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - normal hours: 0.1651,0.1667,0.1694 2024-01-22 09:42:43.110 - debug: tibberlink.0 (854331) calculator channel 0 SBB-type result - expensive hours: 0.1866,0.1911,0.2023,0.2094,0.2104,0.2107,0.2108,0.2115,0.2122,0.214,0.2143,0.2149,0.215,0.2162,0.222,0.2222,0.2273,0.2286,0.235 2024-01-22 09:42:43.111 - debug: tibberlink.0 (854331) calculator channel: 0-smart battery buffer; setting first state: 0_userdata.0.Strom.Batterie_Netzladung_guenstigerstrom to false 2024-01-22 09:42:43.111 - debug: tibberlink.0 (854331) calculator channel: 0-smart battery buffer; setting second state: 0_userdata.0.Strom.Batterieentladung_beenden to true

this was the last time of calculation

2024-01-23 00:59:01.448 - debug: tibberlink.0 (854331) Got prices today from tibber api: [{"total":0.1622,"energy":0.0162,"tax":0.146,"startsAt":"2024-01-23T00:00:00.000+01:00","currency":"EUR","level":"CHEAP"},{"total":0.1549,"energy":0.0101,"tax":0.1448,"startsAt":"2024-01-23T01:00:00.000+01:00","currency":"EUR","level":"CHEAP"},{"total":0.1541,"energy":0.0094,"tax":0.1447,"startsAt":"2024-01-23T02:00:00.000+01:00","currency":"EUR","level":"CHEAP"},{"total":0.1479,"energy":0.0042,"tax":0.1437,"startsAt":"2024-01-23T03:00:00.000+01:00","currency":"EUR","level":"CHEAP"},{"total":0.1551,"energy":0.0102,"tax":0.1449,"startsAt":"2024-01-23T04:00:00.000+01:00","currency":"EUR","level":"CHEAP"},{"total":0.1896,"energy":0.0392,"tax":0.1504,"startsAt":"2024-01-23T05:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.214,"energy":0.0598,"tax":0.1542,"startsAt":"2024-01-23T06:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2339,"energy":0.0764,"tax":0.1575,"startsAt":"2024-01-23T07:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.226,"energy":0.0698,"tax":0.1562,"startsAt":"2024-01-23T08:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2261,"energy":0.0699,"tax":0.1562,"startsAt":"2024-01-23T09:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2143,"energy":0.06,"tax":0.1543,"startsAt":"2024-01-23T10:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2141,"energy":0.0598,"tax":0.1543,"startsAt":"2024-01-23T11:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2133,"energy":0.0591,"tax":0.1542,"startsAt":"2024-01-23T12:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2137,"energy":0.0594,"tax":0.1543,"startsAt":"2024-01-23T13:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2175,"energy":0.0627,"tax":0.1548,"startsAt":"2024-01-23T14:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2317,"energy":0.0746,"tax":0.1571,"startsAt":"2024-01-23T15:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2369,"energy":0.079,"tax":0.1579,"startsAt":"2024-01-23T16:00:00.000+01:00","currency":"EUR","level":"EXPENSIVE"},{"total":0.24,"energy":0.0816,"tax":0.1584,"startsAt":"2024-01-23T17:00:00.000+01:00","currency":"EUR","level":"EXPENSIVE"},{"total":0.2435,"energy":0.0845,"tax":0.159,"startsAt":"2024-01-23T18:00:00.000+01:00","currency":"EUR","level":"EXPENSIVE"},{"total":0.2316,"energy":0.0746,"tax":0.157,"startsAt":"2024-01-23T19:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2167,"energy":0.062,"tax":0.1547,"startsAt":"2024-01-23T20:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.2069,"energy":0.0537,"tax":0.1532,"startsAt":"2024-01-23T21:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.1969,"energy":0.0454,"tax":0.1515,"startsAt":"2024-01-23T22:00:00.000+01:00","currency":"EUR","level":"NORMAL"},{"total":0.1825,"energy":0.0333,"tax":0.1492,"startsAt":"2024-01-23T23:00:00.000+01:00","currency":"EUR","level":"CHEAP"}] Force: true

This is the price for today (next day)

No i mean doesn't it need to be recalculated at 00:00?

maduuto commented 8 months ago

So efficiency lost have been to 0.15 and hours to 2. When i manually changing the efficieny loss to like 0.16 it triggers the automation and immediately the battery charging begins because it is the expected cheap time. So the automation only reacts to triggers which are not time or cost based, like restart or change of settings?

hombach commented 8 months ago

Now I got your point..... Calculator is triggered by changes and when current price is updated... watch out for log sections like this:

2024-01-23 19:00:53.179 - debug: tibberlink.0 (203583) Got current price from tibber api: {"total":1.017,"energy":0.7196,"tax":0.2974,"startsAt":"2024-01-23T19:00:00.000+01:00","currency":"SEK","level":"VERY_EXPENSIVE"} Force: undefined 2024-01-23 19:00:53.180 - debug: tibberlink.0 (203583) Cron job CurrentPrice - okPrice: true 2024-01-23 19:00:53.181 - debug: tibberlink.0 (203583) calculator channel: 4-best price LTF; setting state: 0_userdata.0.best_cost_LTF to false 2024-01-23 19:00:53.182 - debug: tibberlink.0 (203583) calculator channel: 5-best single hours LTF; setting state: 0_userdata.0.best_single_hours_LTF to false 2024-01-23 19:00:53.183 - debug: tibberlink.0 (203583) calculator channel: 6-best hours block LTF; setting state: 0_userdata.0.best_hours_block_LTF to false 2024-01-23 19:00:53.225 - debug: tibberlink.0 (203583) calculator channel: 0-best price ; setting state: 0_userdata.0.example_state to true 2024-01-23 19:00:53.229 - debug: tibberlink.0 (203583) calculator channel: 1-best single hours ; setting state: 0_userdata.0.test2 to false 2024-01-23 19:00:53.231 - debug: tibberlink.0 (203583) calculator channel: 2-best hours block ; setting state: 0_userdata.0.test_block to false 2024-01-23 19:00:53.232 - debug: tibberlink.0 (203583) calculator channel: 3-best price ; setting state: 0_userdata.0.String_Test to NO 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - cheap hours: 0.1767,0.2473,0.2575,0.2626,0.3424,0.4247,0.4829 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - normal hours: 0.495,0.4971,0.4975,0.5104,0.5293,0.5349,0.5424 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - expensive hours: 0.5552,0.5898,0.595,0.6972,0.8624,0.9761,1.017,1.0399,1.0659,1.0897 2024-01-23 19:00:53.339 - debug: tibberlink.0 (203583) calculator channel: 7-smart battery buffer; setting first state: 0_userdata.0.SBB-charge to False 2024-01-23 19:00:53.339 - debug: tibberlink.0 (203583) calculator channel: 7-smart battery buffer; setting second state: 0_userdata.0.SBB-feedIn to True 2024-01-23 19:00:54.243 - debug: tibberlink.0 (203583) Got consumption data from Tibber Server for home: 96a14971-525a-4420-aae9-e5aedaa129ff

maduuto commented 8 months ago

Yeah but this doeant work. It didnt stop charging on expensive time today because it was not triggered

hombach @.***> schrieb am Di., 23. Jan. 2024, 20:35:

Now I got your point..... Calculator is triggered by changes and when current price is updated... watch out for log sections like this:

2024-01-23 19:00:53.179 - debug: tibberlink.0 (203583) Got current price from tibber api: {"total":1.017,"energy":0.7196,"tax":0.2974,"startsAt":"2024-01-23T19:00:00.000+01:00","currency":"SEK","level":"VERY_EXPENSIVE"} Force: undefined 2024-01-23 19:00:53.180 - debug: tibberlink.0 (203583) Cron job CurrentPrice - okPrice: true 2024-01-23 19:00:53.181 - debug: tibberlink.0 (203583) calculator channel: 4-best price LTF; setting state: 0_userdata.0.best_cost_LTF to false 2024-01-23 19:00:53.182 - debug: tibberlink.0 (203583) calculator channel: 5-best single hours LTF; setting state: 0_userdata.0.best_single_hours_LTF to false 2024-01-23 19:00:53.183 - debug: tibberlink.0 (203583) calculator channel: 6-best hours block LTF; setting state: 0_userdata.0.best_hours_block_LTF to false 2024-01-23 19:00:53.225 - debug: tibberlink.0 (203583) calculator channel: 0-best price ; setting state: 0_userdata.0.example_state to true 2024-01-23 19:00:53.229 - debug: tibberlink.0 (203583) calculator channel: 1-best single hours ; setting state: 0_userdata.0.test2 to false 2024-01-23 19:00:53.231 - debug: tibberlink.0 (203583) calculator channel: 2-best hours block ; setting state: 0_userdata.0.test_block to false 2024-01-23 19:00:53.232 - debug: tibberlink.0 (203583) calculator channel: 3-best price ; setting state: 0_userdata.0.String_Test to NO 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - cheap hours: 0.1767,0.2473,0.2575,0.2626,0.3424,0.4247,0.4829 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - normal hours: 0.495,0.4971,0.4975,0.5104,0.5293,0.5349,0.5424 2024-01-23 19:00:53.338 - debug: tibberlink.0 (203583) calculator channel 7 SBB-type result - expensive hours: 0.5552,0.5898,0.595,0.6972,0.8624,0.9761,1.017,1.0399,1.0659,1.0897 2024-01-23 19:00:53.339 - debug: tibberlink.0 (203583) calculator channel: 7-smart battery buffer; setting first state: 0_userdata.0.SBB-charge to False 2024-01-23 19:00:53.339 - debug: tibberlink.0 (203583) calculator channel: 7-smart battery buffer; setting second state: 0_userdata.0.SBB-feedIn to True 2024-01-23 19:00:54.243 - debug: tibberlink.0 (203583) Got consumption data from Tibber Server for home: 96a14971-525a-4420-aae9-e5aedaa129ff

— Reply to this email directly, view it on GitHub https://github.com/hombach/ioBroker.tibberlink/issues/297#issuecomment-1906794507, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANHXFJQM2BQH3S66FBAN3YQAGJ7AVCNFSM6AAAAABCEZTLDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWG44TINJQG4 . You are receiving this because you authored the thread.Message ID: @.***>

hombach commented 8 months ago

do you get "Cron job CurrentPrice - okPrice: true" in log?

maduuto commented 7 months ago

no, never in the last day only false. But everything works except the automation

hombach commented 7 months ago

doesn't look like everything works - if you only get "okPrice: false" ....

Are the time stamp and last changed match to the cuttent system hour AND also to the value in "startsAt" ??

image

maduuto commented 7 months ago

No, last time was at 28. January 3:22

maduuto commented 7 months ago

log always shows:

Error (Too Many Requests) occured during: -pull of current price- : --

maduuto commented 7 months ago

maybe this helps

Error (Unknown Status) occurred during: -force pull of prices today- : Cannot read properties of undefined (reading 'total') --
hombach commented 7 months ago

log always shows:

Error (Too Many Requests) occured during: -pull of current price- : --

so looking at past logs you posted - you sometimes get data, but in between Tibber is blocking your requests. The "Too Many Requests" message is directly from Tibber server. Please halt the adapter for min 5h AND don't use any second method to call your account.

Also there is a fix for a feature in this TibberLink adapter to slow down requests when no connect is possible - unfortunately this feature was buggy, so didn't change the timing.... It is fixed in 2.1.1 - Maybe this helps in your case.

[Also the screenshots of your complete TibberLink Calculator config might help to discover a glitch. ;) ]

hombach commented 7 months ago

@maduuto : any news? Adapter working now as expected?

maduuto commented 7 months ago

no sorry, error messages still appear, but every live information like actual usage is available. Everything works bit still errors like false pulling price and Error (Unknown Status) occurred during: -pull of prices today- : Cannot read properties of undefined (reading 'total')

maduuto commented 7 months ago

also some error like

[verifyStateAvailable](Homes.1cb43540-a913-4fde-9c6b-7a418d4b4e07.CurrentPrice.startsAt): State does not exist. --
hombach commented 6 months ago

What is your current status of your Tibber contract? Pulse is active - but do you currently have an hourly contract? Or monthly pricing?

maduuto commented 6 months ago

Yes, normal hour contract with pulse.

maduuto commented 6 months ago

But i have seen this is a second "home", which is an old contract bevore moving years ago. tibber has saved it. Think the issue is that live measurement is active for all homes, i can not activate it differently for the standard home and deactivate it for the other home which is not active anymore

hombach commented 6 months ago

Did you try to deactivate this obsolete home in config? image

maduuto commented 6 months ago

didnt work very well during saving, now tibber has removed the old home, i restartet the script and now it works

hombach commented 6 months ago

Great! So this issue is fixed - how did you manage to get it deleted? Just asked the support? Looks like there are more users with the same problem.

maduuto commented 6 months ago

Yes, was deleted within one working day. But on tibberlink one or two days later, i had to restart the adapter and manually reactivate the right home, than it worked.