I opened an issue today (Issue #5770), as it seems the cloud service gets blocked when using the mobile app after PR #5631
The openhab cloud connector addon is not working properly to me since that PR, which removes the increase of maximum httpclient connections to a same destination for the instance used by the addon to connect to the local openhab’s rest API.
The change itself makes sense as since PR #5612 the connector is now using the common shared httpclient, so its parameters should not be changed. But this makes it allow only the “default” 2 maximum connections to the local rest api (which is a single destination), and this blocks the cloud connector.
So, as a summary, the cloud addon does not really work with, at least, the android app, which requests a long rest “event” subscription: one client works (slowly) till you start navigating through the sitemap, and at that moment it blocks and fails. Two clients at the same time block the cloud connector directly.
This discussion seems to me getting far away from a “Monthly” () release but more in the direction of a stable release. Why not do the monthly release when #5503 is solved.
There will be many more bugs but we need to get the features out to the people to get the bugs found to be able to work towards a stable release …
@cweitkamp I do not believe that the issue (897) was fixed. I upgraded to 1633 and now my visibility is completely ignored (where it used to be processed but had to be manually refreshed before). While I don’t get the error, visibility is totally ignored. Everything shows up no matter what is selected.
EDIT: The problem only seems to show itself on the beta version of the app. The non beta app seems to work.
Hope you read those threads before offending anyone …
Its not the goal to solve all problems before releasing a milestone but those that affect many users. The bugs which have been named during duscussion are all solved.
So the question regarding what is missing to get the milestone out is quite valid.
Yes, the idea is that milestone builds are released roughly each month and we all know why that process has stalled.
More importantly though, they should not have any (known) critical issues.
(Strike-through by me; these issues have been fixed)
I’m sorry that I value the opinion of those who contribute to the code higher than the opinion of the ones that don’t.