Adding Hub to System Breaks Windows Desktop Controller
If the Hub is connected to the network and I launch the Windows controller, it will fail to launch until I both remove the Hub from the network, delete the BluOS folder from the app data folder, and reboot every BluOS device on my network. Once any BluOS device has knowledge of the Hub on the network, Windows controller 3.18.2 will not load.
I have been dealing with support on this for the whole week and it is the standard game of blaming my network and suggesting egregious workarounds.
Edit: The engineering team identified an actual bug, not a problem with my network, that was causing the problem. Shocking, I know! If anyone is reading this with the same problem, the bug was related to having hidden sources on players/Hub. You need to unhide all sources on Hub and players until the bug is fixed, or the windows desktop controller will fail to load.
0
-
Official comment
Devices not being found in your App are an indication of an issue of network discovery due to an error in the network allocation table (cache) in your router. Reboot your router - wait 5 minutes - then reboot all your players - wait 5 more minutes then relaunch the App. Consider using DHCP reservations as suggested.
Please continue to work with your Level 2 Support Crew Member who will be happy to help you resolve this issue.
Post is closed for comments.
Comments
1 comment