Add Shelly to issue_context.yaml (#294)

Co-authored-by: Shay Levy <[email protected]>

data/github/issue_context.yaml

@@ -28,3 +28,12 @@
   5. Fill out the issue template and include whether or not you're using a VM/Proxmox with USB passthrough, what addons you have installed, and so on.
 
   ZHA does not have low-level control over your network, the mesh is self-organizing. If you started having network issues in a specific release, the release probably didn't cause the issue. Check your environment for new sources of 2.4GHz interference and make sure you're using an extension cable, not placing the coordinator near SSDs and USB 3.0 ports, etc. Just because things worked in the past with a bad setup doesn't mean they'll keep working in the future.
+"integration: shelly": >-
+  If your issue is related to Shelly generation 1 device, make sure you have configured [CoIoT peer](https://www.home-assistant.io/integrations/shelly/#shelly-device-configuration-generation-1) correctly.
+
+  If your issue is related to **battery powered** Shelly generation 2/3/4 devices, make sure you have configured [Outbound WebSocket](https://www.home-assistant.io/integrations/shelly/#shelly-device-configuration-generation-2-and-3) correctly.
+
+  Please enable [Shelly debug logging](https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging), let it run for 10-15 minutes, and make sure to capture whatever problem you're having in the debug log.
+  Note: it is better to drag the log file into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.
+
+  Finally, be sure to include [diagnostics](https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics) for the Shelly device you're having problems with.