WXforum.net
Weather Station Hardware => Ambient Weather and Ecowitt and other Fine Offset clones => Topic started by: cheeroip on September 05, 2022, 01:06:52 PM
-
EDIT Refresh coming before 2023
----------------------------------------
I just deployed a new implementation of a dashboard for the Ecowitt TCP protocol
The application is available in the Windows store (windows 10 and 11)
15 days trial
https://www.microsoft.com/store/apps/9NFHW253XQ91
ms-windows-store://pdp/?productid=9NFHW253XQ91
[ You are not allowed to view attachments ]
Supported Devices:
Ecowitt GW2000
Ecowitt GW1100
Ecowitt GW1000
https://shop.ecowitt.com/collections/lan-wifi-gateway
http://www.foshk.com/Wifi_Weather_Station/WH2650.html
Fine Offset WH2650
***note to whoever already purchased the GW1000 version:
https://apps.microsoft.com/store/detail/gw1000/9MWXH1RGGWJB?hl=en-us&gl=us
I'll soon update the GW1000 application to match the improvement or send me a message here and I'll generate some promocode for the GW 1100.
-
in 0.96 (almost) all earlier display errors are removed [tup]
except for the missing WH55 (Leak) Channel 2 which is not showing in the interface.
It's contained in the API response:
#define ITEM_LEAK_CH2 0x59//for Leak_ch2 value 0x00 = OK, 0x01 = Alarm
see below (flag red, value green)
...
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0x94 0x01 0x00 0xE4
0x06 0x43 0x08 0x26 0x96 0x09 0x27 0xB9
0x02 0x00 0xCA 0x07 0x57 0x0A 0x00 0x8C
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x05 0xBF 0x18 0x16 0x02 0x1C 0x17 0x02
0x2A 0x00 0xA0 0x4D 0x00 0x46 0x51 0x01
0xB8 0x4E 0x00 0x90 0x2C 0x31 0x2E 0x3D
0x30 0x36 0x32 0x2E 0x1A 0x00 0xD8 0x22
0x4F 0x1B 0x00 0xC3 0x23 0x54 0x1C 0x00
0xDA 0x24 0x4A 0x1D 0x00 0xB8 0x25 0x5D
0x1E 0xFF 0x43 0x1F 0x00 0xE8 0x27 0x3D
0x20 0x00 0x42 0x28 0x37 0x59 0x00 0x62
0x00 0x00 0x00 0x07 0x61 0x63 0x16 0x98
0xB9 0x60 0x1F 0x19 0x00 0x39 0x0E 0x00
0x00 0x10 0x00 0x31 0x11 0x00 0x33 0x12
0x00 0x00 0x00 0x73 0x13 0x00 0x00 0x13
0x31 0x0D 0x00 0x31 0x70 0x00 0xFF 0x36
0x00 0x47 0x00 0x19 0x00 0x47 0x00 0x16
0x01 0x64 0x01 0x60 0x06 0x16
-
Thanks for the troubleshooting.
Sadly the application had zero traction and interest.
I will probably do a release before the end of the year just to refresh a bit the thing while waiting for Microsoft to implement some kind of ads platform that would support store apps.
The application is even featured on the Ecowitt support page of the product:
https://www.ecowitt.com/shop/goodsDetail/16
but it's impossible to link directly to the page and I think they do a terrible job at explaining what the product is and how people could use it :?
-
Hello
Application to have on your pc to have the main info. I like it [tup]
-
Thanks! I was thinking about creating multiple smaller more focused apps for specific use case.
Leaks app.
Air quality app.
Thermostat app.
But they would have even less market impact without Ecowitt or the community showing any interest so why bother :grin:
-
I think, there are so many alternative ways to do this, the boat has kind of sailed on developing something for mass appeal. For personal appeal sure.
You have the web sites, the phone apps.
I even run WSView on my windows pc via the phone link to my android phone
But, if something truly different, I guess there is always room. I wrote my own stuff to log to a SQL Database and provide data for my other applications and websites
-
Thanks for the troubleshooting.
Sadly the application had zero traction and interest.
I will probably do a release before the end of the year just to refresh a bit the thing while waiting for Microsoft to implement some kind of ads platform that would support store apps.
The application is even featured on the Ecowitt support page of the product:
https://www.ecowitt.com/shop/goodsDetail/16
but it's impossible to link directly to the page and I think they do a terrible job at explaining what the product is and how people could use it :?
I think once you enable it to show all nowadays available EW sensors properly including the synoptical display of the WS90 (piezo) rain and a 2nd connected classical rain gauge, be it on one page, be it on several pages via tabs, it could find more interested users.
Either with a similar layout (from the tab assignment) as the WS View app or with a different composition. And also giving it some window sizing feature (zoom in/zoom out). For the Windows platform I don't know any other simply to install app or program which could compete with your app (once completed :-)).
Alternatively one needs to install Meteobridge with a template or CumulusMX which needs more space, knowledge and attention and is already a data logging program or use WS View Plus on a Windows computer with e.g. Samsung DEX with the Android phone connected or in an Android emulator like NOX.
But it's difficult to recommend and promote a "half-ready" piece of software to a wider community beyond the "nerds".
I personally like and use it. [tup]
-
I think, there are so many alternative ways to do this, the boat has kind of sailed on developing something for mass appeal. For personal appeal sure.
You have the web sites, the phone apps.
I even run WSView on my windows pc via the phone link to my android phone
But, if something truly different, I guess there is always room. I wrote my own stuff to log to a SQL Database and provide data for my other applications and websites
Ahaha, nope, the ship didn't even left the shipyard.
There is no alternative simple desktop solution that read data directly from the gateway.
Plus big numbers and friendly graphics.
Just think of it like an alternative console, a widget, not like an application to get nerdy numbers.
The WSView app (terrible name btw) is ugly and nerdy, (a separate tab for the extra sensors? really?) no indication if a single sensor is not functioning, how do you copy and paste the data from there?
Your comments make it look like it is something useless that doesn't add anything to the user experience.
Did you even try it? :grin:
Also there is no way for Ambient weather stations to read their data without going trough the web login/user or downloading the mobile app + user/password.
Every weather stations should have a free simple desktop application that read data directly from their console and ideally integrate directly with their web service for the history stuff.
It would be a huge selling point and a precious troubleshooting tool for advance user.
But nope: they hide the link like something they are ashamed to offer lol.
-
I get it, I was just working off the lack of interest mentioned.
I also am a programmer, a lot on doze. Sorry, I did not try your app, and maybe I should, but I personally don't have a need as there are alternatives I am OK with.
That being said, please don't take my response as being offensive, as it was not meant to be.
-
But it's difficult to recommend and promote a "half-ready" piece of software to a wider community beyond the "nerds".
I personally like and use it. [tup]
[/quote]
wow, half-ready? Is that is your impression you get from the app?
Beside that it's not that the "nerds" or the actual weather stations company see any value in the application anyway.
I contacted Ambient Weather and Ecowitt and somebody working there considered the apps good enough to link the apps on their website but I doubt any big wig there even noticed it.
So sure, thanks for the support and for implying that the app is half baked and buggy :lol:
-
I get it, I was just working off the lack of interest mentioned.
I also am a programmer, a lot on doze. Sorry, I did not try your app, and maybe I should, but I personally don't have a need as there are alternatives I am OK with.
That being said, please don't take my response as being offensive, as it was not meant to be.
Not offended. You're an expert and people that read this thread probably trust your opinion.
It's a public forum and you just dismissed my work without even installing the application suggesting to not even bothering try it out.
There is a free trial of 15 days, it doesn't need any special knowledge, no need to install Linux, no need to install any extra software or library or create any account, no ads and no privacy tricks.
I don't believe as principle in free software. There is always a price to pay and I really prefer to be upfront about it instead of hiding behind shady practices or annoying ads.
I really believe that $2 is REALLY way too cheap and every serious developer should be outraged to see something like that offered for so low even if that was just a skin slapped on a service. (it isn't).
It's always a shame to see how developers always like to boycott each other.
I get it, the whole imposter syndrome and trying to protect their little garden or inflated ego that believe that everybody else is a complete idiot.
-
I understand, I also work in a paid software environment , and paid well to do so , completely unrelated to this.
I will take the time, to try out your app, but because I am also busy with other endeavors might take a while.
I am no expert with this, I try to stay humble, works better for my sanity that way.
Feel free to contact me in PM if needed
-
As said earlier - I like and use it - even though it doesn't yet show all sensors that already have a place in the interface (e.g. water leakage) and quite a bunch is still missing (WH45, WS90 piezo rain and synoptical view, WN34, WN35).
So the ship still needs some construction to be completed before leaving the harbour.
I understand Ecowitt as your app isn't working completely yet - in the sense showing all available sensors.
It would not enhance their credibility to promote a still "half-baked" app.
But as also said earlier - make it working with all sensors with whatever design to start with (with tabs, without tabs - with tabs you can easily switch views, everything on one page is considered cumbersome by many users to have to page down - and it's the users who will go for your app or not at the end of the day) - and then Ecowitt will most likely change their promotion policy.
-
OK, I installed it , needs a bit of work, sorry, I'm going to start with the simplest on configuration, I'll get into the rest later. Don't take this the wrong way, but you have to work with a lower common denominator as far as those that may use this, it is a something as a techie I still struggle with , just because it is obvious to me, well, not so much for the GP
- IP configuration of device, mask the field or explain xxx.xxx.xxx.xxx
- Discover needs more explanation, although it kind of works
- In the case of multiple devices (I have 6) , list them for selection, it just picked the first one it found , no chance of selecting another , assume most are using DHCP and have no idea on IP of the unit
-After you are OK with that setup, needs an accept or save for the end user to understand, I see it took it, but feedback is good
-You need doc, or hovers etc to assist
-Few Typos , nothing serious
-Pictures/text of only the GW1100 will mislead, if you intend to support other consoles
That is as far as I am going to go for right now
-
I Frankly don't know what you have to do to put an app on the site , but you should mark this is an Alpha or Beta. It is nothing ready to charge money for, of course that is just my opinion. Please don't take offense, but I have seen so much stuff like this just brought forward on various platforms like it is ready to go, and the end user expects it will be , so charging for it , not yet. if your development is based on recurring revenue from your initial push out , this can go against you in a negative way.
But those are just , my opinions
-
I gave the free trial a go..
Lightning is showing the last strike to be 32 miles, but that's wrong, it is 12.9 miles (20km) 20 miles would be 32km. The value from my GW1100 is already in miles.
No WN34 data either.
-
I also tried the free trial. My yearly rain is in inches and multiplied by 10. I have no PM sensors (and none that appear in WSView or WSView Plus) yet the GW1100 app shows a 03 PM2.5 sensor with hazardous levels. Before I finished typing this, now there's a 02 PM2.5 sensor with the same 2560 hazardous level. The lightnings section also doesn't show the date, just the time.
While the app looks organized nicely, it's just not for me. I wouldn't use entire sections of the display and the sensors are just numbered. Being able to rearrange and customize the display would make it a lot nicer. But I realize I'm picky and I have created my own web page and infrastructure so I can see my data wherever I want, however I want.
-
I gave the free trial a go..
Lightning is showing the last strike to be 32 miles, but that's wrong, it is 12.9 miles (20km) 20 miles would be 32km. The value from my GW1100 is already in miles.
No WN34 data either.
Thanks for give it a go.
Gyvate already pointed out that problem in here. He is very thorough with his troubleshooting.
I would not push things as much as saying those problems are my "brown m&m's" but I do use them to have an idea of how many people actually use a feature and how much credit I give to the userbase :).
There are few other "bugs" in the app have been completely ignored for now.
Is this the right strategy to deploy and support an application? Hell no, but it's not that an ultra-niche $2 app would make any difference to anybody.
I like the idea to "donate" my work to people that can appreciate the effort.
Ideally I would have hope to have somebody working at Ecowitt to just test all their damn sensors or offer to send me a full set for testing...
but hey: who need another developer working for them for free right?
Send me a to message if you need promocodes to keep the app(s) for free and if you're interested in any of the other apps available in the store.
I will eventually deploy a new version if I notice the numbers going up a bit.
-
I also tried the free trial. My yearly rain is in inches and multiplied by 10. I have no PM sensors (and none that appear in WSView or WSView Plus) yet the GW1100 app shows a 03 PM2.5 sensor with hazardous levels. Before I finished typing this, now there's a 02 PM2.5 sensor with the same 2560 hazardous level. The lightnings section also doesn't show the date, just the time.
While the app looks organized nicely, it's just not for me. I wouldn't use entire sections of the display and the sensors are just numbered. Being able to rearrange and customize the display would make it a lot nicer. But I realize I'm picky and I have created my own web page and infrastructure so I can see my data wherever I want, however I want.
Excellent, thanks.
Yes, I hate that multiplier! :)
I think some stations/gateway call that field "yearly" and other "total" so I always get annoyed every time I think about it. I'll eventually fix that.
I have no idea how those lightnings sensors works since I don't own any. and I m late for grilling.
Family is going to yell.
later for updates
-
yet the GW1100 app shows a 03 PM2.5 sensor with hazardous levels
as long as you go by what @cheeroip is writing in his interface .... :roll:
I have already suggested that he use the EPA scale and thresholds for describing the air quality.
His scale (if any) used is completely unrealistic
see example attached
I guess a correction will/could/should be part of his next update ...
showing non existing sensors could be the result of not having non-existing or intentionally not connected sensors actively disabled !
-
yes, I just don't have those sensors, annoying to troubleshoot and I have no idea how popular those things are.
Ecowitt could push a lot more those air quality sensors and suggest people to install them in every bedroom/kitchen/living room and tapping the whole lifestyle market now that a bunch of companies sell those cheap air filters.
So far I had zero requests about that feature and Ecowitt doesn't even explain that the gateways can be used with those sensors and that people could read all their sensor data on the pc or web.
I will eventually buy one of those thing at some point and I could cross data with the Dyson's numbers or see if frying meatballs could trigger some spikes :)
I would have REALLY like it if somebody at Ecowitt would have test the thing at least once and remove it from their product page unless I would fix it. But if they are happy, I'm happy.
It's not that I can teach or tell anybody how to run their business.
Maybe they are afraid of pissing off Ambient Weather people.
I should really try to push harder on Ambient Weather compability next version since the Ambient Weather apps tend to perform way better.
Ideally I should refresh those apps too and suggest people to buy a GW1000 but I would really start feeling I would be working way too hard for a company that didn't even open the app once lol.
-
as long as you go by what @cheeroip is writing in his interface .... :roll:
I have already suggested that he use the EPA scale and thresholds for describing the air quality.
His scale (if any) used is completely unrealistic
I think to I found those values somewhere in some official gov websites (If I remember correctly there were HUGE differences in what US, Europe and Asia consider harmful lol. It's an old trick of every government, if you don't have the money or willing to fix something just change the parameters.
In any case I had fun creating he pretty colored interface but annoyed that I couldn't test it.
If only the app had any visibility I would have spin off the AIRquallity function in a complete separated application specifically targeting airquality. Same with water leaks. People concerne about waterleak dont necessarily overlap with weathernerds and those 2 things MUST have an offline reliable access.
-
Welcome to the conundrum .
Just look at all the work Gyvate has put in to the matrix of different combinations at https://www.wxforum.net/index.php?topic=40730.0
I applaud your effort, but look at the actual breadth and width of the effort.
But, as I know from my own efforts on various projects, some things just can't be denied in the pursuit until you experience them. And for some they come up with something we haven't thought about. I do wish you luck, and hopefully minimal frustration.
I run both Ecowitt and Ambient stuff, and , if needed, can test your product (Based on available time, I do work for a living).
Rover
-
1. the awnet app is as far as I know not made by Ambient but also by Fine Offset / Ecowitt - but with the ambientweather.net and customized ambient protocol upload facility.
It behaves with the Ambient consoles like with the other consoles only reading the WiFi firmware
2. only from the new Ambient ObserverIP 2.0 (or FineOffset WH2682) data can be read either via the WebUI or via port 45000 as does the WS View Plus app.
There is no application beyond WS View Plus or the OberserverIP 2.0 (WH2682) console/gateway WebUI which can read the live data
That's for Ambient ...
Your app should be able to read from a WH2682 (to be verified by a ObserverIP2.0 user)
For the remaining sensors I can provide you with all sensors except for the WN34. The API response in your app shows all the sensors with their identifier ==> you can do the necessary programming and you can send me an updated for test purposes. Happy to do so as I already did before. The Ecowitt decoding of the API is available at Ecowitt.net/Ecowitt.com - if needed I can provide a translation of an actual API response marking all the bytes which represent sensor values respectively their markers/identifiers in the API response.
10:42:40 pm [ LIVEDATA ]
INTERRUPTED
...
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0x96 0x01 0x00 0xC8
0x06 0x39 0x08 0x26 0xE0 0x09 0x28 0x03
0x02 0x00 0x44 0x07 0x59 0x0A 0x00 0x77
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0x00 0x00 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x78 0x4D 0x00 0xAF 0x51 0x00
0x82 0x4E 0x00 0x7D 0x2C 0x41 0x2E 0x40
0x30 0x3E 0x32 0x2B 0x1A 0x00 0x40 0x22
0x4C 0x1B 0x00 0x5A 0x23 0x52 0x1C 0x00
0x43 0x24 0x58 0x1D 0x00 0x5B 0x25 0x4F
0x1E 0xFF 0x54 0x1F 0x00 0x57 0x27 0x45
0x20 0x00 0x39 0x28 0x4B 0x59 0x00 0x62
0x00 0x00 0x00 0x00 0x61 0x63 0x22 0x26
0x5E 0x60 0x11 0x19 0x00 0x0C 0x0E 0x00
0x00 0x10 0x00 0x00 0x11 0x00 0x02 0x12
0x00 0x00 0x01 0xDB 0x13 0x00 0x00 0x1A
0x23 0x0D 0x00 0x00 0x70 0x00 0xD3 0x34
0x00 0x61 0x00 0x9D 0x00 0x55 0x00 0x96
0x02 0xB1 0x02 0xFF 0x06 0x72 0x00 0xC4
header: FF, FF, CMD, length from CMD to end including checksum
marker: observation/sensor Hex value from API
0x01: inTemp 00C8 = 20.0 °C
0x06: inHum = 39 = 57%
0x08: absPress = 26E0 = 995.2 hPa
0x09: relPress = 2803 = 1024.3 hPa
0x02: outTemp = 0044 = 6.8 °C
0x07: outHum = 59 = 89%
0x0A: WindDir = 0077 = 119°
0x0B: WindSpeed 0000 = 0 m/s
0x0C: windGust = 0000 = 0 m/s
0x15: Solar = 00000000 = 0 Lux
0x16: SolRad = 0000 = 0 W/m2
0x17: UVI = 00 = 0
0x2A: PM2.5 Ch1 = 0078 = 12.0 µg/m3
0x4D: PM2.5 Ch1 24h = 00AF = 17.5 µg/m3
0x51: PM2.5 Ch2 = 0082 = 12.4 µg/m3
0x4E: PM2.5 Ch2 24h = 007D = 12.5 µg/m3
0x2C: soilMoist1 = 41 = 65%
0x2E: soilMoist2 = 40 = 64%
0x30: soilMoist3 = 3E = 62%
0x32: soilMoist4 = 2B = 43%
0x1A: extraTemp1 = 0040 = 6.4°C
0x22: extraHum1 = 4C = 76%
0x1B: extraTemp2 = 005A = 9.0°C
0x23: extraHum2 = 52 = 82%
0x1C: extraTemp3 = 0043 = 6.7°C
0x24: extraHum3[/b] = 58 = 88%
0x1D: extraTemp4 = 005B = 9.1°C
0x25: extraHum4 = 4F = 79%
0x1E: extraTemp5 = FF54 = -17.1°C (WN30, no Hum: FFFF-FF54=AB=171; FF = '-')
0x1F: extraTemp6 = 0057 = 9.3°C
0x27: extraHum6 = 45 = 68%
0x20: extraTemp7 = 0039 = 6.3°C
0x28: extraHum7 = 4B = 75%
0x59: Leak Ch2 0 = OK
0x60: lightning distance 11 = 17 km
0x61: lightning time stamp (last) 6322 265E = EPOCH 1663182430 = 14 September 2022 19:07:10
0x62: lightning day count 00000000 = 0
0x19: day max wind m/s 000C = 12 m/s = 43.2 km/h
0x0E: rain rate 0 mm/h
0x10: rain day 0 mm
0x11: rain week 0.2 mm
0x12: rain month = 1DB =47.5 mm
0x13: rain year = 1A23 = 669.1 mm
0x0D: rain event 0 mm
0x70: WH45 temp (2), Hum (1), pm10(2), pm10-24(2), pm25(2), pm25-24 (2), CO2 (2), CO2-24 (2), battery (1) - sequence !!
WH45-temp: 00D3 = 211 = 21.1°C, WH45-hum: 34 = 52%, PM10: 61 = 9.7 µg/m3, PM10-24: 9D = 15.7 µg/m3, PM2.5: 55 = 8.5 µg/m3 , PM2.5-24: 96 = 15.0 µg/m3, CO2: 02B1 = 689 ppm, CO2-24: 02FF = 767 ppm, battery = 6 (on DC)
0x72: Leaf Wetness Ch1 0%
0x73 - 0x79: WN35 Ch2-8 (not present)
0x2B, 2D, 2F, 31, 33, 35, 37, 39: WN34 Ch1-8 (not present)
0x32, 34, 36, 38: WH51 Ch5-8 (not present)
last byte: Checksum
inside this response (from your app) there is contained
- a WH32 as outdoor temperature and humidity
- the GW1100 indoor T/H and absolute and relative pressure
- the wind speed, maxGust daily, wind direction
- solar radiation and UVI
- 4 WH51 soil moisture sensors
- 7 WH31 extra T/H sensors
- 1 WN35 leaf wetness sensor (channel 1)
- 1 WH55 waster leakage sensor (channel 2)
- 1 WH57 with daily lightning count, EPOCH time stamp of last lightning occurrence and distance of last lightning
- 1 WH40 with all rain data from the interface
- 1 WS90 with piezo rain data
- 1 WH45 with PM2.5, PM10, CO2 data (actual and 24h) plus WH45 temp/hum
- 2 WH41 PM2.5 sensors (channel 1 and 2)
so, except for a WN34 all sensors needed for the complete sensor "fleet"
Most of them (except for WS90 piezo rain, WH45, WH55, WN34 and WN35) you have already properly shown in your interface - just a few more to pick up from the API response.
Only, for the WS90 rain data, you need an extra call beyond CMD_GW1000_LIVEDATA = 0x27 for the piezo rain data (CMD_READ_RAIN = 0x57 - the command will return the values of a classical rain gauge [if connected] and the WS90 piezo rain gauge).
For the PM2.5/PM10 EPA data, there are two scales: one for the actual µg/m3 and related EPA value and one for the 24 h average - to be applied to each of the sensor observations
-
ahaha, yes, see? That is what I mean: a lot of confusion for no reason.
Even super experts have problem understanding what work with what and why.
I think Ecowitt is the actual marketing face of FineOffset that only real player in the whole Ambientweather/froggit/Ecowitt and who knows which other brands ecosystem.
I'm not interested at all in the whole online/logging side of things here. That isn't what my apps is for.
I intentionally left out EVERYTHING cloud/serve based to show that there is no need for any account/password/internet connection. no magic hidden service that just pull data from the internet.
That decision wasn't enough to make people understand how those gateway works seem.
Sometime I'm convinced that companies intentionally try to mud and confuse things for some evil interest but incompetence and ignorance are usually the reason.
Marketing people aren't smart enough to understand how thing works and nerd guys have zero clue about real use case scenario.
Ecowitt is giving away those gateway pretty much for free: I can't imagine how big of a margin they can have on those $30 devices.
They should just packaged it as the center of their whole weather/air quality/water leak/soil stuff ecosystem.
I'm sure engineers there imagined that to be the strategy but Ecowitt have zero clue about it.
A real shame
-
I've always considered the release of the API as a nice to have. Initially, it was very hard to get access to it and was considered closed , and members of this group lobbied hard to have it opened up . I really don't believe the availability of the API had anything to do with the product development in their thought process for the product. I mean it is primarily a cheap way to have a weather station.
No argument the API is confusing, and has occasional changes (a no no for those that use it). For what I use, I just use the custom server option and parse HTTP requests. Not the best thing, but all I need. I can understand your frustration.
Edit: We were ecstatic with even the custom server option when that came about. It allowed a lot of other integrations without being stuck with the standard weather services. I mean most consumer level stuff, don't give you that. I get it is push only, but we didn't have anything at that point.
-
I've always considered the release of the API as a nice to have. Initially, it was very hard to get access to it and was considered closed , and members of this group lobbied hard to have it opened up . I really don't believe the availability of the API had anything to do with the product development in their thought process for the product. I mean it is primarily a cheap way to have a weather station.
I always think about an API from the producer point of view.
Why they release it; what is their goal? How many resources are they going to put into it, is it part of a wide strategy or is it something that one department / side contractor just do on their own for their own reasons?
From my point of view having a local API would be a no brainer for every kind of IOT device.
I'm well aware of how scared are companies to share their stuff but it's really just ignorance and short-sightedness 99% of the time.
It's not that they planning carefully ahead how one decision would effect their strategy.
I feel that all these medium size companies are all super confuse to what their core business is.
Of course the API is part of the product development and strategy. It isn't something you slap on top of a device :).
In case of Fine Offset I can really see how they originally had in mind a whole strategy with their gateways.
I'm pretty sure they started with the API and build a product around it.
I think the original idea was that other producers would use those API to integrate their own service and hardware and wasn't intended to be release to the public at all.
No argument the API is confusing, and has occasional changes (a no no for those that use it). For what I use, I just use the custom server option and parse HTTP requests. Not the best thing, but all I need. I can understand your frustration.
Edit: We were ecstatic with even the custom server option when that came about. It allowed a lot of other integrations without being stuck with the standard weather services. I mean most consumer level stuff, don't give you that. I get it is push only, but we didn't have anything at that point.
Some companies understand that they can exploit nerd communities and the whole free and open github generation but don't know exactly how.
The Ecowitt API isn't really that confusing, it is actually better implemented than most API I see around.
I have almost 0 issue with how stable and reliable the whole product is and how graceful they seem to be able to add new devices and backward combability.
My "frustration" is mostly about the commercial side and the confusion about the product capabilities and I express them here just to vent or find other like minded guys to work with on some fun projects.
-
"From my point of view having a local API would be a no brainer for every kind of IOT device."
I am software development manager for a company that sells an enterprise scale product. Although there is no actual device, I can tell you maintaining an API is expensive in time/labor regardless of the product. You will notice in this case, even on their forums, you will find little direct support for API use. From my perspective , it was released as an AS IS after thought when they were pressured. From a corporate stand point I kind of get that, cheap device, supporting an API cost wise ... eh. I know we only sell access to our API, and that is so we can maintain it, document it, etc.
In reality it is not an APi meant for public use by hobbyists. There are, few, like you, that would tackle it compared to the sale figures for the units, which is the goal. It is readily apparent , this was not meant to be something for the casual developer. Most companies would not even think of releasing the API for free, if it meant, that someone could create something to compete with their own products (now or in the future).
Basic business, you want to control your ecosystem and maximize profit.
Luckily, they did open it up. I really don't expect them to provide support for individual questions on it. Which is why, you are getting your information from in here, on this forum, from others that work with it.
-
provided decoding of post #23 inline - see above
-
i did not know about this windows app i just seen it so i downloaded the trial version i fill in the ip address and its not working i have provided screen shots.... is this a trail version limitation? i can view my GW1100 on my phone app with no issues.
I have tried rebooting both my windows machine and the GW1100
Thank You
[ You are not allowed to view attachments ]
[ You are not allowed to view attachments ]
-
quick update i left the app running and forgot about it so i open the app getting ready to close it and its working how odd i have not altered or changed anything
-
OK time for a refresh.
[ You are not allowed to view attachments ]
Next week I'll refresh the app a bit, clean up the protocol and rebranding the things.
(maybe splitting into different use cases since I think EcoWitt is doing a terrible job at explaining their products.
I always look for people to help testing and suggest features.
-
I finally had a bit of time to clean up some of protocol mess.
Beta available for free as usual on the microsoft Store
https://apps.microsoft.com/store/detail/ew-gw2000/9MTK0V8DTXSM
Feedback is always appreciated.
Once I'll finalize this I'll update the whole set that market the different models (GW1000 GW1100 WH2640 etc)
[ You are not allowed to view attachments ]
-
Hi!
A first quick test ...
Basically a useful Windows programme with a lot of potential.
However, the query via GW1000-API does not yet work completely. But it's still a beta - I'm sure you'll get to grips with that before release.
A few comments:
- DISCOVER does not work yet
- after manually input the ip address the program crashed; after restarting and set units again it seems to work
- show device info tile does not work
About sensors:
- WH45 values do not appear
- I see 16 (!) SOIL sensors (some with the same name) - SOIL1..8 are the WH51 - ok (but they only have the soilmoisture - no need for displaying the temperature
- Sensors 9 - 16 partly from the WH45
- in Live Data I see also 16 soiltemp sensors - there're only 8 at all
- Outddor temperature is not correct (even in °F)
- Indoor humidity is not correct (even on your screenshot)
- 24h AQI#1 is not correct
- AQ#2-4 (non-existent here) all show the same values
And some suggestions:
- it would be nice to have the possibility to disable unused tiles
- one should be able to name the sensors
- I would like to see the battery and/or the reception state
- UI should be also scrollable with keyboard (not only mouse)
- Many users will probably want to be able to arrange the tiles as they wish
I think as soon as the programme works correctly it will find its buyers.
Oliver
-
Nice app! Testing with a GW1100. A couple of observations:
- The decimal point in the rain reporting (in inches) needs to move left one position. Rain Event shows 5.4, should be .54. Daily Rain shows 2.6, should be .26, etc.
- All other data looks accurate.
- I like the ability to check the firmware version from the settings screen.
- When I click on the Feeback link in the settings screen, it shows a window with the latest incoming data but no way to enter feedback or send it.
- Agree with the request to disable blocks that aren't used. I only have the basic sensors.
Keep up the great work!
-Chris
-
Hi!
A first quick test ...
Basically a useful Windows programme with a lot of potential.
However, the query via GW1000-API does not yet work completely. But it's still a beta - I'm sure you'll get to grips with that before release.
Excellent thanks for trying the app.
A few comments:
- DISCOVER does not work yet
- after manually input the ip address the program crashed; after restarting and set units again it seems to work
UDP traffic isn't always the most reactive. Maybe I did set timeouts a bit too aggressive. Keep smashing that DISCOVER button and the gateway should eventually answer.
- show device info tile does not work
Yes, that is an extra tile with some low level info, I'm still not sure if I want implemented in the final version...
About sensors:
- WH45 values do not appear
- I see 16 (!) SOIL sensors (some with the same name) - SOIL1..8 are the WH51 - ok (but they only have the soilmoisture - no need for displaying the temperature
- Sensors 9 - 16 partly from the WH45
- in Live Data I see also 16 soiltemp sensors - there're only 8 at all
- Outddor temperature is not correct (even in °F)
- Indoor humidity is not correct (even on your screenshot)
- 24h AQI#1 is not correct
- AQ#2-4 (non-existent here) all show the same values
I don't know which sensors a WH45 populate. Take a look under the Device LIVEDATA in the settings and
see if you can recognize the values there.
The 16 humidity values and 16 temperature values are in the protocol. Ecowitt could use them or not use them anytime.
It they are in the protocol I'll show them.
The idea is to give users a useful troubleshooting tool that is as transparent as possible and help them decide what they can buy or not.
Ideally somebody could start sending EcoWitt screenshots to ask which sensor buy.
As now I just feel that their marketing is pretty confusing and not show the potential of the ecosystem.
I honestly have no idea how EcoWitt utilize that outdoor temperature. In my case the outdoor/wind/rain/pressure are all coming from an Ambient Weather station WS2902 that the GW1000 just recognize.
Indoor humidity is not correct (even on your screenshot)
24h AQI#1 is not correct
[AQ#2-4 (non-existent here) all show the same values
I want believe that I left test values there. Those sensors should be pretty straighforward
PM25_CH1; // =0x2A,
PM25_24HAVG1; // =0x4D
PM25_24HAVG2; // =0x4E
PM25_24HAVG3; // =0x4F
PM25_24HAVG4; // =0x50
PM25_CH2; // =0x51
PM25_CH3; // =0x52
PM25_CH4; // =0x53
I considered about leaving those markers visible in the application.
And some suggestions:
- it would be nice to have the possibility to disable unused tiles
- one should be able to name the sensors
- I would like to see the battery and/or the reception state
- UI should be also scrollable with keyboard (not only mouse)
- Many users will probably want to be able to arrange the tiles as they wish
Once this ALL-IN version is acceptable is done I'll probably deploy alternative interfaces that will let the user name their sensors.
Would love to have those battery levels but my GW1000 (firmware GW1000B_V1.75) don't return any and I don't understand the protocol implementation.
I'll see how Microsoft implemented tiles but during last years they change their mind so many times and every version works a bit different, add a huge overhead and break combability.
Now that I had a bit of feedback (I didn't even know if the thing was still working outside my house) I'll rush a cleaner version.
Thanks for now
-
Thanks for testing
Nice app! Testing with a GW1100. A couple of observations:
- The decimal point in the rain reporting (in inches) needs to move left one position. Rain Event shows 5.4, should be .54. Daily Rain shows 2.6, should be .26, etc.
- All other data looks accurate.
That is very weird. I forced a last minute en-US localization for numbers and dates (to avoid commas and points confusion) and I wonder if that broke something./
Do you mind posting a screenshot and paste the result of the LIVEDATA /feedback here?
- I like the ability to check the firmware version from the settings screen.
- When I click on the Feeback link in the settings screen, it shows a window with the latest incoming data but no way to enter feedback or send it.
- Agree with the request to disable blocks that aren't used. I only have the basic sensors.
Keep up the great work!
-Chris
For this specific version Im thinking to keep EVERYTHING VISIBLE ALL THE TIME....
Once the protocol is solid I'll deploy another version that will HIDE everything not used and give it for free to people that own the more technical and less user friendly.
-
Thanks for testing
Nice app! Testing with a GW1100. A couple of observations:
- The decimal point in the rain reporting (in inches) needs to move left one position. Rain Event shows 5.4, should be .54. Daily Rain shows 2.6, should be .26, etc.
- All other data looks accurate.
That is very weird. I forced a last minute en-US localization for numbers and dates (to avoid commas and points confusion) and I wonder if that broke something./
Do you mind posting a screenshot and paste the result of the LIVEDATA /feedback here?
- I like the ability to check the firmware version from the settings screen.
- When I click on the Feeback link in the settings screen, it shows a window with the latest incoming data but no way to enter feedback or send it.
- Agree with the request to disable blocks that aren't used. I only have the basic sensors.
Keep up the great work!
-Chris
For this specific version Im thinking to keep EVERYTHING VISIBLE ALL THE TIME....
Once the protocol is solid I'll deploy another version that will HIDE everything not used and give it for free to people that own the more technical and less user friendly.
Attached a screen shot of the Rain tile and the Feedback window. No rain today, but the weekly rain should be .54 and the monthly and annual should be 1.66. Interestingly, today the Feedback window is showing what looks like hex data - could have also been hex data last night and I misinterpreted. Also, I had no problem with the discovery - it found my GW1100 right away.
Makes sense to focus on the protocol first. Again, nice app!
-Chris
-
Attached a screen shot of the Rain tile and the Feedback window. No rain today, but the weekly rain should be .54 and the monthly and annual should be 1.66. Interestingly, today the Feedback window is showing what looks like hex data - could have also been hex data last night and I misinterpreted. Also, I had no problem with the discovery - it found my GW1100 right away.
Makes sense to focus on the protocol first. Again, nice app!
-Chris
Excellent. Fixed.
l should probably hide better that "feedback" menu....
"Feedback" show exactly what the Gateway return.
"Device" show a more human parsed version and conversions.
In "Main screen" I apply all the necessary unit conversions.
I apologize for all the exceptions, I'm being very disorganized applying the conversions in different spots just because I work on the thing 20 minutes here and there instead of just giving it 4 solid hours lol.
-
Interestingly, today the Feedback window is showing what looks like hex data - could have also been hex data last night and I misinterpreted. Also, I had no problem with the discovery - it found my GW1100 right away.
the hex data is the API response of the Ecowitt Gateway API
If you are interested in more details, read https://www.wxforum.net/index.php?topic=40730.0 chapter 14
-
Attached a screen shot of the Rain tile and the Feedback window. No rain today, but the weekly rain should be .54 and the monthly and annual should be 1.66. Interestingly, today the Feedback window is showing what looks like hex data - could have also been hex data last night and I misinterpreted. Also, I had no problem with the discovery - it found my GW1100 right away.
Makes sense to focus on the protocol first. Again, nice app!
-Chris
Excellent. Fixed.
l should probably hide better that "feedback" menu....
"Feedback" show exactly what the Gateway return.
"Device" show a more human parsed version and conversions.
In "Main screen" I apply all the necessary unit conversions.
I apologize for all the exceptions, I'm being very disorganized applying the conversions in different spots just because I work on the thing 20 minutes here and there instead of just giving it 4 solid hours lol.
in the version released in the Microsoft store under the link provided
a) CO2-AQ-Combo (WH45) data are in the API response (settings, feedback), NOT is the human readable parsing result (Settings, device) and NOT in the user interface
b) AQ data (WH41/43) for non-existing channels are displayed with the data of the last existing channel (they are not in the API response nor in the parsing result => some field initialization missing)
c) WN34 data are in the API response, also in the parsing results, but not shown in the user interface (they are USER-TEMP and not SOIL-TEMP)
16 completely useless (because non-existing) sensors: SOIL-TEMP1-16 are shown and take unnecessary space in the interface
d) WN35 data is in the API response, NOT in the parsing result and NOT shown in the user interface
imho removing the SOIL-TEMP and displaying the 8 WN34 (USER-TEMP) and the 8 WN35 (Leaf Wetness) instead would solve the user interface space problem
(that the WN35 doesn't show in the parsing results is most likely a programming error, same with WH45 data)
I sent you supporting evidence as text files (feedback [API] and corresponding parsing results [Device] in topic related PMs
It's getting better and better ... [tup]
-
one correction:
in my latest download the WH45 data is now also displayed in the user interface
missing the buffer clearance for the WH41/43 sensors - and the display of the WN34 and WN35 sensors
[ You are not allowed to view attachments ]
EDIT: attached screencopy
-
New Sunday beta (still free) version is out.
https://apps.microsoft.com/store/detail/ew-gw2000/9MTK0V8DTXSM
nothing dramatic on the surface.
moved around the structural protocol so it's just much easier for me to keep the thing modular. /
I finally got all the tiles out.
Still no idea how to get a
Feel like value (calculated?)
DewPoint (calculated?)
Air Quality Index (calculated?)
battery levels
sensors ID
Happy weekend
-
Still no idea how to get a
Feel like value (calculated?)
DewPoint (calculated?)
Air Quality Index (calculated?)
as per the API description ("TCP protool") they should come with the API response: markers 0x03, 0x04, 0x05
the console should have calculated these values
battery levels
sensors ID
via the API - read the description closely 8-)
use
CMD_READ_SENSOR_ID_NEW
on page 9 of the API documentation it says:
"CMD_READ_SENSOR_ID_NEW interpret each sensor for battery status ."
see also page 30 from "31)" on and 33
for other sensors the battery level comes with the sensor data WH45, WH31 ... (see API description)
-
My GW1000 did never return
DewPoint, WindChill or Heatindex.
...
0x01 IN_TEMP C x10: 197
0x02 OUTTEMP C x10: 109
0x03 DEWPOINT C x10:
0x04 WINDCHILL C x10:
0x05 HEATINDEX C x10:
0x06 INHUMI %: 45
0x07 OUTHUMI %: 80
...and I don't think your configuration have those either but the
Ecowitt app WSView have those values (that why the hypothesis was that they were calculated)
---
DIFFERENT COMMANDS FOR THE BATTERIES AND IDS!!!! I didn't even considered those... :roll:
-
I think you messed up a few things with your "corrections" - but not only
a) (superficial) the second column of the Leaf Wetness sensors shows °F where it should be %
b) the WH45 sensors are not properly read/displayed (everything is in the API response though)
if the PM2.5/PM10 sub-sensors show, after a long time passed, they show some "astronomical" values - the CO2 and T/H values are missing
c) the User Temp 1 shows also astronomical numbers - the first two of the three bytes contain the temperature, the 3rd byte has the battery status (value x 0.02)
d) the Leaf Wetness 1 shows a wrong value
e) the PM25 CH4 sensor (WH41/43) shows a ghost sensor which doesn't exist (and no other such sensor around - not shown in the API response either)
0x4D PM25_24HAVG01 μg/m³: 161
0x4E PM25_24HAVG02 μg/m³: 455
0x4F PM25_24HAVG03 μg/m³:
0x50 PM25_24HAVG04 μg/m³:
0x51 PM25_CH02 μg/m³: 810
0x52 PM25_CH03 μg/m³:
0x53 PM25_CH04 μg/m³: 108
0x53 doesn't occur in the API response ...
not sure how you program, but the detection of the sensors MUST be done in the sequence they appear in the API response and not alphabetically or by sorted HEX values.
Otherwise it won't work. The sequence is shown in my post https://www.wxforum.net/index.php?topic=40730.0 chapter 14
the 0x71 sensor does not exist by the way - for sure no PM25 sensor
09:40:45 PM [ LIVEDATA ]
OK
Size: 154 bytes
Last Update : 09:40:48 PM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0x9A 0x01 0x00 0xC0
0x06 0x30 0x08 0x26 0xF3 0x09 0x28 0x16
0x02 0x00 0x13 0x07 0x63 0x0A 0x00 0x8F
0x0B 0x00 0x0B 0x0C 0x00 0x0C 0x15 0x00
0x00 0x00 0x00 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x8C 0x4D 0x00 0xA1 0x51 0x03
0x2A 0x4E 0x01 0xC4 0x2C 0x41 0x2E 0x40
0x30 0x49 0x32 0x2C 0x1A 0x00 0x0A 0x22
0x5D 0x1B 0x00 0x0C 0x23 0x61 0x1C 0x00
0x13 0x24 0x62 0x1D 0x00 0x10 0x25 0x62
0x1E 0xFF 0x38 0x1F 0x00 0x0F 0x27 0x5F
0x20 0x00 0x4F 0x28 0x3D 0x59 0x00 0x62
0x00 0x00 0x00 0x00 0x61 0x63 0x76 0x34
0xD6 0x60 0x25 0x19 0x00 0x6A 0x0E 0x00
0x00 0x10 0x00 0x0A 0x11 0x00 0x0A 0x12
0x00 0x00 0x04 0x95 0x13 0x00 0x00 0x04
0x95 0x0D 0x00 0x02 0x63 0x00 0x05 0x4B
0x70 0x00 0xC3 0x2F 0x00 0x64 0x00 0x72
0x00 0x5C 0x00 0x6C 0x03 0x73 0x03 0x33
0x06 0x72 0x51 0xFB
0x63 TF_USR01 C x10: 346992
0x64 TF_USR02 C x10:
0x65 TF_USR03 C x10:
0x66 TF_USR04 C x10:
0x67 TF_USR05 C x10:
0x68 TF_USR06 C x10:
0x69 TF_USR07 C x10:
0x6A TF_USR08 C x10:
SENSOR CO2 (WH45)
0x---- ---- C x10:
0x---- ---- %:
0x---- ---- ppm:
0x---- ---- ppm:
0x---- ---- μg/m³:
0x---- ---- μg/m³:
0x---- ---- μg/m³:
0x---- ---- μg/m³:
SENSOR
0x71 PM25_AQI -----:
0x72 LEAF_WETNESS_CH01 -----: 0
0x73 LEAF_WETNESS_CH02 -----:
0x74 LEAF_WETNESS_CH03 -----:
0x75 LEAF_WETNESS_CH04 -----:
0x76 LEAF_WETNESS_CH05 -----:
0x77 LEAF_WETNESS_CH06 -----:
0x78 LEAF_WETNESS_CH07 -----:
0x79 LEAF_WETNESS_CH08 -----:
-
I'm testing the GW2000 V0.99.
A lot to like.
If not mentioned before, the compass wind pointer is 180 deg out of phase with the numerical reported value.
Steve
-
[ You are not allowed to view attachments ]
to show a few of the inconsistencies in the interface mentioned earlier
a) WH45 not showing, not showing in the parsed table, showing in the API response
b) WN34 CH1 wrong number, as mentioned above you have to use the first two bytes, not all three bytes
c) what temperature is supposed to be shown at the wind tile ?
d) the wind direction is showing correctly in my case, under the console calibration I have a 90° offset, but this is considered in the API response
e) the WN35 CH1 value now correct, after some time - not sure what "dirt effect is going on" - but parsed table and interface are consistent - only sometimes wrongly translated from the API response (some buffer initialization issue ?)