I have a Sony STR-DN1080 A/V receiver that I control via automations in HA, but each time I restart HA, the automations misbehave for a cycle. This has been going on for months if not years, but I relatively recently noticed that the coorelation between automations acting up and HA restarts. Given that, I was able to determine that was because the device powers on when HA restarts, and I planned to look into it eventually. Much more recently, eventually came around, and I tried to figure out why operating under the assumption that something goofy in one of my automations was causing the issue. However, that doesn’t appear to be the case. After my most recent HA restart, I verified that the device had turned on and reviewed all relevant automations to confirm they hadn’t run around the time of the reboot. Since they hadn’t, I proceeded to checke the logbook. Normally, when I look at the logbook for this device I will only see entries like “ turned off triggered by automation triggered by state of ” and “ turned off triggered by automation triggered by state of ” as expected. In this case, the last entry in the logbook before HA restarted was like the latter example above even though the device came on during the restart. Turning the device off manually lead to a logbook entry like “ turned off” even though the previous entry was already about it being turned off some time prior to the restart. Nobody was around the device during the restart and nothing else was involved to turn it on remotely. I don’t see anything in the SongPal integration documentation that would imply this is normal. II’d like to know if there are any other troubleshooting steps I should take and/or if this is something I should be taking to github (and if core is the correct repo for this type of issue).