Same thing is happening to me. If you set your Logitech G HUB to a persistent profile (I did default desktop) I believe that fixes the problem for the most part.

also, in my case, while I got the GHub lighting with Aurora running, GHub still says the lighting is controlled by Aurora and Aurora shows the lighting that should be on the keyboard in realtime.

I have the same issue. My PC wakes up from sleep and my keyboard is showing the GHub profile (I have selected the default profile, a solid light blue across the keyboard). I have to close Aurora, which doesn't close it properly, so I have to kill the Aurora.exe process from the Task Manager. Starting Aurora again puts it in the Aurora profile.

I also experience the Logitech row say "Disconnected" in the device manager, with the start button doing nothing.

Same thing is happening to me. If you set your Logitech G HUB to a persistent profile (I did default desktop) I believe that fixes the problem for the most part.

I have my GHUB set to a persistent default profile and it doesn't fix anything.

Same thing is happening to me. If you set your Logitech G HUB to a persistent profile (I did default desktop) I believe that fixes the problem for the most part.

I use GHUB macros heavily, so a persistent profile won't work for me.
I also tried the Override DLL option, but it didn't made a difference.
In Patch Notes for GHUB update 2020.02, it says

Fixed an issue with the LED SDK

So the problem is probably caused by the new GHUB update.

Downgrading GHUB will probably fix this, however I can't find a way to downgrade GHUB. Even if I download an installer for an older version, it just installs the latest version. (Installer doesn't work without an active internet connection)
Has anyone found a solution?

I've updated my g hub to the latest version and added a few profiles for applications (I usually use persistent desktop).

It is working perfectly. I don't know if I'm not replicating your setup properly but I can't replicate this issue.

Same thing is happening to me. If you set your Logitech G HUB to a persistent profile (I did default desktop) I believe that fixes the problem for the most part.

Found a solution for myself.
I tried to make JUST the lighting for my desktop profile persistent (NOT the whole profile). It didn't work. Then I created a brand new profile (with every color the default cyan) and made that lighting persistent (again, NOT the whole profile) and it seems to be fixed. Lighting is controlled by Aurora and GHUB macros work as they should.
EDIT: At the startup, Aurora still shows Logitech devices as Disconnected. Restarting Aurora fixes that. (so this is more of a temporary solution)

The startup issue can be fixed by adding a delay to aurora's startup task. You can do so in the general settings

trxraptor's solution is the only thing that worked for me. Creating a new Desktop profile in G HUB and making it's lightning persistent works to keep G Hub from taking over Aurora's integration when you switch between apps that have different profiles in G Hub.

Here's pre-fix G HUB profile that exhibits the problem. Switching between of the apps there breaks Aurora.

https://drive.google.com/open?id=1AJ1XoUDlHvKSZquqQKrSVnEzjsh0z4Mk

Then I created a brand new profile (with every color the default cyan) and made that lighting persistent

unfortunatly this is no solution for me. Also setting up a complete permanent profile only works for a certain amount of time. So far I couldn't find out when it was stopping, because I was playing...

I've experimented some more. It seems that as long as the Lighting profile (just the lighting) that is currently active on GHUB is in no way edited, Aurora seems to work fine. Settings other than Lighting doesn't seem to have an effect on Aurora.
Edit: Grammer

I don't know what did change, but since today the permanent lighting solution is partially working.

Text I was planning to write:

If the Desktop profile in G Hub is active, Aurora works fine. It also works, if the Aurora profile is switched. But once another G Hub profile is activated, the Standard G Hub lighting is active. A plus is that Aurora doesn't crash permanently. So as soon as the G Hub Desktop profile activates all lighting is working again.

But after some more testing:

The more I test the weirder and better it gets. I tried to set up several G Hub profiles as permanent lighting (all with standard Cyan). With some profiles Aurora crashed like instantly, with some only some Games have the right lighting and sometimes everything is working fine. Also I can't really see a pattern, because testing specific profiles twice gives different results...
But overall I can say, the more I test, the better it gets. Right now I use the Standard Desktop profile as permanent lighting and everything is working fine. This morning this profile had the behavior described above ("Text I was planning to write"). I won't change anything right now and observe, if it is working from now on.

