The Thinking Big blog post talks about better Z-Wave integration by replacing OpenZWave with the SiLabs public SDK.
I'm guessing this will take a while to build out. So my first question is: what do we want to do regarding improvements/etc with the current Z-Wave implementation (like converting to config entries, implementing the device registry, etc). Is it worth it to code that into the current implementation, or should we leave it as-is and focusing on building the new integration?
Outside of moving to use config entries/the device registry are there any major architecture changes that need to be addressed? Has anyone put thought into a migration process, or has it been mostly an idea but hasn't gotten a lot of attention yet?
Mostly just want to get the discussion started so we can have a solid foundation and idea where to focus development time and how to respond to any issues that crop up with the current implementation.
The Thinking Big blog post talks about better Z-Wave integration by replacing OpenZWave with the SiLabs public SDK.
I'm guessing this will take a while to build out. So my first question is: what do we want to do regarding improvements/etc with the current Z-Wave implementation (like converting to config entries, implementing the device registry, etc). Is it worth it to code that into the current implementation, or should we leave it as-is and focusing on building the new integration?
Outside of moving to use config entries/the device registry are there any major architecture changes that need to be addressed? Has anyone put thought into a migration process, or has it been mostly an idea but hasn't gotten a lot of attention yet?
Mostly just want to get the discussion started so we can have a solid foundation and idea where to focus development time and how to respond to any issues that crop up with the current implementation.