I’d suggest then to get a debug log to try and find out what is happening. The issue is that the device initialisation is not complete - the question is why and the debug logs are normally the best way to find out.
Take a look at the binding docs in the When things don't go as planned section.
Thanks. This looks like another issue with the inclusion. From your log, and the extra debug I added on this the other day, I think I now know what is causing this.
Something in the OH core is now blocking when an event is called. The binding sends an event to alert the user when certain things happen. This was originally added to the binding 3 1/2 years ago but now seems to not work .
I will remove this feature and we can see if it resolves the issue.
Well, I’m not really sure about the schedule for M2 - I’ve not seen anything official about this, but maybe I missed it. Therefore, I probably wouldn’t wait for M2 if you need features/database etc from the later binding.