Tydell

@cambriancatalystDid you ever solve this?
 
I think I solved mine. The syslog errors have gone away and I think bluetooth remains functional in my home assistant instance.
 
Looks like the syslog flooding was a bug in bluez that they remedied with 5.64.  The repos ich777 uses for un-get don't yet have anything above 5.63, but I found a slackware repository with 5.64 (there are higher versions than that, but didn't want to push my luck) and added it to the sources.list file for un-get. I then ran 'un-get update' then 'un-get upgrade' to upgrade bluez from 5.63 to 5.64 and restarted bluez. 
 
In detail:
Add this line to Flash/config/plugins/un-get/sources.list: https://slackware.uk/slackware/slackware64-15.0/patches/ patches
Terminal into Unraid & Run: 'un-get update' then 'un-get upgrade'
Force bluez/bluetoothd to stop: sudo pkill bluetoothd
Restart bluez: /etc/rc.d/rc.bluetooth start

alternatively, you can just delete the ssl certs from the flash drive (/boot/config/ssl/certs)...i did that and was able to get back in.  Not sure which is the preferred method, but just throwing it out there.