-TaskName "VPN-IPInterface-Metric-Down-Weight" `
    -Description "Cisco VPN IP interface is given a low weight so it's routing rules do not override the routing rules of internal networks." `
    -Principal $principle `
    -Settings $settings `
    -TaskPath '\Cisco-VPN-mitigation'

@trreeves

But, does WSL2 use a consistent address range for everyone, all the time? My WSL adapter currently has the range <IP_ADDRESS>/28, which is different to @StevenAndradeSonos, and I imagine could be different across the 200 engineers in my organisation.

I forgot to mention on my previous post, that Anyconnect should have `Allow Local (LAN) access when using VPN (if configured) enabled on the client. This allows it to see what your local networks on your computer are and exclude that from the tunnel. It then should not matter what each engineer WSL2 network is setup.

Anyconnect should have `Allow Local (LAN) access when using VPN (if configured) enabled on the client. This allows it to see what your local networks on your computer are and exclude that from the tunnel.

Chiming in to say we don't use Cisco, but even if we did the suggested policy above is unlikely to be accepted by our security department.

One interesting thing: Docker container instances have full networking when Pulse Secure VPN is connected, they don't suffer from this issue.

@kingsumos Docker Desktop use Vpnkit (https://github.com/moby/vpnkit):

VPNKit, part of HyperKit attempts to work nicely with VPN software by intercepting the VM traffic at the Ethernet level, parsing and understanding protocols like NTP, DNS, UDP, TCP and doing the "right thing" with respect to the host's VPN configuration.

Using https://github.com/sakai135/wsl-vpnkit worked for me with Pulse Secure VPN

Thanks for the suggestion. I have tested wsl-vpnkit, here it works partially: local network and Internet access are ok, but I can't reach any host inside my VPN network (i.e. ping fails, ssh login fails). Looks like all traffic is routed outside the VPN, not sure - further investigation is needed... Maybe I need to setup some routing for hosts inside VPN. Any clues?

@kingsumos when you run nslookup in WSL 2 with wsl-vpnkit, is it using <IP_ADDRESS> for the DNS server?
$ nslookup example.internal

Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Non-authoritative answer:
Name:   example.internal
Address: x.x.x.x

Hi @sakai135
Yes, it is using - in fact domain names are resolved correctly.
Interesting thing: when I try to access some host inside my VPN the connection fails immediately (a connection to some internet public IP takes a while). A tcpdump shows a TCP RST, it wasn't generated by the remote server but locally I believe (since it's too fast and the round trip to my remote server is about 300ms).

One interesting thing: Docker container instances have full networking when Pulse Secure VPN is connected, they don't suffer from this issue.

