Change platform to AHT20

[pactarus]

I have bought a PLT-1B and after the first boot it gave me the following problem:

[15:42:53][C][internal_temperature:125]: Internal Temperature Sensor 'ESP Temperature'
[15:42:53][C][internal_temperature:125]:   Device Class: 'temperature'
[15:42:53][C][internal_temperature:125]:   State Class: 'measurement'
[15:42:53][C][internal_temperature:125]:   Unit of Measurement: '°C'
[15:42:53][C][internal_temperature:125]:   Accuracy Decimals: 1
[15:42:53][C][dallas.temp.sensor:029]: Dallas Temperature Sensor:
[15:42:53][C][dallas.temp.sensor:034]:   Address: 0xa500000ff66ab128 (DS18B20)
[15:42:53][C][dallas.temp.sensor:035]:   Resolution: 12 bits
[15:42:53][C][dallas.temp.sensor:036]:   Update Interval: 60.0s
[15:42:53][C][aht10:162]: AHT10:
[15:42:53][C][aht10:163]:   Address: 0x38
[15:42:53][E][aht10:165]: Communication with AHT10 failed!
[15:42:53][C][aht10:167]:   Temperature 'Air Temperature'
[15:42:53][C][aht10:167]:     Device Class: 'temperature'
[15:42:53][C][aht10:167]:     State Class: 'measurement'
[15:42:53][C][aht10:167]:     Unit of Measurement: '°C'
[15:42:53][C][aht10:167]:     Accuracy Decimals: 2
[15:42:53][C][aht10:168]:   Humidity 'Air Humidity'
[15:42:53][C][aht10:168]:     Device Class: 'humidity'
[15:42:53][C][aht10:168]:     State Class: 'measurement'
[15:42:53][C][aht10:168]:     Unit of Measurement: '%'
[15:42:53][C][aht10:168]:     Accuracy Decimals: 2
[15:42:53][E][component:082]:   Component aht10.sensor is marked FAILED

I've tried to factory reset it but the ambient temperature only works for 10 minutes and than stops giving only the error I've mentioned before.
After a bit of research I came across this HA forum post. I think a solution would be to change this line of code to

  - platform: aht20

[TrevorSchirmer]

Thank you! We've heard one other user with this problem but I didn't track it down yet. Odd we aren't seeing more, I'll get it tested and will follow up!

[pactarus]

Yes, I am the user you are referring to :).
I figured out that this issue only occurs in forced awake mode.
I have since disabled it in the settings (as it also significantly drains the battery) and now it works perfectly without any errors.
That being said, I would recommend checking out that Home Assistant forum; I think the problem they are discussing might be the same one I experienced.