I've been watching this thread and just checked my livedata string from my GW1100 and it does not show keys 0x03 or 0x04 when accessed via a sockets call to the GW1100, however when doing the call to the GW1100 using HTTP I do see these keys. Which indicates to me that there is an issue here which Ecowitt needs to address.
The raw data split out by key value and data shows
ffff27005c Header
01 00c5
06 3b
08 278b
09 27b9
02 0045
07 5c
0a 0034
0b 0027
0c 003d
15 00016fe4
16 0000
17 00
2a 0000
4d 0037
1a 0049
22 59
1b 00c7
23 3b
62 00000000
61 63f14470
60 1f
19 005b
0e 0000
10 0004
11 000c
12 00000014
13 000001b5
0d 0006
f1 CRC
and the live data call via http shows
{ "common_list": [
{ "id": "0x02", "val": "6.9", "unit": "C" },
{ "id": "0x07", "val": "92%" },
{ "id": "3", "val": "4.8", "unit": "C" },
{ "id": "0x05", "val": "6.9", "unit": "C" },
{ "id": "0x03", "val": "5.7", "unit": "C" },
{ "id": "0x04", "val": "4.8", "unit": "C" },
{ "id": "0x0B", "val": "6.71 mph" },
{ "id": "0x0C", "val": "9.84 mph" },
{ "id": "0x19", "val": "20.36 mph" },
{ "id": "0x15", "val": "57.16 W/m2" },
{ "id": "0x17", "val": "0" },
{ "id": "0x0A", "val": "57", "battery": "5" }
],
"rain": [
{ "id": "0x0D", "val": "0.6 mm" },
{ "id": "0x0E", "val": "0.0 mm/Hr" },
{ "id": "0x10", "val": "0.4 mm" },
{ "id": "0x11", "val": "1.2 mm" },
{ "id": "0x12", "val": "2.0 mm" },
{ "id": "0x13", "val": "43.7 mm", "battery": "0" }
],
"wh25": [
{ "intemp": "19.7", "unit": "C", "inhumi": "59%", "abs": "1012.2 hPa", "rel": "1016.8 hPa" }
],
"lightning": [
{ "distance": "19.2 mi", "timestamp": "02/18/2023 21:34:40", "count": "0", "battery": "5" }
],
"ch_pm25": [
{ "channel": "1", "PM25": "0.0", "PM25_RealAQI": "0", "PM25_24HAQI": "23", "battery": "4" }
],
"ch_aisle": [
{ "channel": "1", "name": "Outdoors", "battery": "0", "temp": "7.3", "unit": "C", "humidity": "89%" },
{ "channel": "2", "name": "Lounge", "battery": "0", "temp": "19.8", "unit": "C", "humidity": "59%" }
]
}
also there seems to be an issue with the above where one "id" value shows "3" as well as an "id" of "0x03".
Looks to me that the string returned from a socket call for command 27 (get live data) differed from the http call which makes no sense at all. Also I do not have a wh25 so have no idea what that represents, and I do not understand "ch-aisle"
Stuart