@kingsumos Docker Desktop use Vpnkit (https://github.com/moby/vpnkit):

VPNKit, part of HyperKit attempts to work nicely with VPN software by intercepting the VM traffic at the Ethernet level, parsing and understanding protocols like NTP, DNS, UDP, TCP and doing the "right thing" with respect to the host's VPN configuration.

Using https://github.com/sakai135/wsl-vpnkit worked for me with Pulse Secure VPN

I tested @sakai135 solution and it seems to work from a network connectivity standpoint but 2-3 times during the test the whole computer went unstable and only way to restart was to unplug/plugin the power. Then I removed vpnkit and no stability issues since then.

For those interested, I found a solution on my end to what 'appears' to be the same issue.  My results seem to be consistent that if you start WSL before your VPN establishes it's connection on startup, it will fail, however if you allow the VPN to complete it's connection first there is no issue afterwards.
What was really causing issues for me to identify this was that docker-desktop was auto starting at login with WSL connections (thus starting WSL in the background) making it a race condition on whether or not it works,  either docker-desktop would launch first and WSL would have no connection, or the VPN would connect first and it would work fine.  Restarting your machine gave you a 50/50 on which one wins.
I turned off autostart in docker and start it manually after my VPN is established and it everything works.
Using Cisco AnyConnect

For those interested, I found a solution on my end to what 'appears' to be the same issue. My results seem to be consistent that if you start WSL before your VPN establishes it's connection on startup, it will fail, however if you allow the VPN to complete it's connection first there is no issue afterwards.
What was really causing issues for me to identify this was that docker-desktop was auto starting at login with WSL connections (thus starting WSL in the background) making it a race condition on whether or not it works, either docker-desktop would launch first and WSL would have no connection, or the VPN would connect first and it would work fine. Restarting your machine gave you a 50/50 on which one wins.
I turned off autostart in docker and start it manually after my VPN is established and it everything works.
Using Cisco AnyConnect

When I had this kind of issue, I disabled the service autostart, created a small .bat file that could start the problematic process and scheduled it to run 1 minute after the session is open, it could be improved and converted to a powershell script that pre-check that the vpn connexion is established prior to start for example.

This is not what i'm observing with Cisco AnyConnect.  Even if i connect it first, and then open my WSL session via shell and try to ping <IP_ADDRESS>, it fails.
I have a "fix_wsl" powershell script that I run which usually fixes it, but not always.  Sometimes i'm forced to disconnect VPN, close all WSL, and do the whole sequence over, again using 'fix_wsl'.
The entire dance is beyond annoying and frustrating 🙁

From: absynth76 @.>
Sent: Wednesday, May 26, 2021 4:10 AM
To: microsoft/WSL @.>
Cc: luvwagn @.>; Mention @.>
Subject: Re: [microsoft/WSL] WSL2 , problem with network connection when VPN used (PulseSecure) (#5068)
For those interested, I found a solution on my end to what 'appears' to be the same issue. My results seem to be consistent that if you start WSL before your VPN establishes it's connection on startup, it will fail, however if you allow the VPN to complete it's connection first there is no issue afterwards.
What was really causing issues for me to identify this was that docker-desktop was auto starting at login with WSL connections (thus starting WSL in the background) making it a race condition on whether or not it works, either docker-desktop would launch first and WSL would have no connection, or the VPN would connect first and it would work fine. Restarting your machine gave you a 50/50 on which one wins.
I turned off autostart in docker and start it manually after my VPN is established and it everything works.
Using Cisco AnyConnect
When I had this kind of issue, I disabled the service autostart, created a small .bat file that could start the problematic process and scheduled it to run 1 minute after the session is open, it could be improved and converted to a powershell script that pre-check that the vpn connexion is established prior to start for example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FWSL%2Fissues%2F5068%23issuecomment-848605526&data=04|01||e73edeadcfa64c8d53b808d9202614b4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637576170185054909|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=McYVrqMt205U4YhnB9X2e2rxAyv2a88uU5bJQ9a5JJY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP2ELBURXMEKFJM367HTUGTTPS3HTANCNFSM4MFJ2B6Q&data=04|01||e73edeadcfa64c8d53b808d9202614b4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637576170185054909|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=BGE65ir3WZmtipgCOt6wC1UdBCiy%2Bfp7uUVDds0LQAA%3D&reserved=0.

Can you, please, share the script with me?
I have the same issue and none of the approaches described earlier worked
for my setup with cisco anyconnect.
Thanks
On Wed, May 26, 2021 at 9:32 AM luvwagn @.***> wrote:

This is not what i'm observing with Cisco AnyConnect. Even if i connect it
first, and then open my WSL session via shell and try to ping <IP_ADDRESS>, it
fails.
I have a "fix_wsl" powershell script that I run which usually fixes it,
but not always. Sometimes i'm forced to disconnect VPN, close all WSL, and
do the whole sequence over, again using 'fix_wsl'.
The entire dance is beyond annoying and frustrating 🙁
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/5068#issuecomment-848773115, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFARBXGALELX3ESOJQEMQPTTPT2AXANCNFSM4MFJ2B6Q
.

See if this works?  I'm sure some variation of this has been reported before...
#!/bin/bash
cat <<'EOPS' > /mnt/c/Windows/Temp/fix_wsl_routing.ps1
Self-elevate the script if required
if (-Not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator')) {
if ([int](Get-CimInstance -Class Win32_OperatingSystem | Select-Object -ExpandProperty BuildNumber) -ge 6000) {
$CommandLine = "-File "" + $MyInvocation.MyCommand.Path + "" " + $MyInvocation.UnboundArguments
Start-Process -FilePath PowerShell.exe -Verb Runas -ArgumentList $CommandLine
Exit
}
}
$vpnadapter = Get-NetAdapter | ? { $_.InterfaceDescription -match "Cisco AnyConnect*" }
$wsl2Subnet = wsl -- ip addr show eth0 | grep -oP 'inet \S* br' | cut -d' ' -f2 | ip route show | grep -oP '"(\d{1,3}\.){3}\d{1,3}\/\d{1,2}"'
$wsl2Routes = Get-NetRoute | ? { $.DestinationPrefix -eq $wsl2Subnet -and $.ifIndex -eq $vpnAdapter.ifIndex }
$wsl2routes | Set-NetRoute -RouteMetric 6000
EOPS
powershell.exe -File "c:\Windows\Temp\fix_wsl_routing.ps1"
DNS_SERVERS=$(bash -c "powershell.exe -NonInteractive -NoProfile "(Get-NetAdapter -InterfaceDescription 'Cisco AnyConnect*' | Get-DnsClientServerAddress -Family IPv4).ServerAddresses[0]"")
cat <<EOT | sudo tee /etc/resolv.conf
nameserver $(echo "$DNS_SERVERS" | tr -d '[:space:]')
EOT

From: Andre J. @.>
Sent: Wednesday, May 26, 2021 10:42 AM
To: microsoft/WSL @.>
Cc: luvwagn @.>; Mention @.>
Subject: Re: [microsoft/WSL] WSL2 , problem with network connection when VPN used (PulseSecure) (#5068)
Can you, please, share the script with me?
I have the same issue and none of the approaches described earlier worked
for my setup with cisco anyconnect.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FWSL%2Fissues%2F5068%23issuecomment-848883650&data=04|01||2801f59db6d446ed5e8c08d9205ce97f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637576405686996871|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9bYaXPqzdpG%2Bf64yJS%2FNaqui9w7JA5WHMy8C2bGSKmU%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP2ELBRIL6KI5HOGAFUBR53TPUJHNANCNFSM4MFJ2B6Q&data=04|01||2801f59db6d446ed5e8c08d9205ce97f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637576405686996871|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=7R%2F288jAQimG%2B1wOvsi2%2BnazF%2BYow7lag0lnEe2ahpw%3D&reserved=0.

Still no solution, but more info. Following up on xpac1985's excellent comment, I'm guessing that the reason why starting WSL after connecting VPN can work is because it establishes a new route that the VPN doesn't override. Of course this relies on the WSL route not being there at the time you connected VPN - for me, even terminating the WSL instance didn't remove the route, and I'm not sure anything short of stopping the vEthernet (WSL) interface would. But that does suggest a solution for folks with admin privileges:

Stop the vEthernet (WSL) net adapter
Connect to VPN
Start the vEthernet (WSL) net adapter
Maybe restart the WSL instance
Completely untested, since I can't run my Windows machine with admin privileges anyway.

But with admin privilege, there should be some way to raise the metric value of the specific VPN-created route that's overriding the WSL subnet's route, rather than changing all VPN routes. route print shows different metric values for each route after all - metric isn't tied to an interface. If push comes to shove, you can even delete that specific VPN-created route.
The route can be identified by first seeing the IP/subnet of the vEthernet (WSL) interface, via ipconfig. For me it's <IP_ADDRESS>. Then, there should be a route in route print for that subnet going to the <IP_ADDRESS> interface. Right below it is a lower metric route for the same subnet going to your VPN's interface.

Changing route config isn't an option when using Pulse Secure, it detects any changes then the VPN is restarted. Other suggestions required admin privileges, this is an issue as well. The amount of work required to solve the issue doesn't worth it.
Remember, this topic is for Pulse Secure and the only option that really works is using wsl-vpnkit from https://github.com/sakai135/wsl-vpnkit
(anyway... it should work for other VPN flavors as well, install it and have fun)
Here I'm starting wsl-vpnkit this way:
sudo VPNKIT_PATH='/mnt/c/Program Files/Docker/Docker/resources/vpn.exe' ./wsl-vpnkit

For those interested, I found a solution on my end to what 'appears' to be the same issue. My results seem to be consistent that if you start WSL before your VPN establishes it's connection on startup, it will fail, however if you allow the VPN to complete it's connection first there is no issue afterwards.
What was really causing issues for me to identify this was that docker-desktop was auto starting at login with WSL connections (thus starting WSL in the background) making it a race condition on whether or not it works, either docker-desktop would launch first and WSL would have no connection, or the VPN would connect first and it would work fine. Restarting your machine gave you a 50/50 on which one wins.
I turned off autostart in docker and start it manually after my VPN is established and it everything works.
Using Cisco AnyConnect

Yes, that work for me as well - on a fresh booted computer not when using sleep/hibernate since WSL is started. Tried to shutdown them before without no success.
However Docker Desktop with WSL2 backend works after hibernate so they have solved it and @sakai135 tries to mimic that (as I understand) but doesn't work problem-free (see my previous comment)

I have been testing @sakai135 solution for a few days without any issues so far. I have created a couple of installation scripts based on that solution to deploy to our corporate machines. https://github.com/AmmarRahman/wsl-vpn

Going to post this in a few of the longer running threads. Long story short, the AnyConnect fix for this issue is available. The fix requires two pieces, an update to the client of version 4.10.01075 or later and a new custom attribute in the ASDM. Links to info below:
Release Notes
Admin Document Troubleshooting Section that describes the custom attribute that needs to be set up by the VPN adminstrator.

So in theory, for those of us not permitted to configure our VPN client, this should be a friendly email to your IT department to update the configuration. Here's the relevant docs for Cisco AnyConnect I believe:
https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/70847-local-lan-pix-asa.html
But, does WSL2 use a consistent address range for everyone, all the time? My WSL adapter currently has the range <IP_ADDRESS>/28, which is different to @StevenAndradeSonos, and I imagine could be different across the 200 engineers in my organisation.
Is there a set of address ranges that WSL2 cycles through when it chooses? i.e. is there a sensible predictable subset of the non-routable address space that could be configured for local network access across a population of WSL2 installs?
A low-tech hack I've settled on for now is to set up a Windows scheduled task that get's triggered every time the Cisco AnyConnect client adjusts the route table. It can probably be adapted for other VPN clients if they generate the right events.
Run the following in an elevated Powershell session, then observe the metric values from route PRINT as you disconnect/reconnect to your VPN):
$script = "Write-Host 'Down-weighting Cisco VPN Client IP Interface...'; Get-NetAdapter | Where-Object {`$_.InterfaceDescription -Match 'Cisco AnyConnect'} | Set-NetIPInterface -InterfaceMetric 6000; Write-Host 'Done!'"

$action = New-ScheduledTaskAction `
    -Execute 'Powershell.exe' `
    -Argument ('-c {0}' -f $script)

$eventPath = "Cisco AnyConnect Secure Mobility Client"
$eventSource = "acvpnagent"
$eventId = 2057

$CIMTriggerClass = Get-CimClass `
    -ClassName MSFT_TaskEventTrigger `
    -Namespace Root/Microsoft/Windows/TaskScheduler:MSFT_TaskEventTrigger
$Trigger = New-CimInstance `
    -CimClass $CIMTriggerClass `
    -ClientOnly
$Trigger.Subscription =
@"
<QueryList>
    <Query Id="0" Path="${eventPath}">
        <Select Path="${eventPath}">*[System[Provider[@Name='${eventSource}'] and EventID=${eventId}]]</Select>
    </Query>
</QueryList>
"@
$Trigger.Enabled = $True

$principle = New-ScheduledTaskPrincipal `
    -UserID "NT AUTHORITY\SYSTEM" `
    -LogonType ServiceAccount `
    -RunLevel Highest

$settings = New-ScheduledTaskSettingsSet `
    -AllowStartIfOnBatteries `
    -DontStopIfGoingOnBatteries `
    -MultipleInstances Queue `
    -Priority 0

Register-ScheduledTask `
    -Action $action `
    -Trigger $trigger `
    -TaskName "VPN-IPInterface-Metric-Down-Weight" `
    -Description "Cisco VPN IP interface is given a low weight so it's routing rules do not override the routing rules of internal networks." `
    -Principal $principle `
    -Settings $settings `
    -TaskPath '\Cisco-VPN-mitigation'

After several other attempts, this workaround worked like a charm for me.
My company probably suddenly decided to change allowed range of IPs, leading to WSL not able to reach the network...
I'll maybe try to reach my company's IT to inform them about those changes.
Thanks anyway highlighting it.

@sakai135's solution is working for me. Thanks :)

I'm having the same issue. Switching back to WSL1 is the quickest solution for me.

I'm having the same issue with cisco anyconnect. I change app to openconnect with same settings and now network in wsl2 works!

@Hyperspaceru Below a message I just got from our university IT. After upgrading to the latest version of Cisco Anyconnect and changing settings to "Allow local (LAN)" network on WSL2 is working again! No other work arounds needed.

FYI in addition to checking on that route addition- the version on blink doers suport this feature;AnyConnect 4.10.01075 New Features
This is a maintenance release that includes the following features and support updates, and that resolves the defects described in AnyConnect 4.10.01075:

Added support for interoperability with VM-based subsystems (CSCvw81982)—Windows Subsystem for Linux 2 (WSL2) had connectivity issues with AnyConnect VPN active on a Windows 10 host. We addressed this issue by enhancing support for Local LAN wildcard split exclude tunneling, specifically by allowing the limiting of the Local LAN split exclude to virtual adapter subnets.

Had the same issue but what worked for me was lowering the eth0 MTU:
sudo ip link set dev eth0 mtu 1024
Please note that it needs to be executed after each restart.

I have exactly same issue and solved it by

uninstall anyconnect
download and reinstall anyconnect from Windows Store

No issue so far

Had same issue. Switching over to the Windows Store version of AnyConnect worked for me.
Note, the Windows Store version of the app asks you to use the built-in Windows 10 VPN settings to set up the connection. Be sure to change the "VPN provider" dropdown to the AnyConnect option.
Looks like this:

I have exactly same issue and solved it by

uninstall anyconnect
download and reinstall anyconnect from Windows Store

No issue so far

Had same issue today with WSL2 and Ubuntu 20.04.
Switching over to the Windows Store version of AnyConnect worked for me.
Note, the Windows Store version of the app asks you to use the built-in Windows 10 VPN settings to set up the connection. Be sure to change the "VPN provider" dropdown to the AnyConnect option.
Looks like this:

@Aoa77 same issue, but uwp verison of anyconnect cannot set username and password, always failed with connection

Got this working with Pulse VPN, by doing following changes.

Change Pulse Vpn profile to : "tunnel routes with local subnet access". This typically needs to be done by whomever is maintaining the pulse VPN setup.
Set proper DNS server in /etc/resolv.conf
Set proxy settings in OS level (if proxy in use).

After more investigation on my side the problem is due to Trend Vulnerability Protection Agent.
The only way to solve is to uninstall Trend Vulnerability Protection Agent.

All the mentioned solutions in this and other similar threads didnt work for me.
As a work around used docker containers with wsl2 backend: https://docs.docker.com/docker-for-windows/wsl/
With this I was able to access the internal sites with VPN on, but, had to disable the VPN to access other public sites.
Cisco Anyconnect version: 4.10.01075

I'm also experiencing the same issue

So, as per July 09th 2021 - there's no solution for this - except running the VPN from inside WSL itself? (As per @SeePatPlay information here you have to run a Docker container with WSL2 backend
This issue happens with any kind of VPN client, it seems, from Pulse Secure, to Cisco Anyconnect and OpenVPN.

same issue, major pain for me

5+ years following WSL on AnyConnect with split tunnel - and still no joy

Hello there, i haved same issue, and i tried a lot of "fixes" but for me the solution for this problem was correct order of launching programs. I have wsl2 (ubuntu-20.04) and any connect vpn, and if i want internet connection works corretcly with vpn, i need to start previously wsl2, wait while it launchs (check that internet works, for example using "sudo apt update"), only than i turn on any connect vpn. Connection still work and i can connect to my corp working place which available only with vpn.
I hope i helped someone and sry for my English)

easy bro ! just type the command "nano /etc/resolv.conf" .Then delete everything you see and add a line "nameserver"  followed by your router's ip .it works

All the mentioned solutions in this and other similar threads didnt work for me.
As a work around used docker containers with wsl2 backend: https://docs.docker.com/docker-for-windows/wsl/
With this I was able to access the internal sites with VPN on, but, had to disable the VPN to access other public sites.
Cisco Anyconnect version: 4.10.01075

Can you please explain more how did you solve your problem ?

I happened to pick up on this thread as some of users who upgraded to Windows 11 had the same issues with using WSL2 to connect to our internal servers. Curiously, out of the two VPN providers we use viz. OpenVPN and Cisco, we had trouble only with Cisco. The OpenVPN was configured as a split-tunnel whereas the Cisco was configured to route the entire traffic through the VPN.
In spite of trying out multiple solutions from here and from other threads, I was nowhere close to solving it. However, once we configured our Cisco VPN to use split-tunneling instead of routing the entire traffic through the VPN, we were able to use WSL2 (Ubuntu 20.04) with the VPN on.
I realize this is not an ideal solution as this only applies to use cases where the VPN is configured to use split-tunneling. Nevertheless, this should at least provide a pointer for folks searching for a solution.

I'm using Windows 10 Pro, version 21H1, compilation 19043.1110, Windows Feature Experience Pack 120.2212.3530.0 and Ubuntu 20.04 on WSL2. When I connect to my corporate VPN using Check Point Mobile client, Ubuntu on WSL2 can't access any machine on VPN. Access to my home network and Internet remains okay, but I can't reach any machine on VPN. Does anybody knows how to fix it?

Update for me, it appears somehow AnyConnect VPN + Debian WSL2 is working without any additional configuration. Our company recently updated the Cisco ASA's and put out the the latest AnyConnect VPN client from Cisco, but I'm not sure if that's what fixed it.
Microsoft Windows [Version 10.0.19043.1110]
Cisco AnyConnect Secure Mobility Client Version 4.10.00093 (Full Tunneling)

Turning on this setting worked for me for Cisco AnyConnnect

Use openconnect can solve this problem!!!!!!!!

I have exactly same issue and solved it by

uninstall anyconnect
download and reinstall anyconnect from Windows Store

No issue so far

Had same issue today with WSL2 and Ubuntu 20.04.
Switching over to the Windows Store version of AnyConnect worked for me.
Note, the Windows Store version of the app asks you to use the built-in Windows 10 VPN settings to set up the connection. Be sure to change the "VPN provider" dropdown to the AnyConnect option.
Looks like this:

This actually worked for me. Pay attention to the settings and play around with username password formats

I have exactly same issue and solved it by

uninstall anyconnect
download and reinstall anyconnect from Windows Store

No issue so far

Had same issue today with WSL2 and Ubuntu 20.04.
Switching over to the Windows Store version of AnyConnect worked for me.
Note, the Windows Store version of the app asks you to use the built-in Windows 10 VPN settings to set up the connection. Be sure to change the "VPN provider" dropdown to the AnyConnect option.
Looks like this:

This actually worked for me. Pay attention to the settings and play around with username password formats

I also had success with this.

after a few hours of painful in my a$$, I come to an solution to deal with this, since I need the vpn to build my image, but the vpnkit never ever goes with the docker proxy setting(nor win10 system proxy). Then finally, I figured out to use Netch and add the damn vpnkit.exe to the list, then I'm happy now.
Sorry for the wordings, but I went crazy for a few hours to figure out what's the problem and why the build never went through the proxy setting...
Hope this helps others~~~
and thanks for the docker team great work, hope this will be fixed soon.

https://github.com/AmmarRahman/wsl-vpn
This solution worked for me. Thanks

Update for me, it appears somehow AnyConnect VPN + Debian WSL2 is working without any additional configuration. Our company recently updated the Cisco ASA's and put out the the latest AnyConnect VPN client from Cisco, but I'm not sure if that's what fixed it.
Microsoft Windows [Version 10.0.19043.1110]
Cisco AnyConnect Secure Mobility Client Version 4.10.00093 (Full Tunneling)

Did it work for you?

I have been testing @sakai135 solution for a few days without any issues so far. I have created a couple of installation scripts based on that solution to deploy to our corporate machines. https://github.com/AmmarRahman/wsl-vpn

This solution solved my problem, nice and easy to follow. Thanks for the compilation and also thanks to the acknowledged repos.

This issue have been open for almost 1,5 year and still no fix from Microsoft :(

https://github.com/AmmarRahman/wsl-vpn
This solution worked for me. Thanks

Yes, its working.
Before, I had to revert back to WSL1 because of this issue.


Feature Request: Bypass until the sensor gets closed

Hello all,
It's possible to implement a bypass mode that permit to arm the alarm, but doesn't get ignored if open as soon it gets closed?
In example, I'm ready to leave the home, so I open the door, and as soon I'm moving out I activate the alarm... but, huh, the door is open and so it gets ignored until I rearm it because the bypass option is enabled. If I disable it, for sure the next time I'll try to arm the alarm, the door is open and I cannot arm it.
Possible to implement such feature? Seems not present afaik.
Thanks and great project anyway!
Simon

For motion sensors such feature exist.
The idea is that some motion sensors take 1-2 minutes after seeing movement before they return to inactive state.
So if you try to arm the alarm from within the house, you could immediately trigger the alarm when the exit delay is passed (if exit delay is shorter than this motion sensor delay).
This setting will cause the initial state to be ignored:

If you want to apply this kind of behaviour to a door sensor, you could clear the sensor type field:

This makes all settings show up, rather than only appropriate ones.
I'd say it would work for your use-case, give it a try 👍
I'm hesitant to implement extra functionality for this. In my opinion, the bypass functionality should remain transparent, so should completely eliminate the sensor. Assigning extra rules for this might be confusing for users.

Hello,
Thanks, but removing the device type, this option is not (immediately) shown:

But it's shown only if I do the following:

remove the sensor type, the option is not there
select the "Motion" sensor type, the option is shown and activated by default
remove the sensor type, the option remains.

Sorry for the delay answerring and thanks for the support @nielsfaber  !
Simon

Hello @nielsfaber ,
I was partially wrong. If I remove the sensor type, I can enable the "Use Exit Delay", but the sub-command "Allow open after arming" is grayed out, and I cannt activate it.
So to have both "Use Exit Delay" and "Allow open after arming", I need to:

delete the sensor type
select the Motion sensor type
delete the sensor type

Normal?
Thanks, Simon


Adjustment - Steelheads

Ensuring the data transfer from the Mississauga Steelheads to the Brampton Steelheads.

The Brampton Steelheads are still using team_id = 18


Unresolvable reference reports wrong error

As reported in https://github.com/whitlockjc/json-refs/issues/105, it seems like json-refs is reporting a missing reference appropriately but the error message being set is not as expected, which leads me to believe that there is an underlying bug somewhere.

This is not a json-refs issue.  After further digging, json-refs is returning the following error message: connect ECONNREFUSED <IP_ADDRESS>:8080) -> http://localhost:8080/id.json#/definitions/properties/Config  This means that sway is messing up the error and that means that it is where the jacked up error message reported in json-refs was happening.

This seems to have been resolved when upgrading to the latest json-refs.  My test to reproduce this shows it's working:
[
  {
    "code": "UNRESOLVABLE_REFERENCE",
    "message": "Reference could not be resolved: http://localhost:3000/types.json#/definitions/Missing",
    "path": [
      "paths",
      "/pet",
      "put",
      "parameters",
      "0",
      "schema",
      "$ref"
    ],
    "error": "connect ECONNREFUSED <IP_ADDRESS>:3000"
  }
]


sendmail not working in greenlight docker?

It looks like the sendmail in the greenlight docker container is not working properly. At least it is not able to send confirmation mails. And a tcpdump on the big blue button server shows no smtp traffic.
I tested it with the site.yml playbook and the configuration from this git repository.
In the docker container, when I run sendmail, I received the following message:
bash-4.4# echo "Subject: sendmail test" | sendmail -v<EMAIL_ADDRESS>sendmail: can't connect to remote host (<IP_ADDRESS>): Connection refused

are there sendmail experts who can help here?

Can this issue be closed?

the issue is not resolved, I guess.
but I can deal with the workaround. And for the greenlight docker container, I think this is also the wrong place.

Could solve sending email by installing postfix.
Additional steps to configure postfix in /etc/postfix/main.cnf needed were:

and the docker ip range <IP_ADDRESS>/16 to mynetworks
point to the letsencrypt certificates that are created by the bbb role

hostname must match the fqdn.
Maybe should add postfix on the host and configure it within the role?

Could solve sending email by installing postfix.
Additional steps to configure postfix in /etc/postfix/main.cnf needed were:
* and the docker ip range <IP_ADDRESS>/16 to mynetworks

* point to the letsencrypt certificates that are created by the bbb role

hostname must match the fqdn.
Maybe should add postfix on the host and configure it within the role?

@edlerd would you be able to do this as a PR since you have solved it already once?
Closing the issue for now since this is stale since 21.12.2020


😢😢😢 Emoticons not rendered in pdf

Hi i can see there are emoticons included in my HTML sytnax string but its not displayed in PDF file. any ideas? 😢😢😢 my code:
import * as htmlToPdf from 'html-pdf';

[...]

htmlToPdf.create(html).toStream((err, stream) => {
        if (err !== null) {
          reject(err);
        } else {
          resolve(stream);
        }
      });

html string =
"
fsdfsdfsdf😎😍
"

renders:

Icons are missing

Hi, i've recently switched to using Puppeteer, which renders emojis just fine 😄
I've outlined an upgrade path here: #601


Complete a keygen happy path ceremony in axelar-core using rust-tssd

Current status of rust-tssd is a prototype keygen happy path passing only a minimal test.  Next goal is the title: Complete a keygen happy path ceremony in axelar-core using rust-tssd.
Tasks

[ ] Golang client for rust-tssd.  I currently have a local golang rust-tssd client repo for rust-tssd with a basic test---this repo should be moved into the rust-tssd repo itself.
[ ] Better tests: golang client, rust-tssd, thrush.
[ ] thrush, rust-tssd should never panic---return errors instead.
[ ] Rust-tssd does not yet store keys it generates.  Add a KV store for (pubkey_name, pubkey_data).  Need to search for a good KV store rust library.
[ ] Swap rust-tssd into axelar-core, run a ceremony.  Prerequisite: figure out the deserialization needs of the resulting pubkey in axelar-core.
[ ] Code review?

Hey ggutoski! Do you still have the go-tofnd-client to try out?


fixed assertion

The test was failing locally but not on Travis (probably due to different versions of Node).
I hope it's the correct way to fix it.

Yeah, this looks brilliant! Thanks @FezVrasta!


RGB note shader option in Project.xml

What feature do you want to get added on the base engine?
The post title should explain itself - having a setting in Project.xml to disable the RGB note shader globally when compiling would be nice.
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

I'd rather have a way to disable it globally than have to go through every song and manually disable it.


Inconsistent menu options for formatting

Right click on .dart file and I don't see "Source".
I see "Source" when I right-click on a single HTML file.
I see "Source" when I right-click on the project.

Attachment:
[Screen Shot 2014-03-07 at 9.57.35 AM.png](https://storage.googleapis.com/google-code-attachments/dart/issue-17341/comment-0/Screen Shot 2014-03-07 at 9.57.35 AM.png) (69.42 KB)

This issue has been moved to dart-lang/dart_style#331.


Uninstall doesn't remove path

OS version and name: macOS 10.13.6
Poetry version: latest

Issue
I've installed Poetry using the official
curl -sSL https://raw.githubusercontent.com/sdispater/poetry/master/get-poetry.py | python

I've uninstalled Poetry using the official
python get-poetry.py --uninstall

Poetry said it's removed from PATH.
Actually it's not.
export PATH="$HOME/.poetry/bin:$PATH"

Is still at the end of ~/.bash_profile.

https://github.com/sdispater/poetry/blob/5c86d1dfb6b2c8c8b15c0d9522994ee24907e81e/get-poetry.py#L685-L689
https://github.com/sdispater/poetry/blob/5c86d1dfb6b2c8c8b15c0d9522994ee24907e81e/get-poetry.py#L703-L704

@42B Seems like something is missing 😅

This should now be fixed.


MUPX Feature Discussion - proxy, vhost, force-ssl, nginx and docker

My application is a financial application that touches consumer credit card data mag stripe data and must use Meteor's forcessl.
As well, each new customer gets their own instance of the Meteor application. Considering that it is a mission critical financial application I cannot consider multi-homing multiple clients in a single application or database.  It would just be irresponsible.  I don't care that Square, Intuit Quickbooks POS or other point of sale companies do it.  It isn't right.
That creates another requirement, namely to be able to handle requests with a wildcard SSL certificate thereby complicating things a little bit.
So, mupx is great for deploying and managing multiple instances.  Except that it wasn't supporting force-ssl,
Currently, when deploying with mupx it forces your meteor app to launch on port 80.
Even if you use mupx ssl termination, it only handles 443.
This issue opens up a discussions of how can we implement force-ssl while still using mupx's excellent ssl handling and how we might implement proxying and vhosts and maybe even load balancing.
I have successfully used mupx to deploy nginx on port 80 and 443 for ssl termination and  my meteor app on another port (58080).
I did it through some rough hacking and hard coding because I didn't not want to force a solution on the community.
Rather I think it would be good to get Arunoda and his team as well as the community to steer this project to a suitable solution in order to solve these common set of issues.
So, I cloned the docker containers for MeteorD, Mup Front End Server and Mupx and made manual static changes.
You can see for yourself.
https://registry.hub.docker.com/u/etherpos/meteord/
https://registry.hub.docker.com/u/etherpos/mup-frontend-server/
As well, I cloned mupx and made some static changes just to get this to work.
https://github.com/stephentcannon/meteor-up/tree/mupx
https://github.com/EtherPOS/mup-frontend-server/tree/forcessl
https://github.com/EtherPOS/mup-frontend-server/tree/forcessl
Here is what I did to get it to work in a very static manual manner.

I made some manual changes to mup-frontend-server/lib/nginx.conf
This causes nginx to listen on 80, forces ssl and proxies to 58080 properly while still using mupx to handle ssl certification installation, etc... because it is all dockerized.

   upstream site{
      server backend:58080;
    }

    server {
      listen 80  default_server;
      server_name *.etherpos.com;
      return 302 https://$host$request_uri;
    }

Then I made static changes to mup-frontend-server/run.sh by adding the publish of 80:80 for nginx

docker run -it \
  --volume=/opt/nginx/conf/bundle.pem:/bundle.crt \
  --volume=/opt/nginx/conf/private.key:/private.key \
  --link=meteor:backend \
  --publish=80:80 \
  --publish=443:443 \
  meteorhacks:mup-ssl-server /start.sh

Then I changed the Docker file for MeteorD specifically exposing 58080 instead of how it is defaulted to 80.

FROM debian:wheezy
MAINTAINER EtherPOS, LLC

ENV METEORD_DIR /opt/meteord
COPY scripts $METEORD_DIR

RUN bash $METEORD_DIR/init.sh

EXPOSE 58080
ENTRYPOINT bash $METEORD_DIR/run_app.sh

Then I changed my forcessl mupx as follows.    You can test it by visiting http://base.etherpos.com and you will see that nginx is listening on 80, forcing to 443 and proxying requests to 58080.  Also, it is preventing direct access to 58080 either with or without SSL which is what force-ssl should do.
So, what is the strategy for implementing this?
Strategy 1 - Implement force-ssl only to comply with the Meteor package
Maybe have an environment variable
"env": {
    "FORCESSL": false, // true or false
    "HOST": *.domain.com // used to write the nginx.conf file either wildcard or specific host
    "backendPort": 58080 //already exists in mup in SSL config area...maybe leave, maybe put here?
}

I think with these 3 pieces of information we could at least implement force-ssl where nginx listens on 80, forces to 443 and proxies to the backendPort easily enough.
Strategy 2 - Use mupx and mup.json to configure ports, proxies, etc...
We could have new environment elements.
I am honestly not even sure how we would begin to handle all of these requirements from the mup.json
It starts to get quite complicated when we start thinking about vhosts, proxying, load balancing etc...
Strategy 3 - Use mupx and mup.json to configure which docker container to use as the front end and the meteord.
Instead maybe mupx does what it does best.
This could really open up some possibilities for people that want to do load balancing, vhosts, proxying and routing to multiple apps based on varying requirements coming into nginx as well as all the good stuff like ssl termination and certificate handling.
  Currently, mupx doesn't have the line.  I tossed that in there because I am using force-ssl,
--publish=80:80 \

Another advantage of using this last strategy is that it would allow people to package other applications with their deployment if they want.  It could go so far as having a way to support deployment of other docker containers inside the task runner like email servers, etc... but that might be out of scope.
Next Steps
This started as an email discussion between Arunoda and myself and I sent him some details on what I did to get this working.  It would be easy if for only force-ssl via another environment parameter.
I firmly believe supporting force-ssl is absolutely necessary because it is a core package.  Mupx not supporting core Meteor features seems important and that was my primary goal.
While exploring this I saw other people asking about vhosts, proxying, load balancing, etc... and thought that all of it is probably within reach if a strategy can be agreed upon.
So, with that said, comments and help everyone?

Right now we are using force-ssl meteor package and it works pretty well for us.
But, in the long run we need to support www redirect also. So, I think it's better to handle it via nginx layer. We should allow it by default, but should be possible to turn it off. (If the user is managing SSL and other stuff)
Right now we are not proxying port 80 with nginx. But it the user is asking to implement force-ssl and www-redirect via mup.json file, I think we can do the proxying.

@arunoda It seems implementing force-ssl with nginx would be the most straightforward solution.
But there is some overlap on #454 in terms of how @4shaw implemented a volume on the docker image for nginx to serve static files that is in line with strategy 4 I listed above.

That's another issue and we won't support it.
On Mon, Jun 1, 2015 at 5:13 PM steeve cannon<EMAIL_ADDRESS>wrote:

@arunoda https://github.com/arunoda It seems implementing force-ssl
with nginx would be the most straightforward solution.
But there is some overlap on #454
https://github.com/arunoda/meteor-up/issues/454 in terms of how @4shaw
https://github.com/4shaw implemented a volume on the docker image for
nginx to serve static files that is in line with strategy 4 I listed above.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/458#issuecomment-107410671.

That is valid.
Would you like me to take a stab at support for force-ssl then?
If so, will the strategy be through mupx and mup.json and not via configurable docker containers?
Should nginx always listen 80 and proxy?  Regardless of whether ssl or force-ssl is being used, it seems valid that nginx should always listen on 80 and proxy to a backendPort.
Although that forces use of mup-frontend-server even if you aren't using SSL.  Right now if you aren't using SSL then mup-frontend-server is not used.

We can start by listening to port 80 by default. We still need to use
docker. I
We can use your version of mup-front-end server for that.
But, we need to pass the app when running the docker container via env vars.
Then we need to use it.
There is no easy way to access env vars in nginx conf file, so, you've sed
it.
See: http://serverfault.com/a/582794
On Mon, Jun 1, 2015 at 7:14 PM steeve cannon<EMAIL_ADDRESS>wrote:

That is valid.
Would you like me to take a stab at support for force-ssl then?
If so, will the strategy be through mupx and mup.json and not via
configurable docker containers?
Should nginx always listen 80 and proxy? Regardless of whether ssl or
force-ssl is being used, it seems valid that nginx should always listen on
80 and proxy to a backendPort.
Although that forces use of mup-frontend-server even if you aren't using
SSL. Right now if you aren't using SSL then mup-frontend-server is not used.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/458#issuecomment-107483119.

@arunoda @stephentcannon have you made any progress on forcessl?

is there a way to remove force-ssl ? I have a widget and sometimes its a curse to have https.. any thoughts on this ?

If you integrate LetsEncrypt your free keys should be no reason to not use ssl. Without it passwords can be seen.

Yes I do know that. so what i did was remove MUPX SSL and setup my own nginx setup on the server, So if the user visit http then the server serves http. but for login signup i will have the links setup for https so the user will request the https
server_tokens off; # for security-by-obscurity: stop displaying nginx version

# HTTP
server {
    listen 80 default_server; # if this is not a default server, remove "default_server"
    listen [::]:80 default_server ipv6only=on;

    server_name dishdeep.com; # the domain on which we want to host the application. Since we set "default_server" previously, nginx will answer all hosts anyway.

    add_header Strict-Transport-Security "max-age=0;";

    # redirect non-SSL to SSL
    location / {
        proxy_pass http://<IP_ADDRESS>:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header X-Forwarded-For $remote_addr;
    }

}

# HTTPS server
server {
    listen 443 ssl spdy; # we enable SPDY here
    server_name dishdeep.com; # this domain must match Common Name (CN) in the SSL certificate

    ssl_certificate /etc/letsencrypt/archive/dishdeep.com/fullchain1.pem; # full path to SSL certificate and CA certificate concatenated together
    ssl_certificate_key /etc/letsencrypt/archive/dishdeep.com/privkey1.pem; # full path to SSL key

    # performance enhancement for SSL
    ssl_stapling on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 5m;

    # safety enhancement to SSL: make sure we actually use a safe cipher
    ssl_prefer_server_ciphers on;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:ECDHE-RSA-RC4-SHA:ECDHE-ECDSA-RC4-SHA:RC4-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK';

    # config to enable HSTS(HTTP Strict Transport Security) https://developer.mozilla.org/en-US/docs/Security/HTTP_Strict_Transport_Security
    # to avoid ssl stripping https://en.wikipedia.org/wiki/SSL_stripping#SSL_stripping
    add_header Strict-Transport-Security "max-age=0;";

    # If your application is not compatible with IE <= 10, this will redirect visitors to a page advising a browser update
    # This works because IE 11 does not present itself as MSIE anymore

    # pass all requests to Meteor
    location / {
        proxy_pass http://<IP_ADDRESS>:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $remote_addr; # preserve client IP

        # this setting allows the browser to cache the application in a way compatible with Meteor
        # on every applicaiton update the name of CSS and JS file is different, so they can be cache infinitely (here: 30 days)
        # the root path (/) MUST NOT be cached
        if ($uri != '/') {
            expires 30d;
        }
    }
}


introduce doctrine dbal type for pgvector

@kraynel was faster :laughing:
but i can confirm that this would resolve #38


add option to auto skip cutscenes and hunnigan calls

Describe the feature you'd like to see added
just like the title says, for convenience sake. thank you for your work!

Please! This is a really good suggestion, I would love to see this implemented.

Good idea.  I don't know why this hasn't been suggested before.


Revert "chore(deps-dev): bump nltk from 3.8.1 to 3.8.2 (#653)"

This reverts commit c507489be1d620f4f8ed8db6eaf206a7bf99d774.
Thank you for contributing to the Cohere Toolkit!

[x] PR title: "area: description"

[x] PR message: Delete this entire checklist and replace with

fixes the fact that nltk 3.8.2 is not yet released in pypi and #653 is a FP from Dependabot since 3.8.2 is only in the tags atm
AI Description

This pull request updates the poetry.lock file, which contains package dependencies and their versions.
Summary
The poetry.lock file is automatically generated by Poetry, a dependency management tool for Python projects. This PR updates the Poetry version to 1.6.1 and makes changes to the nltk package:

The nltk package version is updated from 3.8.2 to 3.8.1.
The python-versions requirement for the nltk package is changed from ">=3.8" to ">=3.7".
The hash values for the nltk package files are updated to match the new version.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.25%. Comparing base (5f4acda) to head (699b3ec).
Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #673   +/-   ##
=======================================
  Coverage   76.25%   76.25%
=======================================
  Files         238      238
  Lines       10591    10591
=======================================
  Hits         8076     8076
  Misses       2515     2515

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Allow unicode domain names

Fixes #316
IDNA encoding is not used on standard1.1 and portable as explained here.

Thanks! I think we should drop support for netstandard1.1 then and switch to the minimum netstandard version supporting this.

Portable as well or only std1.1?

yeah, we can remove portable as well.

btw, I wanted to add you as a collaborator of markdig?  (instead of a contributor as it is today) you will have a bit more access to the project (moderate issues...etc.), as you have been quite involved, I was wondering if you would be interested?

Of course, thank you :)

This line can be likely removed:
https://github.com/lunet-io/markdig/blob/f8df3c80e16e98ffe0a0ce8a9a5b7b0f4c345b2f/src/Markdig/Markdown.cs#L20
Haven't checked further, but you can double check (I just did a search on GitHub search, might not be complete!)

I tried, looks like uap10 falls under netstandard11 as far as that check is concerned and it doesn't support the alternative

I tried, looks like uap10 falls under netstandard11 as far as that check is concerned and it doesn't support the alternative

Han ok

Oh, also, as I forgot whenever I have to compile the changelog.md, can you add a new line for the next version about this fix in changelog.md (with a WIP on the version so that we know what to integrate)


mr-ui next

Stubbing a placeholder epic for tracking work that rewrites mr-ui

Modifying the title. It looks like mr-ui never pulled itself out of 2.0.0-beta.2 https://github.com/mapbox/mr-ui/blob/6a9074563941dec6ac7a0c4728f777bd34a8adf9/package.json#L4 so this should likely be a 2.0.0 release.


Clean up e2e/setup

According to git grep, none of these files are referenced anywhere.

Good Spot!


Get the latest

It's no longer necessary for me to build my own layer. Current bref version has all the plugins we need.


feat(azure): add bastion_host

Objective:
Add support for bastion_host.
Status:

[x] Added to registry.go
[x] Added resource file
[x] Added integration tests
[x] Added unit tests if applicable - Not applicable

Useful links:
Pricing:
https://azure.microsoft.com/en-us/pricing/details/azure-bastion/
Terraform:
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/bastion_host
Fix #939

Fix #939

Thanks Kevin!


Unity 2020 LTS with IL2CPP: RPCs with INetworkPlayer parameter cause IL2CPP generation to fail

Describe the bug
This is just for record of an issue discussed in private chat where if you use a function with Unity 2020 like one of the following with a INetworkPlayer player parameter, when you go to compile a IL2CPP build, the IL2CPP compiler will catch fire with an error about casting something to something incorrectly.
[ClientRpc]
private void ThisWillCatchFire(INetworkPlayer player, bool mirageIsAwesome) {
  if(mirageIsAwesome == false)
    throw new Exception("Seriously?!");
  // ...
}

Editor is fine but build with IL2CPP and you'll see smoke.
Repro project
Refer to private chat notes.
To Reproduce
Refer to private chat notes.

Screenshots
Refer to private chat notes.
Additional context
Refer to private chat notes.

Should be fixed up https://github.com/MirageNet/Mirage/pull/1021

Perfect. Another bug solved.


Stabilize chaos-tests.

Improve handling of COMPOSE files for shutting down and logging As currently it was displaying logs only for weaviate-node-1 and 2.
Reduce iterations for go leak tests, as they go over 1hour.
Fix issue with golang version in debug-reindexing as fixing the module naming.

I've launched one job

Also, we need to update the PR description with all the changes you added @rlmanrique (remove the golang version point)

Also, we need to update the PR description with all the changes you added @rlmanrique (remove the golang version point)

Done!


move metrics config to a separated section

We are pursuing a more fine-grained configuration section for metrcis, e.g. scrape interval, etc
Signed-off-by: Changwei Ge<EMAIL_ADDRESS>

Codecov Report
Base: 28.99% // Head: 28.97% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (04309e3) compared to base (69c9c6b).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
- Coverage   28.99%   28.97%   -0.03%
==========================================
  Files          37       37
  Lines        3704     3707       +3
==========================================
  Hits         1074     1074
- Misses       2510     2513       +3
  Partials      120      120

Impacted Files
Coverage Δ

config/config.go
9.00% <0.00%> (-0.28%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


angular-leaflet-directive 0.8.8 requires nemLogging

If I update the module to version 0.8.8 it fails to start with this error:
Error: [$injector:modulerr] Failed to instantiate module demoapp due to:
[$injector:modulerr] Failed to instantiate module leaflet-directive due to:
[$injector:modulerr] Failed to instantiate module nemLogging due to:
[$injector:nomod] Module 'nemLogging' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.4.5/$injector/nomod?p0=nemLogging
minErr/<@file:///home/rpadovani/Archon/leaflet/bug-linestring/bower_components/angular/angular.js:68:12
module/<@file:///home/rpadovani/Archon/leaflet/bug-linestring/bower_components/angular/angular.js:1983:1
ensure@file:///home/rpadovani/Archon/leaflet/bug-linestring/bower_components/angular/angular.js:1907:38
module@file:///home/rpadovani/Archon/leaflet/bug-linestring/bower_components/angular/angular.js:1981:1

I've no idea what nemLogging is supposed to be.

Dublicate #918
As per #829 you need to include angular-simple-logger into your project now.

I have "angular-simple-logger": "~0.0.1", in my bower.json, it doesn't work.

You have to load the script prior. There are tools out there to do this for you or you need to move it or direct the html to the correct location.

Too bad, this library doesn't use semantic versionning... Introducing a BC break like this broke a lot of things and semver would have prevented breaking our builds.

@iammichiel yup. #829

It would probably be best if we update the gh-pages so the examples at http://tombatossals.github.io/angular-leaflet-directive reflect this.  The examples using 0.8.6 threw me off too.

See #984 I will start digging into the gh-pages.


Setting terraform

I'm writing functions and make strucutre for serverless architecture using cloud scheduler, function

Success!


Add player collision to example

It'd be useful to show how one can get the player to collide with objects since that seems like it'd be a common use case.

I tried briefly trying to make the camera a rigid body but kept falling through the ground. Will revisit later.

https://github.com/ngokevin/aframe-physics-components/pull/8


Improve gpflow2 code coverage by adding tests

Improve code coverage

I added the same extension of the likelihoods quadrature checks to develop (#1081), which passes. This means that ndiagquad in develop-2.0 has a bug.

Code coverage is now above 95%, so I think it's worth just changing the threshold for codecov to 95%, so that the build status checks (which are red as soon as any test fails) become meaningful again, and to ensure we can more easily distinguish passing PRs from actually failing ones in the pull request overview.

First green build on a gpflow2 branch :wink:


audio: Support for lws

Added a param use_lws (default False). If True use https://github.com/Jonathan-LeRoux/lws for STFT and phase reconstruction. This is needed to use with https://github.com/r9y9/wavenet_vocoder.
preprocess: Minor fix to support LJSpeech 1.0

@r9y9 What is the benefit of LWS over librosa?


Metric Learning of Melanoma Classification

This pull request is to classify benign and malignant skin lesions using a siamese network. It uses a ResNet50 backbone to extract salient features from the images and create an embeddings space where the two classes are as far away from each other as possible.

Future work:
To transition from ResNet to MobileNet, which is showing indicators of better performance

This current iteration now utilises Inception Net with a better oversampling strategy

This iteration now has options to select different types of models and datasets. The default arguments used should be --full-dataset.

This is an initial inspection, no action is required at this point
Recognition Problem : total : 19
Solves problem: The solution is well-suited to the problem (4) but the validation accuracy and other paramaters havehigh fluctuations.
The training manifold is not well separated
the classifier shows good performance in training but not the validation.
Triplet loss is utilized, which is suitable for the problem.
Class imbalance is addressed through oversampling the benign cases.
Implementation functions as intended (2)
Good design: Well-designed (1)
Commenting: Clear and sufficient comments throughout the code. (1)
Difficulty: Hard (10)
Note:
+Well understaning of the problem and the usgae of metric leaning to solve it along with its challanges.

Validation Loss: Downward trend with high fluctuations; suggests instability. Try lowering learning rates or adding regularization.
Validation Accuracy: Inconsistent, possibly not converged. Consider monitoring for more epochs and implementing early stopping.
Precision & Recall: Significant variation, possibly due to class imbalance. Address with class weighting or data augmentation.
Overall Stability: Add techniques like gradient clipping, batch normalization, or learning rate schedules to reduce oscillations.

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation.
Spacing and comments.
No Header blocks. -1
Recognition Problem
Good solution to problem.
Driver Script present.
File structure present.
Good Usage & Demo & Visualisation & Data usage. The training manifold is not well separated.-1
Module present.
Commenting present.
No Data leakage found. Has data splits.
Difficulty : Hard.  Siamese network (Hard Difficulty)
Commit Log
Good Meaningful commit messages.
Good Progressive commits.
Documentation
Readme :Good.
Model/technical explanation :Good.
Description and Comments :Acceptable. References missing.-1
Markdown used and PDF submitted. PDF Checked.
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch). On time.
No Feedback required.
Request Description is good.
TOTAL-3

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes


Django

Function imported from app.py gets invoked twice in django (probably due to development build)

Fixed

Fixed


Fix usage docs

Thanks, sorry for the delay.

Thanks for fixing the docs, this was pushed to npmjs.com a couple of hours ago.


I got some problem with connection to fire base.

I know that this project only support http can't pass through https protocol .
But when i run the code, every connection action will go through https , i've try to fix, but finally i always got{
creating resource: [message] fopen(): SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
}
Can you give me some advice , I've tride all day and didn't got any reward.
Please .

I solve it , although I didn't get ssl passed , but if you change the vendor/guzzlehttp/guzzle/src/clinet.php
add $uri='http://fcm.googleapis.com/fcm/send'; in request($method, $uri = '', array $options = []).
If there any one had the same problem  it can end your suffer.


Fix for Default service dialog values not included in EVM when 'refresh_dialog_fields' action invoked

When calling the API directly, the refresh option gets set to true, and ends up making a call to load_values_into_fields. This is fine if the API call provides the values that the field should be refreshed with, but without the values, customer was running into an issue where they had a few fields that were static and not visible to the user (so therefore just automatically filled in and ready to go) that they did not pass in to the API call in <IP_ADDRESS>. On updating to <IP_ADDRESS>, I believe that https://github.com/ManageIQ/manageiq/pull/17329 made the change to attempt to eliminate automate calls that were happening when calling refresh that didn't need to happen, but also this eliminated the "call" to get the static field values. Again, this is fine if the API call provides these static values in the POST request (which is what the UI does), but direct use of the API does not necessarily inform the user that they should do that.
For @tinaafitz and @gtanzillo (and anyone else) to review: it should be easier to track the "main" change if you go commit by commit, since the first commit contains the "meat" of the change, the second commit just moves the #load_dialog method into the private namespace since it's not used elsewhere and separates out the block of if/else logic into another method.
@miq-bot add_reviewer @tinaafitz
@miq-bot add_reviewer @gtanzillo
@miq-bot add_label bug
@tinaafitz My apologies but I've been out of the cloudforms loop for a bit, so please add any other labels hammer/yes, hammer/no (?) that this might need.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1730813

@tinaafitz @gtanzillo I had to update the code a bit after testing on the appliance. Basically what happened was if you didn't pass in parameters, it went and used my new code that set the static values beautifully....but then overwrote them with nils because you didn't pass in parameters, ending up with exactly the same response as before. D'oh.
So instead, we pass false to the load_values_into_fields call, which used to be the overwrite parameter, but after looking at it more closely that's not really a good name, since while it does "overwrite" the value that a field potentially already has, it really only needs to be doing that if it's not nil.

@eclarizio Are you or @billfitzgerald0120 still planning on testing this manually? I was planning on merging after that.

Sorry @eclarizio, @billfitzgerald0120 missed the comment above. Thanks! I'll merge 👍

hammer/yes ?

Hammer backport details:
$ git log -1
commit 6817c3365b1fb371be1b4ec5fa0d9bc232727daf
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Fri Jul 19 11:30:47 2019 -0400

    Merge pull request #19005 from eclarizio/BZ1730813-CiscoAPIFix

    Fix for Default service dialog values not included in EVM when 'refresh_dialog_fields' action invoked

    (cherry picked from commit a8a06f8826660553e00ec3ff49f0c8bad4f54681)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1731977


WIP GeoMesa BlobStore Refactoring

Start of refactoring effor to make GeoMesa BlobStore pluggable with both DataStore and BlobStore interfaces.
probably won't build...

holding off till 1.2.4

replaced by #960


Unable to select RGB Colours in Home App

What issue do you have? Please be as thorough and explicit as possible.
I have two H6159 strip lights which I am unable to set to RGB colours when using the Apple Home App. Instead of changing to the selected colour, they default to a low-brightness blue/white. I am only able to change the colour using the temperature mode or going into the Goove App
I tried removing and re-adding the lights which seemed to work for a little while but it has now stopped working again. Now if I remove and re-add the lights to the Home App but do not set up adaptive lighting in the app, the Home app crashes when I select and RGB colour
I have tried setting up BLE connection, and disabling adaptive lighting, allowing API whitelisting but none of those has worked.
I also tried creating automation to turn/change the lights to RGB colour, but the Automation just fails.
Photos added show the colour of the LEDs when selecting RGB Red in the home App as an example
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
I manage the homebridge using the web app.

Which version of Homebridge/HOOBS do you have?
I am currently running v1.5.1

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi and running node.js v16.18.0

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
currently running v7.1.1.
It has worked previously but unfortunately, I can not give an exact version number it stopped working on. I would say I've only noticed the issue in the past month or so

Which Govee devices do you have that are causing issues? Please include product models if applicable.
H6159 LED lights

Please paste any relevant logs below.

[10/25/2022, 8:16:42 PM] [Govee] [Desk lights] current colour [rgb 25 29 255].
[10/25/2022, 8:16:42 PM] [Govee] [Sideboard lights] [AWS] sending update {"msg":{"cmd":"color","cmdVersion":0,"data":{"r":25,"g":29,"b":255},"transaction":"v_1666725402857000","type":1}}.
[10/25/2022, 8:16:42 PM] [Govee] [Sideboard lights] current colour [rgb 25 29 255].
[10/25/2022, 8:16:43 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725402857000\",\"sku\":\"H6159\",\"device\":\"8C:85:A4:C1:38:FA:AD:DB\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"color\",\"data\":\"{\\\"red\\\":49,\\\"green\\\":49,\\\"blue\\\":49}\"}","state":{"onOff":1,"brightness":254,"color":{"r":49,"g":49,"b":49},"colorTemInKelvin":0,"connected":"true","sku":"H6159","device":"8C:85:A4:C1:38:FA:AD:DB"}}].
[10/25/2022, 8:16:44 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725402851000\",\"sku\":\"H6159\",\"device\":\"1F:F5:A4:C1:38:93:D9:EC\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"color\",\"data\":\"{\\\"red\\\":49,\\\"green\\\":49,\\\"blue\\\":49}\"}","state":{"onOff":1,"brightness":254,"color":{"r":49,"g":49,"b":49},"colorTemInKelvin":0,"connected":"true","sku":"H6159","device":"1F:F5:A4:C1:38:93:D9:EC"}}].
[10/25/2022, 8:16:47 PM] [Govee] [Desk lights] [AWS] sending update {"msg":{"cmd":"color","cmdVersion":0,"data":{"r":255,"g":204,"b":204},"transaction":"v_1666725407341000","type":1}}.
[10/25/2022, 8:16:47 PM] [Govee] [Desk lights] current colour [rgb 255 204 204].
[10/25/2022, 8:16:47 PM] [Govee] [Sideboard lights] [AWS] sending update {"msg":{"cmd":"color","cmdVersion":0,"data":{"r":255,"g":204,"b":204},"transaction":"v_1666725407347000","type":1}}.
[10/25/2022, 8:16:47 PM] [Govee] [Sideboard lights] current colour [rgb 255 204 204].
[10/25/2022, 8:16:48 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725407341000\",\"sku\":\"H6159\",\"device\":\"1F:F5:A4:C1:38:93:D9:EC\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"color\",\"data\":\"{\\\"red\\\":49,\\\"green\\\":49,\\\"blue\\\":49}\"}","state":{"onOff":1,"brightness":254,"color":{"r":49,"g":49,"b":49},"colorTemInKelvin":0,"connected":"true","sku":"H6159","device":"1F:F5:A4:C1:38:93:D9:EC"}}].
[10/25/2022, 8:16:49 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725407347000\",\"sku\":\"H6159\",\"device\":\"8C:85:A4:C1:38:FA:AD:DB\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"color\",\"data\":\"{\\\"red\\\":49,\\\"green\\\":49,\\\"blue\\\":49}\"}","state":{"onOff":1,"brightness":254,"color":{"r":49,"g":49,"b":49},"colorTemInKelvin":0,"connected":"true","sku":"H6159","device":"8C:85:A4:C1:38:FA:AD:DB"}}].
[10/25/2022, 8:16:51 PM] [Govee] [Desk lights] [AWS] sending update {"msg":{"cmd":"colorTem","cmdVersion":0,"data":{"colorTemInKelvin":2200,"color":{"r":255,"g":147,"b":44,"red":255,"green":147,"blue":44}},"transaction":"v_1666725411161000","type":1}}.
[10/25/2022, 8:16:51 PM] [Govee] [Desk lights] current colour [2200K / 454M].
[10/25/2022, 8:16:51 PM] [Govee] [Sideboard lights] [AWS] sending update {"msg":{"cmd":"colorTem","cmdVersion":0,"data":{"colorTemInKelvin":2200,"color":{"r":255,"g":147,"b":44,"red":255,"green":147,"blue":44}},"transaction":"v_1666725411168000","type":1}}.
[10/25/2022, 8:16:51 PM] [Govee] [Sideboard lights] current colour [2200K / 454M].
[10/25/2022, 8:16:51 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725411168000\",\"sku\":\"H6159\",\"device\":\"8C:85:A4:C1:38:FA:AD:DB\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"colorTem\",\"data\":\"{\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":147,\\\"blue\\\":44},\\\"colorTemInKelvin\\\":2200}\"}","state":{"onOff":1,"brightness":254,"color":{"r":255,"g":147,"b":44},"colorTemInKelvin":2200,"connected":"true","sku":"H6159","device":"8C:85:A4:C1:38:FA:AD:DB"}}].
[10/25/2022, 8:16:52 PM] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1666725411161000\",\"sku\":\"H6159\",\"device\":\"1F:F5:A4:C1:38:93:D9:EC\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"colorTem\",\"data\":\"{\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":147,\\\"blue\\\":44},\\\"colorTemInKelvin\\\":2200}\"}","state":{"onOff":1,"brightness":254,"color":{"r":255,"g":147,"b":44},"colorTemInKelvin":2200,"connected":"true","sku":"H6159","device":"1F:F5:A4:C1:38:93:D9:EC"}}].

