Ecowitt2mqtt: Send data from an Ecowitt device to MQTT

Share your Projects!
37

Your error says ValueError: Invalid host. – sounds like ecowitt2mqtt can’t reach your HASS machine.

38

Thanks Aaron,

Thats kind of what I thought.

I tried different IP address ( that of the HA VM - .171, and that of the host QNAP - .165, ) with no success.

Do I need to add the MQTT broker IP, U/N and P/W at all?

Thanks again.

Jarrod.

39

Correct, ecowitt2mqtt talks to your MQTT broker, so you will need to provide its IP/user/pass.

40

Thansk again Aaron,

so one last question if I may - where do I enter the broker credentails? - my MQTT broker is external to HA, running in a docker containmer on the NAS. - and therefore not ( I dont think ) on the HA auto discovery. - Is this a mandatory ( MQTT Discovery ) for Ecowitt2Mqtt?

Thanks,

Jarrod.

41

It looks like the author of the HA add-on needs to update his code to be able to input MQTT credentials; I recommend creating an issue in that repo: https://github.com/smarthall/hassio-addons/issues

42

Hi Aaron,

Thanks for your help I’ll head on over and do that.

Great work BTW, - this add on got me over the line with the purchase of the Ecowitt Gw1000 and associated sensors. - Until now I wasnt sure which hardware and how I was going to integrate.

I’ll upload some pics of the card and the sensors in situ when this is working. - Hopefully the ‘Author of the code’ can sit back and appreciate the how he has helped others…

If you have nothing better to do for 5 minutes, read here

specifically the content of Para 7… THACF…

J.

2 Likes
43

The addon now allows manual configuration of the MQTT Broker details ( IP, port, user. P/W) directly for situations where the MQTT broker is separate to the HA node.

Tested and works.

Thanks to the Coder…

J

1 Like
44

Excellent! Glad everything is in action and you’re enjoying it.

45

Hi,

I try to run ecowitt2mqtt into a container using portainer.
Running the container stops with error “Missing required environment variable: either MQTT_TOPIC or HASS_DISCOVERY”
If I add those variables it deletes them strangely enough and starting all over with the same error.

Anybody any suggestions what I am doing wrong?

Regards

46

I don’t use Portainer, but have you tried this? https://www.reddit.com/r/docker/comments/gy53r7/how_to_edit_environment_variables_in_portainer/

47

This one broken again? Upon clicking install it just spins the circle then never installs

48

I don’t know which “this” you’re referring to – ecowitt2mqtt or the hass.io add-on?

49

sorry, hass.io addon :slight_smile:

50

I see you already posted an issue in that repo. :+1:t2:

1 Like
51

Released 1.1.0 today. Marquee features:

  • Better detection of device classes in HASS (i.e., temperature sensors will show up as temperature sensors – icons, etc. – automatically)
  • Support for “binary batteries” (batteries that are either “OK” or “Low”)
  • Support for the HASS device registry
1 Like
52

I am so happy that you have made the effort to make this accessible to people and simplify the installation process for less technical like myself. Congrats!

I have my Ecowitt2mqtt running and data is flowing through fine but there is no preceding name to the sensors.

I have a question which probably shows my lack of knowledge:
My mqtt message is as follows and as a result my sensors are all over the place and do not have ecowitt2mqtt in the topic to allow them to be found easily.
How would I go about adding this so that for example in Developer Tools:
sensor.monthlyrain becomes:
sensor.ecowitt2mqtt_monthlyrain

Any help appreciated.

homeassistant/sensor/F6F882B3BA6EF58E2916363883A01CE5/tempin/config at 2:29 PM:
{
“availability_topic”: “homeassistant/sensor/F6F882B3BA6EF58E2916363883A01CE5/tempin/availability”,
“icon”: “mdi:thermometer”,
“name”: “tempin”,
“qos”: 1,
“state_topic”: “homeassistant/sensor/F6F882B3BA6EF58E2916363883A01CE5/tempin/state”,
“unique_id”: “F6F882B3BA6EF58E2916363883A01CE5_tempin”,
“unit_of_measurement”: “°C”
}

53
54

Thank you for doing this and sharing. The other custom component I was using stopped working. I just followed the instructions to add your repository, and set it up quickly, without issues.

1 Like
55

Thanks all for the nice work.
However…I am still not able to get it working on my system.
I prefer the methode of using the add-on “GitHub - smarthall/hassio-addons: Addons for Hassio that I've made/modified” but each time I try to use the link my system give : invalid repository.

Anybody had the same?
Solution?

Thanks

Herbert

56

Hello,

I can’t get this to work and I feel like I missing something obvious?

I tried to install docker in Unraid using this:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='ecowitt2mqtt' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'MQTT_USERNAME'='ha' -e 'MQTT_BROKER'='192.168.1.9' -e 'MQTT_PASSWORD'='password' -e 'HASS_DISCOVERY'='true' -p '8080:8080/tcp' 'bachya/ecowitt2mqtt'`

I have also tried to install using portainer using both of these options:

docker run --name ecowit -e MQTT_BROKER=192.168.1.9 -e MQTT_USERNAME=ha -e MQTT_PASSWORD=password -p 8080:8080 -e HASS_DISCOVERY=true bachya/ecowitt2mqtt:latest

docker run --name ecowit -e MQTT_BROKER=192.168.1.9 -e MQTT_USERNAME=ha -e MQTT_PASSWORD=password -p 8080:8080 -e MQTT_TOPIC=ecowitt bachya/ecowitt2mqtt:latest

The docker does start, but if I check logs it’s always empty, and running MQTT Explorer shows no topic being created or data being sent. I know that my broker IP/port, username/password are correct because I have them configured for bunch of other stuff.

Any ideas?