Roadmap API implementation of new features

Feller-AG / wiser-api

MIT License

15 stars 1 forks source link

Roadmap API implementation of new features #13

Open mpbzh opened 7 months ago

mpbzh commented 7 months ago

The Wiser ecosystem will soon gain new features: A new device generation, room thermostats, heating controller and a weather station (See homepage for more details, German only).

As of now the features are planned on launching in July of this year.

What's the road map on implementing these featuries into the Wiser API? Ideally plugin developers would get some lead time to be able to integrate the functionality into their integrations.

woodworm commented 6 months ago

🆕 There will be an update later this month!

woodworm commented 6 months ago

Preliminary information:

A new μGWv2 is available now! (Wiser WLAN-Bedienaufsatz Generation B)
The µGWv2 comes directly with the API 6.0.X
The API 6.0.X is 100% backwards compatible with the API 5.1.X
For the µGWv1 there will be no API 6.0.X
For µGWv1 there will be a 5.X.X update at a later time
But the µGWv1 will never support all functions of API 6.0.X like thermostats, heating-controller, weather-station
The performance of the µGWv2 is extremely cool 🤭

mpbzh commented 6 months ago

My apartment with Gen B devices is ready, looking forward to the release of the 6.0.x docs!

kinnkler commented 6 months ago

@woodworm Is there a reason to switch to the µGWv2 if i don't have a thermostats, heating-controller or weather-station? Are there any other features regarding push buttons exclusive to µGWv2?

woodworm commented 6 months ago

The µGWv2 is a must 😄! No... As long as everything worked so far, I wouldn't change. It gets really exciting with the new products.

senadjukic commented 2 months ago

Could you elaborate a bit more on the performance difference between µGWv1 and µGWv2? Could you please share any measurements (e. g. on target_state calls)?

Is the current Android app (heavily) impacted by the performance difference, or was it just that the sessions don't keep alive and therefore have always to reconnect?

woodworm commented 1 month ago

The service "api/loads//target_state" is sent over the kPlus bus, so it’s not much faster on the µGWv2 because the kPlus bus is the bottleneck. Of course, there are many services, such as "api/loads", that are much faster with the µGWv2. However, this is especially noticeable in large systems (services with large response bodies).