Просмотр исходного кода

Issue template: remove alternative suggestion of full_info logs

Based on recent requests, full_info=true does not seem to return the same
info as the logs at initial connection. In some cases it is returning even
less that full_info=false log lines.
Jason Rumney 7 месяцев назад
Родитель
Сommit
6f1d123201
1 измененных файлов с 1 добавлено и 2 удалено
  1. 1 2
      .github/ISSUE_TEMPLATE/new-device.yaml

+ 1 - 2
.github/ISSUE_TEMPLATE/new-device.yaml

@@ -11,7 +11,7 @@ body:
         Thank you for reporting your unsupported device. Please provide as much information as you can. Because the developers are busy, new device requests will be prioritised as follows:
 
           1. Pull requests
-          2. Issues with logs and QueryThingsDataModel API results or equivalent
+          2. Issues with warning level logs from when adding the device and QueryThingsDataModel API results or equivalent
           3. Issues with logs and enough dps info to make a useful config.
           4. Issues with logs and a tested config
 
@@ -21,7 +21,6 @@ body:
       label: Log message
       description: |
         From the Home Assistant log (Settings / System /Log), please paste the Warning level log message containing a **dps** list which is output when you attempt to add the device and are presented with a list of non-matching devices.
-        Alternatively, if you already added the device, you can turn on debug logging for a minute or so, and find a message in the log from your device which has `full_poll: true` as part of the message.
         Providing logs shows that you have tried this integration, the device is able to connect, and existing configs are not adequate. They also show exactly what the device is sending, which helps avoid some back and forward steps to get the config working.
       placeholder: Reports without local logs from this integration will be immediately closed
       render: text