spot-hinta-fi / shelly Goto Github PK

Hi,
at first thank you for your hard work.

I would like to ask about the proper way of updating your scripts on a Shelly device. I use provided URL (http://api.spot-hinta.fi/Shelly/library) to download/install scripts on the Shelly.

So when there is a new version of the script, should I delete the existing script and then use "Insert code" to install the newest version and then I would need to manually set parameters again?

HI!

I saw on when running the monitoring diagnostics on my Shelly 1 PRo and the fine heating hotspot script that it looks like the api call is not responding right:

shelly_http.cpp:184 0x3ffe2320 HTTPS GET https://api.spot-hinta.fi/JustNowRank/4/5?boosterHours=04,17&priorityHours=23,00,01,02,03,04,05,06&priorityHoursRank=4&region=SE3 (SSL CA *)
09:09:12
shelly_http.cpp:71 0x3ffe2320 HTTP got 400 Bad Request and 3 byte response

Add a configuration option to the script (e.g., rank and price) that allows you to ignore the last hours of the day if there are cheaper hours after midnight.

Problem: When the cheapest hours are checked for each day, there come situations when the relay is turned on for the last hours of the day, but just after midnight, there are even cheaper hours. I use Shelly with a water boiler, and water is getting heated up during the last "expensive" hours of the day, even if it would be okay to delay the heating to the next day as there is not much water usage before midnight.

This picture illustrates the problem.

Possible solution: Make a configuration switch that ignores X last hours of the day (even if they're the cheapest) if there are cheaper hours after midnight. The number of hours checked after midnight should be, e.g., 5-6 (or configurable). I want the heating to be completed during the night.

Last hours of today (2023-02-10) are cheaper than any hours of tomorrow (2023-02-11).

Would be cool if we could take advantage of this and, for example, start heating a little bit earlier during the cheaper hours.

Something like optimizeLastHours=2 would allow today's 22.00-23.59 to be used for next day's ranking.

I'm not sure if this is even possible as we would probably need to take yesterday's ranking also in to account.

Anyway, just wanted to drop the idea here if smarter minds can work this through and you feel this would be worth doing.

Sorry to bother again.

I was testing /JustNowRankNight endpoint at some point at 2023-02-23 22.00-23.59 and everything seemed to be working fine (/JustNowRankNight?Rank=9 returned 200).

However, during next day, at 3AM I'm only getting error 400. Even without Rank parameter. Is there something I'm missing here (again)?

Few sample requests and responses:

Request URL: https://api.spot-hinta.fi/JustNowRankNight
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 20.107.224.17:443
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 3
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Feb 2023 00:59:33 GMT
Request-Context: appId=cid-v1:bcaa7eb9-5ac3-497d-9ac5-397bee643201

Request URL: https://api.spot-hinta.fi/JustNowRankNight?rank=4
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 20.107.224.17:443
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 3
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Feb 2023 01:03:33 GMT
Request-Context: appId=cid-v1:bcaa7eb9-5ac3-497d-9ac5-397bee643201

Request URL: https://api.spot-hinta.fi/JustNowRankNight?rank=5
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 20.107.224.17:443
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 3
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Feb 2023 00:59:09 GMT
Request-Context: appId=cid-v1:bcaa7eb9-5ac3-497d-9ac5-397bee643201

Request URL: https://api.spot-hinta.fi/JustNowRankNight?rank=4
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 20.107.224.17:443
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 3
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Feb 2023 00:56:19 GMT
Request-Context: appId=cid-v1:bcaa7eb9-5ac3-497d-9ac5-397bee643201

Request URL: https://api.spot-hinta.fi/JustNowRankNight?Rank=9
Request Method: GET
Status Code: 400 Bad Request
Remote Address: 20.107.224.17:443
Referrer Policy: strict-origin-when-cross-origin
Content-Length: 3
Content-Type: application/json; charset=utf-8
Date: Fri, 24 Feb 2023 01:25:23 GMT
Request-Context: appId=cid-v1:bcaa7eb9-5ac3-497d-9ac5-397bee643201

Feature request:
_hieman "ongelmana" se että jos on määritellyt 4 halvinta tuntia esim LVV:lle ja käytännössä varaaja suoriutuu työstään 2 tunnissa, niin se käyttää ne kaksi kalleinta tuntia, jos sähkön hinta on jokaisella tunnilla aina naksun halvempi kuin edellisellä.

Lisäksi tuo tuntuu tapahtuvan aika usein pe-la välillä, kun pörssihinta yleens perjantai-iltana laskee, jolloin perjantain halvimmat tunnit asettuvat sinne iltaan, ja sitten uusi pörssipäivä lauantainen kyykkää usein selkeästi alemmas, niin sitten kun se kyykännyt hinta olisi käytössä varaja on lämmin._

-->
_Suurempi äly vaatisi tiedon varaajan lämpötilasta tai tarkemmin ottaen tiedon kuinka pitkä aika lämmitykseen tarkasti ottaen tarvitaan. Se onnistuisi jos tietäisi 1) lämpötilan nyt 2) varaajan tilavuus 3) vastuksen teho 4) haluttu loppulämpö.

Eli oikeastaan tärkein tieto olisi varaajan lämpötila. Sitä vain helposti suurimmasta osasta varaajia ei saa._

source: https://lampopumput.info/foorumi/threads/spot-hinta-fi-yksinkertainen-p%C3%B6rssiohjaus-api-ja-sit%C3%A4-k%C3%A4ytt%C3%A4v%C3%A4t-automaatioskriptit.33938/page-36

Olen testaillut tuota skriptiä "Shelly-Rank-and-Price.js" muutaman poäivän ajan ja pörssisähkäsopimus astuu voimaa vajaan viikonn päästä.

Kun Shelly muuttaa releen statusta, menee siinä ainakin oman lämpöpumpun (IVT) tapauksessa parikin minuuttia, ennen kuin pumppu sammuttaa itsensä, jos sillä on aktiivinen hetki päällänsä. Tällöin pumppu saattaa syödä tuon pari minuuttia kallista sähköä. Voisiko siis skriptiin asjatella lisättävän jonkun uuden parametrin tyyliin "MachineDelay_min" jonka asettavamlla vaikka itseni tapuksessa arvoon "2" Shelly osaisi aikaistaa noita avaa-sulje ja sulje-avaa toimenpiteitä tuon viiveen verran? Ei menisi senttiäkään ylimääräistä sähköyhtiölle... ;)

Muuten kyllä näyttä oikein hyvältä ja eiköhän täsdtä kahvirahat lähde matkaan...

Hi! Thanks for all so far!

Few things in Shelly-Minimal_water_heating.js could use clarification:

let Rank = "4"; // How many hours relay is on (cheapest hours)
More descriptive name would be good. Such as HowManyHours.

let PriceAllowed = "3"; // Heating is always on, when price is below this (Euro cents)
More descriptive name would be good. Such as PriceLimitAO.

let PriorityHoursRank = "3"; // This limits how many hours are prioritized (i.e. 3 cheapest hours from priority hours)

• More descriptive name would be good. Such as HowManyPriorityHours
• What if none wanted?

let PriorityHours = "00,01,02,03,04,05,06"; // These hours are prioritized (smallest ranks to these hours, f.ex. if you want to heat boiler during night)
What if I do not want any priority hours - should this be left empty? Or "99" like "boosterhours"? Comment does not tell this. IMO empty "" would be best if none wanted.

Use "99" if none wanted.
Same as above.

Shelly.call("HTTP.GET", { url: urlToCall, timeout: 15, ssl_ca: "*" }, RunResponse);

function RunResponse(result) {

I guess the script should check the response so it accepts only integer number (the hour/rank or such) OR force the response to be an integer number, yes? Currently it seems to trust the response 'blindly', which is huge security flaw?

Feature request:
_API voisi ilmoittaa Rank:in lisäksi myös persentiilin (kuinka suuri osa hinnoista on yhtä suuria tai pienempiä kuin kyseinen hinta).

Jos haluaisi lämmittää puolet vuorokaudesta, niin ehto "currentPrice.Percentile <= 50" hoitaisi homman. Vastaava Rank:ia käyttävä ehto on "currentPrice.Rank <= 12".

Tuota persentiiliä voisi käyttää, oli hinnat ilmoitettu sitten tunnin tai vartin jaksoille.

Vartin jaksoja on vuorokaudessa 96 kpl, joten "persentiili" kääntyy arkikielessä melkein suoraan jaksojen lukumääräksi._
source: https://lampopumput.info/foorumi/threads/spot-hinta-fi-yksinkertainen-p%C3%B6rssiohjaus-api-ja-sit%C3%A4-k%C3%A4ytt%C3%A4v%C3%A4t-automaatioskriptit.33938/page-36

Are negative values allowed for PriceAlwaysAllowed?

I tried to use negative value but seems that relay still got turned on when price hit zero.

This is a bit problematic for us with a bad electricity deal... 😅

Has there been some changes in /CheapestPeriodTodayCheck endpoint?

I'm calling the API like this:

https://api.spot-hinta.fi/CheapestPeriodTodayCheck/2?priorityHours=0,1,2,3,4,5,6

For some reason this failed to start my boiler today. I was expecting it to start at 02:00.

Am I missing something here?

Not an issue but more of a question.

This is not directly related to Shelly script but to /JustNowRankDynamic endpoint.

Could it be possible to have a little bit more information how the ranking hours are decided in the backend? I mean if it's possible to do that in a few sentences.

What's the time frame for ranking system? Is it something like minimum temperature for the whole day or for the next 48 hours or something like that?

Anyway I'm going to test it soon. Thanks again for these superb scripts!

Yösähkön tunnit taitaa olla oletusarvoisesti väärin. "PriceModifier_Hours: [22, 23, 0, 1, 2, 3, 4, 5, 6, 7]" pitäisi olla "PriceModifier_Hours: [22, 23, 0, 1, 2, 3, 4, 5, 6]".

Hi.

Is it possible to invert the I/O status(?) for ”Shelly-Minimal_water_heating.js”? So when price is high, shelly turns on.

With current script it’s the other way around: Low price = shelly on.

Thanks

On Swagger documentation it states that rankAdjusterPercentage parameter must be value of 0-20.

However, nothing is said about that in the Shelly script:
https://github.com/Spot-hinta-fi/Shelly/blob/main/Scripts/Shelly-Outdoor_temperature_adjusted_heating.js

So the question is: what are the accepted values?

IMO it would make sense that the value could also be higher than 20 (for example when rankAtZeroDegrees === 1).

Hi!

Shelly-Rank_and_Price_limit.js has 'Region' setting for each relay. I believe region is always same for all relays, right? If yes there should be only one global setting for region.

Hi!

Why do my script sometimes go to Backup, even though it should’t?

Testing request string (https://api.spot-hinta.fi/JustNowRank/6/2?boosterHours=99&priorityHours=02,03,04,21&priorityHoursRank=2&region=SE3) in web browser, the respons is: Could not load price information.

Btw, thank you for all your effort.

Regards Henrik

Hi! I think my Shelly 1PM Mini Plus has a working internet connection as it shows time right. The monitoring script says internet connection is not working - can it be trusted?

FYI: I have another 1PM Mini Plus running Minimal Heating script and also a script that HTTP POST's the data to cloud server. It has had a robust internet during past few days and latest data was stored to the cloud 1 minute ago.

If minimumRank is set to 24 should the endpoint always return with 200 OK?

If not, could you give some hints why not... 😅

Having some hard time understanding how 'minimumRank` should work.

Here's the URL I'm playing with:
https://api.spot-hinta.fi/JustNowRankDynamic?rankAtZeroDegrees=4&rankAdjusterPercentage=10&minimumRank=24&priceAlwaysAllowed=0&postalCode=20100&priorityHours=0%2C1%2C2%2C3%2C4%2C5%2C6&priceModifier=-100&debugMode=true

Thanks again for these scripts! 💯