Hi @ryanlbates01
I think there could be a number of things going on here.
It would be useful to direct message on discord if you'd be happy to do so? Invite link is:
https://discord.gg/cMGhNtZ3tW

Hi bwp91
sure thing, I’ve clicked on the invite link and I’ve joined your server. I’m ryanlbates01

Hello. I had the same issues. It don´t apply the color.

@GodzillaTV which model?

I have the Govee H6159. Hardware Version: 1.00.02.

ok es funktioniert jetzt wieder...

Has anyone found a fix for this? I have the exact same problem with my two light bulbs. Both are H6009

Has anyone found a fix for this? I have the exact same problem with my two light bulbs. Both are H6009

I think this is a per model solution. can you try updating to the beta version to see if this is fixed for your H6009?

I just updated to the new beta and it did not fix the issue. I even deleted the H6009 and re-added them, changed my govee password and api key, and cleared all my caches. Im able to turn the lights on and off but not able to change the color. I am able to adjust the brightness however when the brightness gets to 99% it is at about max brightness but when I go up to 100% the night then visually dims way down to almost 1% brightness but the home app still shows it as being at 100%. I'll attach screen shot of my logs from when I try changing the colors. I have about 30 various Govee lights and this issue is only occurring with my two H6009s. Both did work as intended in the past. The H6009s in my logs are named TV Lamp and Couch Lamp. Ill also attach a text file of all my logs however it is quite long.

