wireless

A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

Feature Description

Add the ability to display the grid that blocks snap to in GRC. This should be toggleable and saved using a preference and have a menu item in the dropdown menu to enable/disable.

Feature Urgency

low (just an idea)

More Information

Thanks to @skoslowski for outlining the steps to implement the drawing of the grid:

To implement it, you'll want to start here

In #1122, @okke-formsma added a new ignore-modifiers property you can set on sticky keys, but the docs got missed for documenting the option. Need to add to docs/docs/behaviors/sticky-key.md in the "Configuration" section.

Indicator CC V4 adds two new commands:

• Indicator Description Get Command
• Indicator Description Report Command

https://github.com/zwave-js/node-zwave-js/blob/master/specs/SDS13782%20Z-Wave%20Management%20Command%20Class%20Specification.pdf

TODOs:

• Implement the new commands
• Implement a getDescription method on IndicatorCCAPI
• update @implementedVersion decor

Steps to replicate

1. Create a VPN server with OpenVPN backend
2. Create a template for the VPN server created in step 1
3. Create a device and apply the template created in step 2 to this device
4. Go to /admin/pki/cert/ and delete the certificate related to the device

Expected Outcome
The certificate is deleted and along with it VpnClient object is also deleted.

**Ac

Geocoding tests are converted in deployment checks via this PR

We should add this checks to ensure geocoding works as expected