So I'm running beta v0.7.2 with GHUB Version: 2020.2.35921 and Aurora doesn't work at all. It can't install the wrapper because it's trying to install the SDK into the logitech gaming software folder which obviously doesn't exist because it was replaced by G-HUB.

Aurora Wrapper Patch for Logitech could not be applied.

Exception: Could not find a part of the path 'C:\Program Files\Logitech Gaming Software\SDK\LED\x86\LogitechLed.dll'.

I can't seem to get the plugin to start when going through settings. It's always off and clicking start doesn't work. Even going into the advanced settings and switching it to "GHUB" doesn't seem to do anything.

I had similar issue where only my G910 keyboard would not load game profiles but was able to get it working fairly consistent by making sure I did not use the desktop lighting effects. The issue seemed to be that it did not like switching from that profile to other profiles. I also run as administrator which fixed the issue with it not initializing. One other weird thing that would occur is it didn't always work correctly when it started up with windows automatically so I made sure to not enable it and just it when I want to use it.

@Pentazer , the wrapper patch does not affect aurora's ability to control lighting on logitech hardware.
The purpose of that feature is capturing games that target Logitech devices, redirecting the lighting information into aurora.

As for g hub not working, try the usual troubleshootingn steps:

• Close G Hub and aurora completely.
• Open G Hub, wait for it to fully start up.
• Open Aurora. It should now connect properly.
• If the issue still persists, upload a log please.

Note: If this works, but breaks when rebooting, add a 15 second delay to aurora's startup task. You can do so in general settings.

For the persistent profile issue, I'm not sure what logitech intended with these "fixes". Thanks for the information you've gathered. Once we fully understand what causes this and how to fix it, I can add a wiki page with instructions on how to setup G Hub correctly.

@Pentazer , the wrapper patch does not affect aurora's ability to control lighting on logitech hardware.
The purpose of that feature is capturing games that target Logitech devices, redirecting the lighting information into aurora.

As for g hub not working, try the usual troubleshootingn steps:

• Close G Hub and aurora completely.
• Open G Hub, wait for it to fully start up.
• Open Aurora. It should now connect properly.
• If the issue still persists, upload a log please.

Note: If this works, but breaks when rebooting, add a 15 second delay to aurora's startup task. You can do so in general settings.

For the persistent profile issue, I'm not sure what logitech intended with these "fixes". Thanks for the information you've gathered. Once we fully understand what causes this and how to fix it, I can add a wiki page with instructions on how to setup G Hub correctly.

This worked, thank you! Starting GHub first, waiting a few seconds and then starting Aurora fixes the problem.

I won't change anything right now and observe, if it is working from now on.

So now after not changing anything for 5 days everything still works. It's fixed for me. Hopefully it will never come back and everyone else can solve their issues too. Thanks for all the tips, I never want to miss Aurora again.

I have found something that can be related to this issue.
When connecting a new device (for example a Logitech G933) GHub overrides aurora integration. Restarting the Device Manager on Aurora or the integration on GHub fixes the problem, but it will happen again the next time a device connection appears.

One reason for this is the fact, that the LogiLEDWrapper dll is not returning the actual status of the operation but the init status. Once the init is done there is no option to check if a device is still accessible.

I created a testpatch, that checks the status of a keyboard.
status_test.zip

Has a bug been filed with logitech regarding these G HUB issues?

I looked into this the last days, and I think there are actually two issues here.

First is that Aurora doesn't check the connection status to GHub or the devices once init is done. I did a quick hack in the patch I attached to my previous post. I am not satisfied with this solution so I only made a patch and no PR.

The second issue is, if GHub switches from the default profile to any other, it seems GHub is rejecting data coming from the SDK. I wasn't able to overwrite the the GHub settings once it was not in the default profile.