Skip to content
Home Assistant TestFlight
Sensors

LaCrosse

lacrosse

Built inLocal polling

The LaCrosse integration is using the data provided by a Jeelink USB dongle or this Arduino sketch.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
sensorSensor (humidity, temperature)

1 report below say how a device from this integration behaves in the Home app.

What people report

LaCrosse temperature sensors work through a JeeLink USB receiver. Some users could not scan sensor IDs.

  • Works3
  • Not working2
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Technoline TX 29 DTH-ITWorks LocalTemperature and humidity
Saved copy
Supported devices: Technoline TX 29 IT (temperature only); Technoline TX 29 DTH-IT (including humidity); TFA Dostmann LaCrosse sensors (type 30.3147.IT).

Excerpt saved from home-assistant.io on 2026-10-23.

Docs
Technoline TX 29 ITWorks LocalTemperature only, via JeeLink
Saved copy
Supported devices: Technoline TX 29 IT (temperature only); Technoline TX 29 DTH-IT (including humidity); TFA Dostmann LaCrosse sensors (type 30.3147.IT).

Excerpt saved from home-assistant.io on 2026-10-23.

Docs
TFA Dostmann LaCrosse 30.3147.ITWorks LocalListed in docs
Saved copy
Supported devices: Technoline TX 29 IT (temperature only); Technoline TX 29 DTH-IT (including humidity); TFA Dostmann LaCrosse sensors (type 30.3147.IT).

Excerpt saved from home-assistant.io on 2026-10-23.

Docs
JeeLink USB receiver LED controlNot working LocalLED on/off option not working; closed stale
Saved copy
The problem As I activated the lacrosse integration for my Docker Installation of Homeassistant, working with the Jeelink and the device is OK. But as mentioned here: https://www.home-assistant.io/integrations/lacrosse Turning ON/OFF the LED should work with the command: led boolean (Optional, default: false) That I integrated inside of my sensors.yaml like following: `platform: lacrosse #device: /dev/ttyUSB0 device: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AI03DAN7-if00-port0 baud: 57600 led: false` Using false oder true does not have any effect. ### What version of Home Assistant Core has …

Excerpt saved from GitHub on 2026-10-23.

Issue #134578 · 2025-01
LaCrosse humidity sensorNot workingBroken in Home
Humidity sensor sends no data to HomeKit
Missing humidity device_class so HomeKit gets no value
Saved copy
The problem LaCrosse does not add `device_class: humidity` to humidity entity. Seems to be related to sensor.py: line 207-212 [code] In comparison with temperatur, device_class is defined: [code] As a result the entity does not send any data to HomeKit, because the device_class is missing. ### What version of Home Assistant Core has the issue? core-2023.5.2 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue LaCrosse ### Link to integration documentation on our website …

Excerpt saved from GitHub on 2026-10-23.

Issue #93007 · 2023-05

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Details

Installs (analytics)96 (0.01%)
Quality scaleLegacy
Added inHome Assistant 0.58
Set up in the UINo, YAML

Devices listed in its documentation

  • Technoline TX 29 IT (temperature only)
  • Technoline TX 29 DTH-IT (including humidity)
  • TFA Dostmann LaCrosse sensors (type 30.3147.IT)

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.