[RE-RELEASE] EcoWitt and Wittboy Weather Stations And Sensors (Local)

New Feature - Forwarding EcoWitt Custom Data Feed

I released another update, 1.34.11, adding the option to forward the data feed from the gateway on to another hub. An example use case could be wanting to utilise the built-in EcoWitt integration in Home Assistant, but being limited by the Gateway natively supporting only one custom data feed.

The driver updates introduce three new optional settings, Forward Address, Forward Port and Forward Path:

These can be left blank for most users, only populating these if you want to use this feature.

I have only tested this with Home Assistant, so if people have other scenarios and the code doesn't support them, let me know and I will consider expanded / adjusting the driver.

Note - The HA EcoWitt documentation talks about leaving out the first forward slash in the WS View App. I have not added it in, like they describe, so please include the forward slash at the beginning of the Forward Path setting if you are using this feature.

FYI - @Horseflesh

4 Likes

@sburke781 do you happen to know which template to use for the WH51 soil moisture sensors? I can't seem to find ne that works..

13 or 13B

oh, I didn't see those, is there a more detailed list? i was only finding 0,1,2,3,and 6 ( I believe).

Yeah, I keep meaning to update the template listing documentation... One day...

2 Likes

If I can ever figure out how to somehow follow, bookmark, follow, or save that in git hub I will, for now, though ill just book market here for future reference. I really need to figure out how to use GitHub better.

You should be able to just bookmark it in your browser, but either should be fine. I should just up date the documentation and you wouldn't need to worry

Yeah, when I get home I will (bookmark it), I just can't here. But I do need to learn git better, there are enough that references to it, I always feel like a long-tailed cat under a recliner chair when I try to do stuff on git.

The older I get, the more I email random stuff to myself to "bookmark" it for later.
Since I usually start searching for forgotten stuff in my email, it works great.... until I try to remember what the h*ll I called the thing I'm looking for in the email I sent to myself. :man_shrugging:

3 Likes

I used to have a draft email in my email box I did that with. Now there is a note for a similar purpose in Outlook. But its been a while since I actually did anything with it, hell I think forgot what half that stuff on there is for!

2 Likes

If possible, a Screen shot of each tile would be really helpful - it would save us the painful trial and error process.

If you really want to level up tho, get rid of this clunky system and make something more user-friendly.

eg A pick list for each category (but with descriptive names, not Alpha-Numeric codes):

Air: 2, 2A, 2B
Water: 5, 5B
UV: 7
Soil: 13, 13B
etc, etc :sunglasses:

But my favourite option would be to create Custom tiles for each sensor type. eg the Netamo style of a General Gauge, Wind Gauge, a Rain Gauge, UV / Solar radiation / Luminance Gauge, and an Indoor Gauge, but with the cool EcoWitt icons:

Screenshot 2023-08-18 at 4.22.05 pm

I find the composite ecowitt tiles hard to read as there is a real mishmash of info on most of the useful ones. eg

Screenshot 2023-10-23 at 10.47.58 am

1 Like

Yeah, that's what the markup template page has, I just need to sit down and add some of the additions that are not on there.

I'd start by saying I am conscious of spending too much time on tiles just for this driver. I was always a little on the fence with having tiles built in, as they were specific to the driver and not something that could be re-used. The other side of the same fence was that I liked that users had something built in and ready to go if they wanted it, without needing to find a different app just to build possibly a single tile. So I am comfortable with having built-in tiles, but don't want to speend too much time on it.

With that said, I don't think any of your suggestions are particularly complicated and most of them would, like you say, make the user experience easier.

I like the idea of the lists to replace needing to enter the codes. I will need to include (I think) 4 of them, as the current text field allows comma separated codes to create more than one tile. But that would still be fine. Behind the scenes I would still record them as a code, but present them with descriptive names when selecting.

That's essentially what each EcoWitt tile is trying to achieve... There are ones for Soil Moisture sensors, one's for the indoor ambient sensor, etc.

I think this can come down to a personal preference, some people would prefer words, some prefer the brevity of icons that, while they make take a bit of getting used to what means what, act as a short-hand.

Some of the tile templates are for the outdoor weather stations that can have up to 7 sensors and some additional calculations done by the driver, such as dew point and Summer Sizzle Index.

The original design for the template setting included both the pre-canned (code) option, e.g. 13, 13B, plus an option to enter the text manually that is included in the JSON file, so you could construct your own, but limitations in what could be recorded in a Preference Setting value meant the manual option would no longer work.

As much I don't like saying no, I feel like the text-based alternative tile layouts might be a step too far in terms of effort when there are other options available for constructing tiles. I don't disagree that there are likely more appealing designs people may want, but because it is such a personal and subjective thing, I am more inclined to improve what is in the EcoWitt drivers, but direct people elsewhere for that aspect if they want something significantly different in their tile layouts. Sorry...

1 Like

Dont worry, I know how much work goes into maintaining a driver - it's only been recently that the WU Driver I maintained has reached the stage where I would consider it "done".

I must be a bit dense tho, I went through all the options and these are the only ones I found that worked with my GW1100:

Indoor Unit:
Screenshot 2023-10-23 at 2.24.06 pm

Outdoor Unit:
Screenshot 2023-10-23 at 2.27.53 pm

and I'll leave off my Soil Sensors as they work quite well.

:man_shrugging:

It will depend on what weather station you have, more so than the gateway model. A couple if things could be throwing you, but I also need to actually look this up myself as well:

  • The icons won't display on the device page, they are made possible through the importing of a true-type font in a dashboard
  • If you were going by the list on the templates page in the EcoWitt repository, that list is incomplete, the json file I posted for Clay is the complete list (but I need to check this to see what else may or may not suit a weather station)

I'll take a quick look at the json file.

Out of interest, what sensor readings do you not see that you would have expected?

1 Like

10, 10A, 11, 15 and 15B might be worth a look. Like I said, I need to finish the documentation

I've got the GW1100 with most of the possible toys:

If we could replicate the above tiles, I'd be thrilled. :rofl:

PS, I really like the above logical structure - it's just really glanceable and logical.

Hmmm... Now you've got me thinking... Whilst not your previous suggestions around Netatmo tiles, match the EcoWitt tiles is a tempting feature.... Would make it consistent with the rest of the platform experience. Some may be more easily split into two, like the Rainfall, wind, pressure... and could be satisfied by some of the existing tile layouts.

Some of them would require your other suggestions around min/max readings, but I also like that idea.

I'll have think about it some more... But no promises on when....

3 Likes

Exactly, I only used my old Netatmo tiles as an example to show HE possibilities and the logical layout I had in mind.

Thanks mate, that's all I can ask.

2 Likes

I must be dense or something, but I've been trying to get two templates for my GW2000 so I can create 2 different tiles (due to the number of readings I get off the WS90, but under template, I've tried 1, 3 and 1,3, I get:

Current States

[truncated]

  • solarRadiation : 123.52
  • status : Invalid attribute or template for the current sensor
  • temperature : 14.1
    [truncated]

I've followed the setup instructions, and it works if I use either 1 or 3. Is this because I'm using the GW2000?

The ws90 foes not have one child device with all the attributes of 3. Check all the children. You will have to make separate for each child.