README: remove device specific issues

Only a few early devices were covered, with almost 1000 device configs
now, this approach is not scalable, and many of the "issues" are obsolete.

README.md

@@ -233,113 +233,6 @@ When adding devices, some devices that are detected as protocol version
 3.3 at first require version 3.2 to work correctly. Either they cannot be
 detected, or work as read-only if the pprotocol is set to 3.3.
 
-## Heater issues
-
-Goldair GPPH heaters have individual target temperatures for their
-Comfort and Eco modes, whereas Home Assistant only supports a single
-target temperature. Therefore, when you're in Comfort mode you will
-set the Comfort temperature (`5`-`35`), and when you're in Eco mode
-you will set the Eco temperature (`5`-`21`), just like you were using
-the heater's own control panel. Bear this in mind when writing
-automations that change the operation mode and set a temperature at
-the same time: you must change the operation mode _before_ setting the
-new target temperature, otherwise you will set the current thermostat
-rather than the new one.
-
-When switching to Anti-freeze mode, the heater will set the current
-power level to `1` as if you had manually chosen it. When you switch
-back to other modes, you will no longer be in `Auto` and will have to
-set it again if this is what you wanted. This could be worked around
-in code however it would require storing state that may be cleared if
-HA is restarted and due to this unreliability it's probably best that
-you just factor it into your automations.
-
-When child lock is enabled, the heater's display will flash with the
-child lock symbol (`[]`) whenever you change something in HA. This can
-be confusing because it's the same behaviour as when you try to change
-something via the heater's own control panel and the change is
-rejected due to being locked, however rest assured that the changes
-_are_ taking effect.
-
-When setting the target temperature, different heaters have different
-behaviour, which you may need to compensate for.  From observation,
-GPPH heaters allow the temperature to reach 3 degrees higher than the
-set temperature before turning off, and 1 degree lower before turning
-on again.  Kogan Heaters on the other hand turn off when the
-temperature reaches 1 degree over the target in LOW mode, and turn on
-again 3 degrees below the target.  To make these heaters act the same
-in LOW power mode, you need to set the Kogan thermostat 2 degrees
-higher than the GPPH thermostat.  In HIGH power mode however, they
-seem to act the same as the GPPH heaters.
-
-The Inkbird thermostat switch does not seem to work for setting
-anything.  If you can figure out how to make setting temperatures and
-presets work, please leave feedback in Issue #19.
-
-## Fan issues
-
-Reportedly, Goldair fans can be a bit flaky. If they become
-unresponsive, give them about 60 seconds to wake up again.
-
-Anko fans mostly work, except setting the speed does not seem to
-work. If you can figure out how to set the speed through the Tuya
-protocol for these devices, please leave feedback on Issue #22.
-
-
-## Smart Switch issues
-
-It has been observed after a while that the current and
-power readings from the switch were returning 0 when there was clearly
-a load on the switch.  After unplugging and replugging, the switch
-started returning only dps 1 and 2 (switch status and timer). If
-HomeAssistant is restarted in that state, the switch detection would
-fail, however as Home Assistant was left running, it continued to work
-with no readings for the current, power and voltage.  I unplugged the
-switch overnight, and in the morning it was working correctly.
-
-Cumulative Energy readings seem to be reset whenever the reading is
-successfully sent to the server.  This leads to the energy usage never moving
-from the minimum reporting level of 0.1kWh, which isn't very useful.
-It may be possible to get useful readings by blocking the switch from accessing
-the internet, otherwise an integration sensor based on the Power sensor
-will need to be set up on the Home Assistant side, and the Energy sensor
-ignored.
-
-For the amount of consumed energy, it may be reasonable to use an additional
-helper - the [Riemann integral](https://www.home-assistant.io/integrations/integration/).
-Select `power` of switch as the sensor for it. The result of the integral will be
-calculated in `(k/M/G/T)W*h` and will correspond to the consumed energy.
-
-## Kogan Kettle issues
-
-Although these look like simple devices, their behaviour is not
-consistent so they are difficult to detect.  Sometimes they are
-misdetected as a simple switch, other times they only output the
-temperature sensor so are not detected at all.
-
-## Beca thermostat issues
-
-Some of these devices support switching between Celcius and Fahrenheit
-on the control panel, but do not provide any information over the Tuya
-local protocol about which units are selected.  Three configurations
-for BHP6000 are provided, `beca_bhp6000_thermostat_c` and
-`beca_bhp6000_thermostat_f`, which use Celsius and Fahrenheit
-respectively, and `beca_bhp6000_thermostat_mapped` for a buggy looking
-firmware which displays the temperature on the thermostat in Celsius
-in increments of half a degree, but uses a slightly offset Fahrenheit
-for the protocol, as detailed in issue #215.  Please select the appropriate
-config for the temperature units you use.  If you change the units on the
-device control panel, you will need to delete the device from Home Assistant
-and set it up again.
-
-## Saswell C16 thermostat issues
-
-These support configuration as either heating or cooling controllers, but
-only have one output.  The HVAC mode is provided as an indicator of which
-mode they are in, but are set to readonly so that you cannot accidentally
-switch the thermostat to the wrong mode from HA.
-
-
 ## Finding your device ID and local key
 
 ### Tuya IoT developer portal