Closed criticallimit closed 1 year ago
Well, this sometimes happens in my tests too with a very stable configuration: i.e. I'm sure the device key is correct but still the hash verify algorithm fails. I'm considering this as a bug in the device firmware which sometimes produces invalid hashes itself (of course this is only a 'friendly' and easy explanation) but since it doesnt happen very often I tend to disregard this as a 'random' glitch and so it should be no real issue. I could nevertheless try to log better context informations so to eventually have the raw values leading to the hashing failure and eventually dig more onto it..
thanx for your reply and explanation. So I ignore these messages in the log and don´t care. It´s working good so far.
Just another Warning in HA which is coming at start and sometimes during normal opertion:
System is on actual Versions (HA and Meross)