Since update on Saturday, I haven't noticed any major issues and love the update.
Something separate from the update, has anyone had any issues with websockets not reporting events at times from remote to server hub? Seems to be 1-2x a week until I turn the Remote Hub off/on on the server hub to reestablish the web sockets connection. I had that issue now for a long time, not related to the 1.5 update at all. HTTP seemed to be worse with that regard when I tried it before months back. I wonder if it's more hub related though maybe with how HubConnect is getting the events from Event Sockets, I did try deleting all HubConnect apps/drivers along with code and recreated everything last month along with soft resets of all 3 hubs but didn't help at all with fully fixing that issue.
No errors shows in logs either so not really sure why that happens. Was mostly curious if anyone has had issues with events not feeding at times from remote hubs to server hub until the Remote Hub was turned off then on to reestablish the Web Socket connection with remote hub.
All 3 hubs are on the same LAN and not seeing too many disconnects between the hubs per logs unless I reboot the hubs for things like updates which would obviously show the errors for no connection between remote/server hubs.
Is Maker API a possible option someday in the future for getting events instead of Event/Web Sockets? Not sure if that would give HubConnect everything Event Sockets does or would even work since I barely played around with Maker API yet myself.
I remember seeing this post previously regarding Maker API, not sure if HubConnect uses the same methods though:
