v0.2.0 - New API types: widgets, users

• Add API type to select which API call to use:
  • users (NEW)
  • installations
  • widgets (NEW)
  • Dynamic ESS
• Code cleanup
• If storing the global data, store it in an object, depending on the selected api call
• The msg.topic reflects the selected api call
• Update documentation

Full Changelog: v0.1.4...v0.2.0

v0.1.4

• Allow context variable to be used as site id (issue #13) - Instead of filling out the number of the VRM site id in the box, you can also use context variables, e.g. {{flow.siteId}} or {{global.vrmId}}. This allows to query the site that has been set in this context field. Of course you need to make sure that context contains a valid VRM site id first. (thanks @danikalt!)

Full Changelog: v0.1.3...v0.1.4

v0.1.3

What's Changed

• align start and end to full hours by @codeworkx in #11

Full Changelog: v0.1.2...v0.1.3

v0.1.2

• Allow the vrm_id to be empty (issue #10)

Full Changelog: v0.1.1...v0.1.2

v0.1.1

• Retrieve data from the dynamic ESS api
• Add option to store the retrieved data in the global context
• Fix a npm test complaint about d_start and d_end not in camelcase
• Update documentation

Full Changelog: v0.1.0...v0.1.1

v0.1.0

What's Changed

• Treat the access token as a secret, do not export it by @codeworkx in #9

Full Changelog: v0.0.11...v0.1.0

v0.0.11

What's Changed

• fix calculation of beginning of yesterday by @codeworkx in #8

Full Changelog: v0.0.10...v0.0.11

v0.0.10

What's Changed

• Add option for installation statistics to choose between local time and UTC by @codeworkx in #7

Full Changelog: v0.0.9...v0.0.10

v0.0.9

What's Changed

• fix end of day calc, add options for yesterday, add additional usefull attributes by @codeworkx in #6

v0.0.8

• added attributes for consumption forecast and energy flows
• extend available values for the parameter start by the value beginning of the day

Thanks @codeworkx