You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
you have have written a very cool adapter with cool addons. The addon features are great but can only be used in conjunction with tibber. The only problem (for me) is, that i live in austria and there is no tibber available. But other providers which deliver the data needed. Do you have plans to support additional dynamic price input values eg. not from tibber but e.g from awattar or someone else?
so your tool could be used more universally
what do you think?
The text was updated successfully, but these errors were encountered:
tminimax
changed the title
tibberlink
additional channel for priced from different providers (austria)
Jan 30, 2025
tminimax
changed the title
additional channel for priced from different providers (austria)
additional channel for prices from different providers (austria)
Jan 30, 2025
It's not planned - also that's not fitting to the idea of ioBroker at all.... also having the calculators inside TibberLink adapter isn't optimal. Best would be to have this split into two adapters....
Technically it would be quite easy to use external price inputs as JSON data ..... do you have this for Awattar already working?
yes, for awattar it is running, but no calculations. so the idea of 2 separat adapters would be great....that´s why i was asking. i thought i could use your cool calculations....
Hi,
you have have written a very cool adapter with cool addons. The addon features are great but can only be used in conjunction with tibber. The only problem (for me) is, that i live in austria and there is no tibber available. But other providers which deliver the data needed. Do you have plans to support additional dynamic price input values eg. not from tibber but e.g from awattar or someone else?
so your tool could be used more universally
what do you think?
The text was updated successfully, but these errors were encountered: