Not only reported, even PRs have been sitting for months to be merged. At this point he hasn’t even commented on critical bugs that have been open for months. By critical I mean crash the backend, take the cpu to 100%, require a restart, delete and rebuild the cache, see you in an hour level bugs. On my setup this was triggered by toggling the same switch on and off a few times in quick succession, refreshing a node, deleting a node, etc.
A PR for a simple fix to a critical bug causing all Leviton devices to flood the network sat uncommitted for so long that people had to build custom docker images to run in the meantime just to stay up. This also caused the whole backend to go down with the network saturated and the CPU at 100%.
The MQTT timeout issue has been open since July. A good number of people have to delete the ozwcache file and rebuild it on startup to get it going…that has been open for months and a PR has been pending for sometime to adjust the timeout setting. Just go to the issue list on qt-openzwave and look at how many have been closed since July.
Here is fishwaldo’s github activity across all projects this year:
Clearly he owes us nothing and is free to cease development. I wish him well (and hope he’s ok!) and appreciate all of his work, but this has all of the hallmarks of a dying project not one in beta being pushed for more widespread testing. As others have said, why this is the committed path forward when he is the sole maintainer and one of the only people contributing code is an odd choice if he has other things going on. The maintainer of zwavejs2mqtt seems to have been pushed to create that because of a lack of support for the ozw 1.6 backend on which his prior project, zwave2mqtt, was also built.
@martinhjelmare any comment or insight? Your presentation suggests this will exit beta the end of Q1 but at this point many people have given up and switched back or switched to zwave2mqtt/zwavejs2mqtt. There has been practically no progress since July, at least no public progress.