Home Assistant Community

Hoping to correctly implement component for lacrossealertsmobile.com

#1

Hello!

In May of last year I spent some time making a custom component for a cheap but extremely effective device for getting the temperature of my hot tub. For around $30, this accomplished exactly what I wanted and I was very excited to get the data into Home Assistant. La Crosse Technology 926-25106-WGB Wireless Monitor System Set w/Wet Probe

My source can be found on my GitHub here: https://github.com/Legomaniac/hass_lacrosse_alerts_mobile/blob/master/lacrosse_alerts_mobile.py

It was quite bodged and hacked together, but it worked! I knew some of the techniques I used weren’t right, so I disabled it in my configurations.yaml and told myself I would get back to it.

Well, life happened and Home Assistant got neglected. However, I’ve recently been spending some time getting Home Assistant updated to the latest version, Fedora fully up to date, etc. and I’m really interested in getting this to work again.

I uncommented the following section of my config, and unfortunately it doesn’t seem to work anymore.

sensor:
  - platform: lacrosse_alerts_mobile
    user: !secret lacrosse_username
    pass: !secret lacrosse_password

The only error I seem to get is the following:

2019-02-09 19:09:53 WARNING (MainThread) [homeassistant.loader] You are using a custom component for sensor.lacrosse_alerts_mobile which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

I just ran the following and verified that the code that interacts with lacrossealertsmobile.com still works, so whatever is wrong with my code is the portion that interacts with Home Assistant, not the portion that queries the website.

(homeassistant) [[email protected] sensor]$ pwd
/home/homeassistant/.homeassistant/custom_components/sensor
(homeassistant) [[email protected] sensor]$ python
Python 3.7.2 (default, Jan 16 2019, 19:49:22)
[GCC 8.2.1 20181215 (Red Hat 8.2.1-6)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from lacrosse_alerts_mobile import LaCrosse
>>> import re
>>> import json
>>> mySensor = LaCrosse("***my_user***", "***mypass***")
>>> sessionKey = mySensor.getSessionKey()
>>> webPage = mySensor.getWebPage(sessionKey)
>>> match = re.findall('^userGatewaysList.* ({.*})', webPage.text, flags=re.MULTILINE)
>>> onlyData = json.loads(match[0])
>>> onlyData['device0']['obs'][0]['humidity']
'64'
>>> onlyData['device0']['obs'][0]['probe_temp']
'101.8'
>>> onlyData['device0']['obs'][0]['ambient_temp']
'-2.5'
>>> exit()

My end goal is to create a component that is worthy of being included on the Home Assistant website, however for the time being it would be nice just to get the custom component working again. I’m hoping there is someone with experience creating Home Assistant components that can set me off in the right direction.

Hoping to hear from you all soon,

James

#2

Short update,

I was able to get the values back in my Home Assistant interface by clicking the menu button in the upper right of the interface and selecting “Configure UI” then choosing “Raw Config Editor” and adding them as follows:

title: Digihouse
views:
  - badges:
      - sensor.entryway_thermostat_temperature
      - sensor.entryway_thermostat_humidity
      - sensor.outside_ambient
      - sensor.outside_probe
      - sensor.outside_humidity

So apparently, the groups.yaml file doesn’t populate the interface anymore. Looks like I have some catching up to do.

Anyway, I now have this “working” but I’m sure nowhere near the standards needed to get this to be a listed component on the website.

Any direction on what to do next would be greatly appreciated!

Thanks,

James

#3

Thank you for your work on this! I was hoping for a way to use this sensor in Home Assistant. My first thought was to find an RF bridge that works with the sensor and pull the data straight into HA. I still may try that, but this will be great in the interim. I would be happy to help with any testing of this component.

#4

Hey @Hassiopeia, I’ve changed quite a bit about how the custom component works since this thread, and I’m now looking for some assistance / direction over in this thread:

If you want to comment there showing your support, hopefully it could get more visibility and maybe a little traction. Thanks!!