HomeBridge Logs .txt

@Iverson20 ignore my last message, can you try a newer beta I have just published? 7.1.4-beta.0

Hello. I had the same issues. I'm not able to change the Color.
Model H615C
Hardware Version 2.01.01
Thx

Hello. I had the same issues. I'm not able to change the Color.
Model H615C
Hardware Version 2.01.01
Thx

Hi @lvl03 can you enable debug logging in the plugin settings, then restart, then use the govee app to change the colour to red, and post here the logs that appear in homebridge from doing this action?

Hello. I had the same issues. I'm not able to change the Color.
Model H615C
Hardware Version 2.01.01
Thx

Hi @lvl03 can you enable debug logging in the plugin settings, then restart, then use the govee app to change the colour to red, and post here the logs that appear in homebridge from doing this action?

[Govee] [Decke Flur] current colour [rgb 255 0 0]

Hi! I have the same issue with HS7020 light bulb strings. I can turn on/off, but I can only change color from the Govee App. I am using the latest 7.4.0 version, latest home bridge 1.6.0, node 18.12.1.
BTW, I tried rolling back to 7.1.x, and it was working there.
Here are the logs when trying to change from the Govee App (it's OK):
[03/12/2022, 02:20:57] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"a_1670034056865","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":0,"g":255,"b":0},"result":1}}].
[03/12/2022, 02:20:57] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":0,"g":255,"b":0},"result":1}.
[03/12/2022, 02:20:57] [Govee] [LED Bulb String Lights] current colour [rgb 0 255 0].
[03/12/2022, 02:21:05] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"a_1670034064098","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":255,"g":255,"b":0},"result":1}}].
[03/12/2022, 02:21:05] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":255,"g":255,"b":0},"result":1}.
[03/12/2022, 02:21:05] [Govee] [LED Bulb String Lights] current colour [rgb 255 255 0].
[03/12/2022, 02:21:09] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"a_1670034068522","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":255,"g":0,"b":0},"result":1}}].
[03/12/2022, 02:21:09] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":255,"g":0,"b":0},"result":1}.

