Snapshots are where problems like these are discovered so they can be fixed. Your reporting the problems is exactly what you should do when you encounter errors like this in any version of OH. Thank you for reporting. I haven’t read the linked to topic yet but can I assume that an issue was filed?
But if you expect the Snapshots to be error free or to interpret errors you discover in the snapshots to mean that the developers don’t care about any particular binding or platform your expectations from the snapshots are unreasonable.
We have been spoiled a lot by the fact that OH 2 was so stable for the past year or so that perhaps we have grown to expect the snapshots to not experience these types of errors. But it is important to realize that it isn’t until the nightly builds and the snapshots that all the changes from all the teams contributing to all the github repos first come together. With a change as big as the merge of ESH back into OH, there is going to be many problems like these.
It has been repeated many times on this forum that the snapshots are not suitable for production use right now and will not be so until the next milestone is released. So only run the snapshots if you are willing to serve the role of tester which means risking errors and diligently reporting errors you encounter.
So what can we do as users? Report problems we see like these and file issues. Without the issues the developers may not become aware there even is a problem. It’s not like each and every developer has an RPi, Windows machine, Mac, QNAP, and Synology to test every change they make. They rely on us to help test and report problems by running the snapshots.
If you are not willing to do this, then you should be running the Milestone builds or release builds. If you are willing to do this, please do not interpret errors seen in the snapshots as neglect or malpractice on the part of the developers. That is unfair and unreasonable.