MQTT support

[syyyr]

Hello, I was wondering if MQTT support (and possibly Home Assistant MQTT discovery support) could be added. I am currently scraping the HTTP server, but it does get kind of brittle (especially since my mouse switches between two different devices IDs). With MQTT, LGSTray could send the data immediately when available instead of waiting for the data to be polled from the HTTP endpoint.

[darmach]

Hi @syyyr check out #132 - if your only problem is ID changing, I would advise to scrape using device name instead. Example of my scrape:

scrape:
### Logitech Devices
# Scrape with device name instead of ID as it might change
# Discover your devices on http://address:12222/
  - resource: "http://address:12222/device/G515%20LIGHTSPEED%20TKL%20Gaming%20Keyboard"
    # Scan never - trigger entity update with automation triggering
    # only when PC is on - checked by power usage on intelligent socket
    scan_interval: 60000000
    sensor:
      # Battery Level
      - name: Logitech G515 Battery
        unique_id: logitech_g515_battery
        icon: mdi:battery
        select: "battery_percent"
        device_class: battery
        unit_of_measurement: "%"
        value_template: >-
          {% if value | is_number %}
            {{ value | float | int }}
          {% else %}
            {{ states('sensor.logitech_g515_battery') }}
          {% endif %}
      # Charging Status - raw data to template binary_sensor with
      # as scrape integration does not seep to support binary sensors
      - name: Logitech G515 Charging Raw
        unique_id: logitech_g515_charging_raw
        select: "charging"
        # Just grab the raw "True" or "False" string
        value_template: "{{ value }}"

[syyyr]

Hi, @darmach, the problem is not the device that's changing, it's just that at all times, I have these two devices:

<xml>
<device_id>dev00000000</device_id>
<device_name>Pro Wireless Mouse</device_name>
<device_type>Mouse</device_type>
<battery_percent>50.00</battery_percent>
<battery_voltage>0.00</battery_voltage>
<mileage>31.99</mileage>
<charging>False</charging>
<last_update>12/14/2025 22:06:44 +01:00</last_update>
</xml>

and

<xml>
<device_id>81AA2BD0-4079C08800</device_id>
<device_name>G Pro Wireless Gaming Mouse</device_name>
<device_type>Mouse</device_type>
<battery_percent>50.00</battery_percent>
<battery_voltage>3.81</battery_voltage>
<mileage>-1.00</mileage>
<charging>False</charging>
<last_update>12/14/2025 22:06:43 +01:00</last_update>
</xml>

And LGSTrayBattery seems to update these on random (ofc this is probably not LGSTrayBattery's fault), so it's not about the IDs changing (it's always these two IDs), it's about the fact that there are always two devices, and only one of them has the current info.

[darmach]

@syyyr have you tried disabling one of the polling methods in the toml config already?

[syyyr]

I have not... But it seems to me that sometimes one of the devices (I guess polling methods?) has outdated info. I remember that at first I only configured the scrapes for one of the devices, and at some point I saw -1 % battery (or maybe 0) for the one configured device, and the other (that I have configured at that point) had up-to-date info. So right now, my setup has both of the devices configured, and whichever gives me an update first will be the one that's active in the "cached" variant of the sensor. I think I generally have it figured out right now, so no big deal, but there's a lot of code now.

I suppose this problem wouldn't really be solved by MQTT though.