We tried to keep z-wave API as much compatible as possible. But there's actually a lot of changes under the hood.zoic22 wrote:I don't see any big difference in API for now
Key changes are:
1) The system is now fully modular. Everything (even web server and z-wave core) is now a JS object available in HA, and can be loaded and unloaded any time.
2) Added a new proxy API to access resources from intranet (like IP cameras streams) even when accessing RaZberry remotely.
3) Support for native modules which are loaded dynamically. You may write a C++ library, and it will be exposed to JS.
4) All requests are now handled inside JS. So it is possible to add custom JS handler for any url, not only under /ZAutomation. A new parser processes requests and parses forms (both application/x-www-form-urlencoded and multipart/form-data) into JS objects, so it very easy to access forms data now.
5) Support for WebSockets, so you can push changes to client (it is not yet implemented in HA though).
6) Initial support of HomeKit. It is still under development, but it is already possible to experiment with it.
7) A brand new Expert UI for network management (the old one is still available).
8) Redesigned module dependency mechanism in HA.
9) And a lot of improvements in Z-Wave core for better devices support, of course.
We also made a huge effort on stability improvements. Please monitor memory and CPU usage to see if there are some problems remaining.