Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request API access #2

Open
CFenner opened this issue Jan 18, 2018 · 2 comments
Open

request API access #2

CFenner opened this issue Jan 18, 2018 · 2 comments

Comments

@CFenner
Copy link
Owner

CFenner commented Jan 18, 2018

To request API access, send a mail to support@smappee.com and provide the following informations:

  • full name
  • user name
  • serial number
@c-m0s
Copy link

c-m0s commented Dec 7, 2018

Hi @CFenner
thanks a lot for you Smappee Module, I'd love to add it to my mirror.

Unfortunately, SMAPPEE replied to me with this message:

Our API has become a paying feature I will forward you for this matter to my sales colleague.
https://support.smappee.com/hc/en-us/articles/202153935-Where-can-I-find-the-API-documentation-

and further more:

For the usage of our API, we ask for a small recurring fee of € 2,50 per month for Smappee Energy/Solar, to be paid
upfront for 24 months (so € 60 for 2 years). In case of a Smappee Plus, the fee is €3 per month, so €72 for 2 years.
After reception of the payment, our support team activates the API account.

I personally find that's too much for this single MagicMirror-Module use. And I don't have other applications in mind right now to make use of the API.

SMAPPEE also writes

We also offer free alternatives, like :

Do you know these solutions? Would it be easily possible to modify your module to use these interfaces?

@CFenner
Copy link
Owner Author

CFenner commented Dec 7, 2018

Hi @cmose,

Great that you would like to use the module!
I’ve dismantled my mirror, so I didn’t notice the API change. Sad to hear about that and the price.

So I know MQTT but I fear that in that case you need to take case about the data persistence yourself. I could imagine the following setup:

  1. Mqtt Server collecting the measurements
  2. Influx dB with mqtt Interface to store the data points
  3. Custom API endpoint serving the same data as the Smappee api.

This would only require a change of the endpoint in the module but requires some serious coding effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants