• 9 Posts
  • 790 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle



  • just_another_person@lemmy.worldtoTechnology@lemmy.worldTired of Microsoft?
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    6 days ago

    It’s not really stable enough to be used for daily driving. That, and the driver support is whacky at best, so you’d need a very specific stack of hardware to even get it running. The OS in general is made to be binary compatible with Windows, but that doesn’t guarantee drivers actually work and can install due to a number of other factors.


  • Do you have a Zigbee bridge? Philips Hue things do work without the Hue App, but you probably have to add a manually entry for the device, and you need a Zigbee Bridge. Also, if I remember correctly, almost every device that isn’t a Hue bulb still shows up as a bulb for some reason. This is more due to the limitations of the Hue ecosystem than the HA implementation.

    If you just want a smart plug without all the corporate BS, get one that works on Matter (Zigbee or Z-Wave if you have an endpoint), and check the integration before buying. Moe’s is pretty solid, but there’s a ton of open devices out there that “just work” on HA.















  • It certainly looks like this device is either: a) not maintaining a stable broadcast in low power mode, b) missing some standard BLE information that is expected to be broadcast, or c) your machine has duplicate UUIDs for this device.

    It’s hard to discern without being at the machine, so as a jumping off point, I would look at the devices your machine thinks it’s already paired with: bluetoothctl devices

    Copy and paste that list, and note the device IDs. Wait for this event to happen again, then check the bluetoothctl command again and see if the same mouse has registered with different IDs. If so, either the mouse is broadcast different device info all the time (weird), or you have a collision in the registered devices that isn’t being overwritten on pairing (also weird).

    SO…I’d say a good starting point after this is to just nuke all the registered BT devices:bluetoothctl remove {deviceID}

    See if that kicks things back into working. Have you tried new batteries by chance? Some of these BLE devices act super wonky if they don’t have perfect voltages. Sometimes Alkaline Batteries are needed instead of Lithium rechargeables even. Sounds dumb, but check the manuals to see if it’s mentioned.