How far from the hub are you when you try to use the remote or phone and how well hidden is the hub? If it's behind several barriers, it can't be expected to receive RF signals and the remote communicates with the hub over BT, which doesn't have the range of WiFi, but that's a difficult thing to stuff into such a small package along with the rest of the innards. While it's true that smart phones can do a lot, there are reasons for using BT vs WiFi but I'm not one of the designers.
Some latency issues have to do with the programming, especially if someone adds custom delays (or doesn't when they're needed), extra steps for input switching, etc. Have you used the troubleshooting steps to fix any of the commands or activities? I would suggest that, if you want to get it to work. Some (many) devices need a fairly long delay between power on and any other command and that's not the fault of the remote manufacturer, it's the nature of the controller in the piece of the equipment. Before I knew about the need for long delays with some brands, I had some terrible problems getting systems to do what I wanted, then I was told that Denon AVRs needed more than five seconds between Power On and any input command. Denon didn't tell me, it was another integrator and I had attended several Denon training sessions, too.
.