1 year later, all seems to be well with the Google voice-control of the X1 for simple “turn on (X1 Activity)” commands. It’s been working regularly for me. To summarize- How to Link SofaBaton to Google Home: Steps: 
 Open Google Home app
 Click + in upper left Click “Set up device”
 Select “Works with Google” 
Click search icon upper right 
 Enter Sofa 
 Select Sofabaton This should launch an AWS authenticate web page. The AWS page will show the Sofabaton logo and login fields, into which you need to enter your SofaBaton X1 account login info. This will link Google Home to the X1 Hub, and will populate Google Home’s Linked fields with a Sofbaton service. To use an Activity you say "Hey Google, turn on (activity name)" using the name of the X1 Activity you defined in the Sofabaton app. The Activity will activate and fire up the device(s), and the remote will switch to the selected Activity controls. No devices or Activity names are displayed in Google Home. You will need to remember your SofaBaton Activity or scene routine as suggested by Ward000 above. I imagine you could create an X1 Activity for each function you might subsequently want (“mute TV”, “increase volume”, “lock and load”, …) but I haven’t tried, it’s just easier to use the remote. So I think voice control of X1 is very limited. But maybe someday SofaBaton can implement a subset for the SofaBaton Nest Hub service or Alexa skill set that would provide AI-based device-command-level voice access for each X1 Activity. That would make good on their implied voice control feature by Google or Alexa assistants.

I have responded by email. In the meantime I have sidestepped the issue of poor first-key-click response for my Samsung QN90A TV while using v15 firmware by downgrading to v13.

After installing the v15 firmware, does anyone else see the return of the Kickstarter-original no-response-to-first-key-click problem? After I updated the X1 hub firmware from v14 to v15, various keys now do not command my Samsung QN85QN90A TV on the first key click: Home, Mute, Return, Volume?, Various others seem to be irregularly responding. I’ve emailed SofaBaton about this. It’s REALLY annoying to have this old problem rear its ugly head again!

@p3t3r, you should be able to create your Activity in the SofaBaton app by listing all the Devices you want involved. Follow the steps in the paper manual or several on youtube (https://youtu.be/HeUpVimv6_8 seems ok). Or just play around as it is fairly straightforward. You asked for step by step instructions/examples. You’ll probably have to make do with general procedures. If you email Sofabaton@outlook.com, they’ll likely send you a video link as an example. Or service@sofabaton.com has also been very responsive. I’m pretty disappointed that SofaBaton isn’t maintaining this BBS and keeping the Manual, Changelog, etc. available and updated, Their answer from a couple days ago is relevant if you power on/off devices separately from Activity control. There’s no feedback about the power status from a device to the X1, the X1 only remembers the last Activity steps, ie the last power switching command. So if you manually turn on or off a device separately from the X1 Activity, the remote will certainly get mixed up when running an Activity. You also need to pay attention to whether you have activated CEC during your setup of TV and Nvidia etc, receiver and subs. From you note, it sounds like you have CEC communication enabled in all or some of your devices. This may complicate your programming. Turn them off to simplify. I have my CEC enabled, because it works for what I want (and let’s me control several devices just using my X1’s Samsung TV commands). But if you’re just starting out programming the remote, you’ll want to keep it simple.

The periodic flashing is characteristic of Hub v14. Resolved in the new v15 firmware, see v15 change log at https://bbs.sofabaton.com/post/1402

Not sure if I’m following you re Timeout, but anyway it’s best to do all Activities building and Editing in the SofaBaton app by clicking the Pencil and Paper icon in the app’s upper right corner. Be sure to click Save when it’s available after you’re done, before exiting the app.

To avoid loosing your place if the remote display times out, one thing you could try is setting the LCD Timeout to a longer time. Go to the topmost menu <- <- and choose Set. Under Sync is LCD Sleep. Click there and choose your Timeout.

For the X1 system, the OFF button on the upper left of the remote is only for your programmed Activity, not for Devices. Activities are a programmed sequence of operations for selected Devices. Once you set up an Activity, the OFF button will run the Shutdown Settings that are set for that Activity. If you happen to be just using a Device not an Activity, and press the OFF button, the remote display will change to the Activity screen but no command to shut off the Device is issued. This is a common source of irritation for new users, but ya get used to it. If you aren’t yet up to crafting an Activity, the recommendation is to Sort the Key functions for your Device so that the Power functions are up towards the top of the list. Then when you roller click the Device name on the remote, the Power command is conveniently displayed. Enjoy and good luck!

My Denon control got messed up too, but I just used the app to (re)Assign the X1 remote’s keys, Took me a couple minutes. Weirdly the WiFi on the Denon got shut down too. I had to pull out the manual and go through some rigamarole of holding down the AVR power button to reset, then hold down its two leftmost buttons, then wait overnight (geeesh) to get the AVR WiFi back. Gotta be coincidental, but weird. Anyway I’m still pretty satisfied with the X1, except SofaBaton keeps changing things and updating/busting their database. Which is par for the course, Harmony was rough around the edges for quite a while too. So I’m hanging in there, exercising patience while they fix it up.

I occasionally get the disconnect bug (after updating to v9, no issues previously), seemingly after charging sessions. Most always, I can resolve it by going to the remote's Set menu and clicking Restart. I'm assuming this restarts the remote, because the display blanks for a couple seconds. No problems with key press execution after restarting. I can't remember when I last had to toggle power to my hub.