Here is when changing from the Home App (2 attempts - and it seems whatever I select it defaults back to  [rgb 24 58 3].
[03/12/2022, 02:41:56] [Govee] [LED Bulb String Lights] [AWS] sending update {"msg":{"cmd":"color","cmdVersion":0,"data":{"red":255,"green":24,"blue":132},"transaction":"v_1670031716262000","type":1}}.
[03/12/2022, 02:41:56] [Govee] [LED Bulb String Lights] current colour [rgb 255 24 132].
[03/12/2022, 02:41:58] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"v_1670031716262000","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"result":1}}].
[03/12/2022, 02:41:58] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"result":1}.
[03/12/2022, 02:41:58] [Govee] [LED Bulb String Lights] current colour [rgb 24 58 3].
----
[03/12/2022, 02:42:47] [Govee] [LED Bulb String Lights] [AWS] sending update {"msg":{"cmd":"color","cmdVersion":0,"data":{"red":58,"green":51,"blue":255},"transaction":"v_1670031767237000","type":1}}.
[03/12/2022, 02:42:47] [Govee] [LED Bulb String Lights] current colour [rgb 58 51 255].
[03/12/2022, 02:42:47] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"v_1670031767237000","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"result":1}}].
[03/12/2022, 02:42:47] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"result":1}.
[03/12/2022, 02:42:47] [Govee] [LED Bulb String Lights] current colour [rgb 24 58 3].

Best Regards,
István

Hi @fifibest
If you use the govee app to turn the brightness of this light to 100%, does this update correctly in homekit? Or does it display a different brightness %?

Hi @bwp91
Thanks for your reply, you're right, when I set the brightness from the Govee app, HomeKit displays different values: 33% in app, 13% in HomeKit:
[03/12/2022, 20:40:22] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"brightness","type":0,"transaction":"a_1670100021034","pactType":1,"pactCode":1,"state":{"brightness":33,"result":1}}].
[03/12/2022, 20:40:22] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","brightness":33,"result":1}.
[03/12/2022, 20:40:22] [Govee] [LED Bulb String Lights] current brightness [13%].
[03/12/2022, 20:40:31] [Govee] [LED Bulb String Lights] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1670096431416000","type":0}}.
[03/12/2022, 20:40:31] [Govee] [LED Bulb String Lights] [API] receiving update {"online":true,"powerState":"on","brightness":33,"color":{"r":24,"b":3,"g":58},"source":"API"}.
[03/12/2022, 20:40:33] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"status","type":0,"transaction":"v_1670096431416000","pactType":1,"pactCode":1,"state":{"onOff":1,"brightness":33,"colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"mode":21,"result":1},"op":{"command":["qgUVAAAAAAAAAAAAAAAAAAAAALo=","qqUBZBg6A2QYOgNkGDoDAAAAAEs=","qqUCZBg6A2QYOgNkGDoDAAAAAEg=","qqUDZBg6A2QYOgNkGDoDAAAAAEk=","qqUEZBg6A2QYOgNkGDoDAAAAAE4=","qqUFZBg6A2QYOgNkGDoDAAAAAE8=","qqUGZBg6A2QYOgNkGDoDAAAAAEw=","qqUHZBg6A2QYOgNkGDoDAAAAAE0=","qqUIZBg6A2QYOgNkGDoDAAAAAEI=","qqUJZBg6A2QYOgNkGDoDAAAAAEM=","qqUKZBg6A2QYOgNkGDoDAAAAAEA=","qhEAHg8PAAAAAAAAAAAAAAAAAKU=","qhL/ZAAAgAoAAAAAAAAAAAAAAKk=","qiP/AAAAgAAAAIAAAACAAAAAgHY=","qkEBAAAAAAAAAAAAAAAAAAAAAOo=","qg8BAAAAAAAAAAAAAAAAAAAAAKQ="]}}].
[03/12/2022, 20:40:33] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","onOff":1,"brightness":33,"colorTemInKelvin":0,"color":{"r":24,"g":58,"b":3},"mode":21,"result":1,"commands":["qgUVAAAAAAAAAAAAAAAAAAAAALo=","qqUBZBg6A2QYOgNkGDoDAAAAAEs=","qqUCZBg6A2QYOgNkGDoDAAAAAEg=","qqUDZBg6A2QYOgNkGDoDAAAAAEk=","qqUEZBg6A2QYOgNkGDoDAAAAAE4=","qqUFZBg6A2QYOgNkGDoDAAAAAE8=","qqUGZBg6A2QYOgNkGDoDAAAAAEw=","qqUHZBg6A2QYOgNkGDoDAAAAAE0=","qqUIZBg6A2QYOgNkGDoDAAAAAEI=","qqUJZBg6A2QYOgNkGDoDAAAAAEM=","qqUKZBg6A2QYOgNkGDoDAAAAAEA=","qhEAHg8PAAAAAAAAAAAAAAAAAKU=","qhL/ZAAAgAoAAAAAAAAAAAAAAKk=","qiP/AAAAgAAAAIAAAACAAAAAgHY=","qkEBAAAAAAAAAAAAAAAAAAAAAOo=","qg8BAAAAAAAAAAAAAAAAAAAAAKQ="]}.

@fifibest
Can you install the beta version of the plugin and see whether brightness and colour are now fixed?
https://github.com/bwp91/homebridge-govee/wiki/Beta-Version
Thanks!

I can confirm that with the latest beta, brightness and color values are passed correctly to / from HomeKit.
[03/12/2022, 22:26:54] [Govee] [LED Bulb String Lights] current colour [rgb 255 190 39].
[03/12/2022, 22:26:55] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"v_1670102814829000","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":255,"g":190,"b":39},"result":1}}].
[03/12/2022, 22:26:55] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":255,"g":190,"b":39},"result":1}.
[03/12/2022, 22:26:55] [Govee] [LED Bulb String Lights] current colour [rgb 255 190 39].
[03/12/2022, 22:26:56] [Govee] [LED Bulb String Lights] [AWS] sending update {"msg":{"cmd":"colorwc","cmdVersion":0,"data":{"color":{"r":23,"g":255,"b":209,"red":23,"green":255,"blue":209},"colorTemInKelvin":0},"transaction":"v_1670102816657000","type":1}}.
[03/12/2022, 22:26:56] [Govee] [LED Bulb String Lights] current colour [rgb 23 255 209].
[03/12/2022, 22:26:57] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"colorwc","type":0,"transaction":"v_1670102816657000","pactType":1,"pactCode":1,"state":{"colorTemInKelvin":0,"color":{"r":23,"g":255,"b":209},"result":1}}].
[03/12/2022, 22:26:57] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","colorTemInKelvin":0,"color":{"r":23,"g":255,"b":209},"result":1}.

[03/12/2022, 22:27:28] [Govee] [AWS] message event [{"proType":2,"sku":"H7020","device":"FB:9C:C4:32:37:35:3D:94","softVersion":"1.00.14","wifiSoftVersion":"1.00.28","cmd":"brightness","type":0,"transaction":"a_1670106447261","pactType":1,"pactCode":1,"state":{"brightness":70,"result":1}}].
[03/12/2022, 22:27:28] [Govee] [LED Bulb String Lights] [AWS] receiving update {"source":"AWS","brightness":70,"result":1}.
[03/12/2022, 22:27:28] [Govee] [LED Bulb String Lights] current brightness [70%].

Thanks for the quick reply and fix for this issue!

@bwp91 Hello there, first of all THANK YOU!
Your Plugin is just perfect and I really admire all the hard work you've put into it.
My H6182 is having similar problems, neither the colour, nor the brightness will change trough the Home App.
It was possible about three months ago but suddenly stopped working.
Device: H6182 (LED Strip); SW-Version: 1.02.16; HW-Version: 1.00.01
homebridge-govee v7.7.1 (and also in previous versions)
Logs from HomeBridge (homebridge-govee v7.7.1):
While trying to change the colour with HomeKit:
[30/12/2022, 17:34:31] [Govee] [Hintergrundbeleuchtung] current colour [rgb 89 255 13].
[30/12/2022, 17:34:44] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"1234567890\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":100,\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:34:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418098517000","type":0}}.
[30/12/2022, 17:34:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":35,"color":{"r":255,"b":0,"g":0},"source":"API"}.

[30/12/2022, 17:36:35] [Govee] [Hintergrundbeleuchtung] current colour [rgb 92 92 255].
[30/12/2022, 17:36:51] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"1234567890\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":100,\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:36:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418218518000","type":0}}.
[30/12/2022, 17:36:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":35,"color":{"r":255,"b":0,"g":0},"source":"API"}.

While changing colour with Govee Home:
[30/12/2022, 17:42:30] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"1234567890\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":254,\\\"modeValue\\\":[\\\"qgUC////AP+NCwAAAAAAAAAAACs=\\\"],\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":255,\\\"blue\\\":255},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":254,"color":{"r":255,"g":255,"b":255},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:42:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418578520000","type":0}}.
[30/12/2022, 17:42:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":100,"color":{"r":255,"b":255,"g":255},"source":"API"}.

[30/12/2022, 17:44:54] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"1234567890\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":254,\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":254,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:44:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418698522000","type":0}}.
[30/12/2022, 17:44:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":100,"color":{"r":255,"b":0,"g":0},"source":"API"}.

While trying to change the brightness with HomeKit:
[30/12/2022, 17:38:58] [Govee] [Hintergrundbeleuchtung] current brightness [100%].
[30/12/2022, 17:38:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418338517000","type":0}}.
[30/12/2022, 17:38:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":35,"color":{"r":255,"b":0,"g":0},"source":"API"}.
[30/12/2022, 17:39:00] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1672418338496000\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"brightness\",\"data\":\"{\\\"val\\\":100}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:39:01] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1672418338517000\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":100,\\\"modeValue\\\":[\\\"qgUC/wAAAP+NCwAAAAAAAAAAACs=\\\"],\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].

[30/12/2022, 17:40:33] [Govee] [Hintergrundbeleuchtung] current brightness [7%].
[30/12/2022, 17:40:43] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"1234567890\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":100,\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].
[30/12/2022, 17:40:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418458519000","type":0}}.
[30/12/2022, 17:40:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":35,"color":{"r":255,"b":0,"g":0},"source":"API"}.
[30/12/2022, 17:41:01] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1672418458519000\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":100,\\\"modeValue\\\":[\\\"qgUC/wAAAP+NCwAAAAAAAAAAACs=\\\"],\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":0,\\\"blue\\\":0},\\\"colorTemInKelvin\\\":0}\"}","state":{"onOff":1,"brightness":100,"color":{"r":255,"g":0,"b":0},"colorTemInKelvin":0,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].

While changing the brightness with Govee Home:
[30/12/2022, 17:46:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418818524000","type":0}}.
[30/12/2022, 17:46:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":25,"colorTemInKelvin":2000,"colorTem":2000,"source":"API"}.
[30/12/2022, 17:46:59] [Govee] [Hintergrundbeleuchtung] current brightness [25%].
[30/12/2022, 17:47:00] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1672418818524000\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":75,\\\"modeValue\\\":[\\\"qgUC////Af+NCwAAAAAAAAAAACo=\\\"],\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":141,\\\"blue\\\":11},\\\"colorTemInKelvin\\\":2000}\"}","state":{"onOff":1,"brightness":75,"color":{"r":255,"g":141,"b":11},"colorTemInKelvin":2000,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].

[30/12/2022, 17:47:58] [Govee] [Hintergrundbeleuchtung] [AWS] sending update {"msg":{"cmd":"status","cmdVersion":2,"transaction":"v_1672418878526000","type":0}}.
[30/12/2022, 17:47:59] [Govee] [Hintergrundbeleuchtung] [API] receiving update {"online":true,"powerState":"on","brightness":75,"colorTemInKelvin":2000,"colorTem":2000,"source":"API"}.
[30/12/2022, 17:47:59] [Govee] [Hintergrundbeleuchtung] current brightness [75%].
[30/12/2022, 17:48:00] [Govee] [AWS] message event [{"proType":0,"msg":"{\"transaction\":\"v_1672418878526000\",\"sku\":\"H6182\",\"device\":\"4E:03:A4:C1:38:F0:64:96\",\"cmdVersion\":0,\"type\":0,\"cmd\":\"status\",\"data\":\"{\\\"softversion\\\":\\\"1.02.16\\\",\\\"wifiSoftVersion\\\":\\\"1.02.07\\\",\\\"turn\\\":1,\\\"brightness\\\":195,\\\"modeValue\\\":[\\\"qgUC////Af+NCwAAAAAAAAAAACo=\\\"],\\\"mode\\\":2,\\\"timer\\\":{\\\"enable\\\":-1,\\\"isGroup\\\":1,\\\"time\\\":[{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0},{\\\"openHour\\\":0,\\\"openMin\\\":0,\\\"closeHour\\\":23,\\\"closeMin\\\":59,\\\"repeat\\\":128,\\\"enable\\\":0}]},\\\"color\\\":{\\\"red\\\":255,\\\"green\\\":141,\\\"blue\\\":11},\\\"colorTemInKelvin\\\":2000}\"}","state":{"onOff":1,"brightness":195,"color":{"r":255,"g":141,"b":11},"colorTemInKelvin":2000,"connected":"true","sku":"H6182","device":"4E:03:A4:C1:38:F0:64:96"}}].

Hi @eyeslow can you install the new beta version of the plugin and see if brightness and/or colour control is fixed?

Hi @eyeslow can you install the new beta version of the plugin and see if brightness and/or colour control is fixed?

Wow, that was fast. Everything is working as expected, the colour changes correctly and also the brightness gets applied properly. Thank you!
This change will be included in the next main release, am I right?
Have a pleasant evening and a happy new year!


Fixes #4406 PEP 561 support

Fixes #4406 PEP 561 support
Adds support for locating type stub packages.
Makes AstPythonInterpreterFactory import process fully async and cancelable
Fixes minor bugs in import completion and module scraping

@AlexanderSher Any further comments?


add commit hash with link to github into frontend

🍰 Pullrequest

add commit hash to frontend footer
add link to github commit to frontend footer

Issues

fixes #744

For me this looks good now (except that test requirement of @Elweyn )
We should do a rebase tho, since the Klicktipp-Stuff affects the config.

Still needs the rebase for

I don't like rebase, most time it is a mess and much work to solve all conflicts which haven't any todo with my code chances.
Most of the time I make better experience with less work with merging.


Merge upstream - 7

Thank you for rebasing the branch.
Hopefully I didn't cause too much mess in fixing the conflicts on the Neogit/ckolkey branch to keep it up to date to Neogit/master.

No worries, I think the confusion came from the commits you made to ckolkey but not to master. Not an issue, I just didn't notice 😅 In any case, I'll get this in ship-shape tomorrow

Yes, merges are tricky because you end up with commits from the target branch sprinkled ontop, which brings more confusion when you add more commits yourself, so the history looks like this:

my feature
my feature
from main from someone else
from main from someone else
my feature

I prefer rebase but it isn't always possible for public branches

Agreed. Well... third time is the charm: https://github.com/TimUntersberger/neogit/pull/531