"Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
Moderator: Mattk
"Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
Meteobridge update 6.0 corrupted
Last edited by Platokidd on Sat Jun 01, 2024 3:29 pm, edited 1 time in total.
Re: Meteobridge update 6.0 corrupted
Thought I would add model of the Meteobridge. Ambient Weather branded TP-LINK TL-MR3020(un) ver. 1.9
Everything was fine until restarting and updating to 6.0.
Everything was fine until restarting and updating to 6.0.
Re: Meteobridge update 6.0 corrupted
From which version did you update?
Re: Meteobridge update 6.0 corrupted
Think it was 5.8.
Re: Meteobridge update 6.0 corrupted
Rolling back to 5.8. Too many issues with 6.0 Corrupt MIN /MAX data. Tried to erase all and start over. Nojoy.
5.8 so far is holding min / max data normally. Fingers crossed.
5.8 so far is holding min / max data normally. Fingers crossed.
Re: Meteobridge update 6.0 corrupted
Think I may have figured this out.
I added a Ecowitt WH46 Air Quality Sensor recently. This replaced the Ecowitt 45 air sensor. https://www.amazon.com/dp/B0CSSJDJYX?ps ... ct_details
Now I removed the sensor and no longer sending it's data to the meteobridge.
Been about an hour and so far, all is good. This is on ver 6.0.
Is it even possible a sensor could mess the meteobridge up that bad??
I added a Ecowitt WH46 Air Quality Sensor recently. This replaced the Ecowitt 45 air sensor. https://www.amazon.com/dp/B0CSSJDJYX?ps ... ct_details
Now I removed the sensor and no longer sending it's data to the meteobridge.
Been about an hour and so far, all is good. This is on ver 6.0.
Is it even possible a sensor could mess the meteobridge up that bad??
Re: Meteobridge update 6.0 corrupted
It would have wondered me if 6.0 has anything to do with corrupted min/max.
A new so far not tested sensor from the array of Ecowitt sensors can make all other Ecowitt sensor data go crazy. Ecowitt data is sent from the station in an ill-designed binary format with no field separators but a field length mapping list that went through different versions with mediocre documentation. I hate to spend my time on stupid things, but it looks like I have to dig into this crap again to make it handling the new sensor instead of blowing the whole data read. Sorry for your hassle with it.
A new so far not tested sensor from the array of Ecowitt sensors can make all other Ecowitt sensor data go crazy. Ecowitt data is sent from the station in an ill-designed binary format with no field separators but a field length mapping list that went through different versions with mediocre documentation. I hate to spend my time on stupid things, but it looks like I have to dig into this crap again to make it handling the new sensor instead of blowing the whole data read. Sorry for your hassle with it.
Re: Meteobridge update 6.0 corrupted
I have pointed Boris (@admin) to my WiKi where the needed info to update Meteobridge for a registered WH46 instead of a WH45 should be available.
Assuming we are dealing with the GW1000 station type here (using the so-called telnet API).
By the way - Meteobridge also supports the custom server http protocol.
You could help Boris to update his http custom server API by having one of your consoles/gateways (which has a WH46 registered) post to @olicat's https://er.phantasoft.de and retrieve the customer server string and provide it.
You can use a 10 second posting interval and have it post for 1-2 minutes and this disconnect again - will be enough.
If you have never used ear.phantasoft.de, go there with your browser and find all needed instructions.
I suggest to change the subject of your post to
"Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
then it's easier to identify for others.
Assuming we are dealing with the GW1000 station type here (using the so-called telnet API).
By the way - Meteobridge also supports the custom server http protocol.
You could help Boris to update his http custom server API by having one of your consoles/gateways (which has a WH46 registered) post to @olicat's https://er.phantasoft.de and retrieve the customer server string and provide it.
You can use a 10 second posting interval and have it post for 1-2 minutes and this disconnect again - will be enough.
If you have never used ear.phantasoft.de, go there with your browser and find all needed instructions.
I suggest to change the subject of your post to
"Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
then it's easier to identify for others.

WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: Meteobridge update 6.0 corrupted
I could get that webpage to load. Hope this helps. Using gw2000 (gw1000 setting in mb)
INTEMP C x10: 216 - F: 70.9
OUTTEMP C x10: 18744 - F: 3,405.9
DEWPOINT C x10: - F: ---
WINDCHILL C x10: - F: ---
HEATINDEX C x10: - F: ---
INHUMI %: 108 - %: 108
OUTHUMI %: 68 - %: 68
ABSBARO hpa: 9842 - hPa: 984.2
RELBARO hpa: 10177 - hPa: 1,017.7
WINDDIRECTION °: 119 - °: 119
WINDSPEED m/s: 1 - mph: 0
GUSTSPEED m/s: 5 - mph: 1
RAINEVENT mm: 0 - in: 0.0
RAINRATE mm: 0 - in: 0.0
RAIN_Gain mm: - in: ---
RAINDAY mm: 0 - in: 0.0
RAINWEEK mm: 250 - in: 9.8
RAINMONTH mm: 0 - in: 0.0
RAINYEAR mm: 3113 - in: 122.6
RAINTOTALS mm: - in: ---
LIGHT lux x10: 51100 - lux: 5110
UV μW/m²: 0 - μW/m²: 0
UVI 0-15: 0 - 0-15: 0
TIME ----: - :
DAYLWINDMAX m/s x10: 10 - mph: 2
TEMP1 C x10: 215 - F: 70.7
TEMP2 C x10: 196 - F: 67.3
TEMP3 C x10: 212 - F: 70.2
TEMP4 C x10: 198 - F: 67.6
TEMP5 C x10: 201 - F: 68.2
TEMP6 C x10: 199 - F: 67.8
TEMP7 C x10: 223 - F: 72.1
TEMP8 C x10: 186 - F: 65.5
HUMI1 %: 63 - %: 63
HUMI2 %: 59 - %: 59
HUMI3 %: 59 - %: 59
HUMI4 %: 53 - %: 53
HUMI5 %: 53 - %: 53
HUMI6 %: 57 - %: 57
HUMI7 %: 52 - %: 52
HUMI8 %: 60 - %: 60
ITEM_PM25_CH1 μg/m³: 30 - μg/m³: 3
ITEM_SOILMOISTURE1 %: 59 - %: 59
ITEM_SOILMOISTURE2 %: 0 - %: 0
ITEM_SOILMOISTURE3 %: 40 - %: 40
ITEM_SOILMOISTURE4 %: 43 - %: 43
ITEM_SOILMOISTURE5 %: - %: ---
ITEM_SOILMOISTURE6 %: - %: ---
ITEM_SOILMOISTURE7 %: - %: ---
ITEM_SOILMOISTURE8 %: 0 - %: 0
ITEM_SOILMOISTURE9 %: - %: ---
ITEM_SOILMOISTURE10 %: 0 - %: 0
ITEM_SOILMOISTURE11 %: - %: ---
ITEM_SOILMOISTURE12 %: 0 - %: 0
ITEM_SOILMOISTURE13 %: 0 - %: 0
ITEM_SOILMOISTURE14 %: - %: ---
ITEM_SOILMOISTURE15 %: - %: ---
ITEM_SOILMOISTURE16 %: - %: ---
ITEM_SOILTEMP1 C x10: - F: ---
ITEM_SOILTEMP2 C x10: - F: ---
ITEM_SOILTEMP3 C x10: - F: ---
ITEM_SOILTEMP4 C x10: - F: ---
ITEM_SOILTEMP5 C x10: - F: ---
ITEM_SOILTEMP6 C x10: - F: ---
ITEM_SOILTEMP7 C x10: 100 - F: 50.0
ITEM_SOILTEMP8 C x10: - F: ---
ITEM_SOILTEMP9 C x10: 100 - F: 50.0
ITEM_SOILTEMP10 C x10: - F: ---
ITEM_SOILTEMP11 C x10: 109 - F: 51.6
ITEM_SOILTEMP12 C x10: 113 - F: 52.3
ITEM_SOILTEMP13 C x10: - F: ---
ITEM_SOILTEMP14 C x10: - F: ---
ITEM_SOILTEMP15 C x10: - F: ---
ITEM_SOILTEMP16 C x10: - F: ---
ITEM_LOWBATT -----: - ------:
ITEM_PM25_24HAVG1 μg/m³: 32 - μg/m³: 3.2
ITEM_PM25_24HAVG2 μg/m³: 207 - μg/m³: 20.7
ITEM_PM25_24HAVG3 μg/m³: - μg/m³: ---
ITEM_PM25_24HAVG4 μg/m³: - μg/m³: ---
ITEM_PM25_CH2 μg/m³: 510 - μg/m³: 51
ITEM_PM25_CH3 μg/m³: - μg/m³: ---
ITEM_PM25_CH4 μg/m³: - μg/m³: ---
ITEM_LEAK_CH1 : 0 - -----: 0
ITEM_LEAK_CH2 : 0 - -----: 0
ITEM_LEAK_CH3 : 0 - -----: 0
ITEM_LEAK_CH4 : 0 - -----: 0
ITEM_LIGHTNING KM: 17 - KM: 17
ITEM_LIGHTNING_TIME EPOCH: 1716934960 - Date: Tuesday, 28/05/2024
ITEM_LIGHTNING_TIME : - Time: 05:22:40 PM
ITEM_LIGHTNING_POWER -----: 0 - -----: 0
ITEM_TF_USR1 C x10: - F:
ITEM_TF_USR2 C x10: 64 - F:
ITEM_TF_USR3 C x10: - F:
ITEM_TF_USR4 C x10: - F:
ITEM_TF_USR5 C x10: - F:
ITEM_TF_USR6 C x10: - F:
ITEM_TF_USR7 C x10: - F:
ITEM_TF_USR8 C x10: - F:
ITEM_SENSOR_CO2 -----: - -----:
ITEM_PM25_AQI -----: 0 - -----:
ITEM_LEAF_WETNESS_CH1 -----: - -----:
ITEM_LEAF_WETNESS_CH2 -----: - -----:
ITEM_LEAF_WETNESS_CH3 -----: - -----:
ITEM_LEAF_WETNESS_CH4 -----: - -----:
ITEM_LEAF_WETNESS_CH5 -----: - -----:
ITEM_LEAF_WETNESS_CH6 -----: - -----:
ITEM_LEAF_WETNESS_CH7 -----: - -----:
ITEM_LEAF_WETNESS_CH8 -----: - -----:
------------------
INTEMP C x10: 216 - F: 70.9
OUTTEMP C x10: 18744 - F: 3,405.9
DEWPOINT C x10: - F: ---
WINDCHILL C x10: - F: ---
HEATINDEX C x10: - F: ---
INHUMI %: 108 - %: 108
OUTHUMI %: 68 - %: 68
ABSBARO hpa: 9842 - hPa: 984.2
RELBARO hpa: 10177 - hPa: 1,017.7
WINDDIRECTION °: 119 - °: 119
WINDSPEED m/s: 1 - mph: 0
GUSTSPEED m/s: 5 - mph: 1
RAINEVENT mm: 0 - in: 0.0
RAINRATE mm: 0 - in: 0.0
RAIN_Gain mm: - in: ---
RAINDAY mm: 0 - in: 0.0
RAINWEEK mm: 250 - in: 9.8
RAINMONTH mm: 0 - in: 0.0
RAINYEAR mm: 3113 - in: 122.6
RAINTOTALS mm: - in: ---
LIGHT lux x10: 51100 - lux: 5110
UV μW/m²: 0 - μW/m²: 0
UVI 0-15: 0 - 0-15: 0
TIME ----: - :
DAYLWINDMAX m/s x10: 10 - mph: 2
TEMP1 C x10: 215 - F: 70.7
TEMP2 C x10: 196 - F: 67.3
TEMP3 C x10: 212 - F: 70.2
TEMP4 C x10: 198 - F: 67.6
TEMP5 C x10: 201 - F: 68.2
TEMP6 C x10: 199 - F: 67.8
TEMP7 C x10: 223 - F: 72.1
TEMP8 C x10: 186 - F: 65.5
HUMI1 %: 63 - %: 63
HUMI2 %: 59 - %: 59
HUMI3 %: 59 - %: 59
HUMI4 %: 53 - %: 53
HUMI5 %: 53 - %: 53
HUMI6 %: 57 - %: 57
HUMI7 %: 52 - %: 52
HUMI8 %: 60 - %: 60
ITEM_PM25_CH1 μg/m³: 30 - μg/m³: 3
ITEM_SOILMOISTURE1 %: 59 - %: 59
ITEM_SOILMOISTURE2 %: 0 - %: 0
ITEM_SOILMOISTURE3 %: 40 - %: 40
ITEM_SOILMOISTURE4 %: 43 - %: 43
ITEM_SOILMOISTURE5 %: - %: ---
ITEM_SOILMOISTURE6 %: - %: ---
ITEM_SOILMOISTURE7 %: - %: ---
ITEM_SOILMOISTURE8 %: 0 - %: 0
ITEM_SOILMOISTURE9 %: - %: ---
ITEM_SOILMOISTURE10 %: 0 - %: 0
ITEM_SOILMOISTURE11 %: - %: ---
ITEM_SOILMOISTURE12 %: 0 - %: 0
ITEM_SOILMOISTURE13 %: 0 - %: 0
ITEM_SOILMOISTURE14 %: - %: ---
ITEM_SOILMOISTURE15 %: - %: ---
ITEM_SOILMOISTURE16 %: - %: ---
ITEM_SOILTEMP1 C x10: - F: ---
ITEM_SOILTEMP2 C x10: - F: ---
ITEM_SOILTEMP3 C x10: - F: ---
ITEM_SOILTEMP4 C x10: - F: ---
ITEM_SOILTEMP5 C x10: - F: ---
ITEM_SOILTEMP6 C x10: - F: ---
ITEM_SOILTEMP7 C x10: 100 - F: 50.0
ITEM_SOILTEMP8 C x10: - F: ---
ITEM_SOILTEMP9 C x10: 100 - F: 50.0
ITEM_SOILTEMP10 C x10: - F: ---
ITEM_SOILTEMP11 C x10: 109 - F: 51.6
ITEM_SOILTEMP12 C x10: 113 - F: 52.3
ITEM_SOILTEMP13 C x10: - F: ---
ITEM_SOILTEMP14 C x10: - F: ---
ITEM_SOILTEMP15 C x10: - F: ---
ITEM_SOILTEMP16 C x10: - F: ---
ITEM_LOWBATT -----: - ------:
ITEM_PM25_24HAVG1 μg/m³: 32 - μg/m³: 3.2
ITEM_PM25_24HAVG2 μg/m³: 207 - μg/m³: 20.7
ITEM_PM25_24HAVG3 μg/m³: - μg/m³: ---
ITEM_PM25_24HAVG4 μg/m³: - μg/m³: ---
ITEM_PM25_CH2 μg/m³: 510 - μg/m³: 51
ITEM_PM25_CH3 μg/m³: - μg/m³: ---
ITEM_PM25_CH4 μg/m³: - μg/m³: ---
ITEM_LEAK_CH1 : 0 - -----: 0
ITEM_LEAK_CH2 : 0 - -----: 0
ITEM_LEAK_CH3 : 0 - -----: 0
ITEM_LEAK_CH4 : 0 - -----: 0
ITEM_LIGHTNING KM: 17 - KM: 17
ITEM_LIGHTNING_TIME EPOCH: 1716934960 - Date: Tuesday, 28/05/2024
ITEM_LIGHTNING_TIME : - Time: 05:22:40 PM
ITEM_LIGHTNING_POWER -----: 0 - -----: 0
ITEM_TF_USR1 C x10: - F:
ITEM_TF_USR2 C x10: 64 - F:
ITEM_TF_USR3 C x10: - F:
ITEM_TF_USR4 C x10: - F:
ITEM_TF_USR5 C x10: - F:
ITEM_TF_USR6 C x10: - F:
ITEM_TF_USR7 C x10: - F:
ITEM_TF_USR8 C x10: - F:
ITEM_SENSOR_CO2 -----: - -----:
ITEM_PM25_AQI -----: 0 - -----:
ITEM_LEAF_WETNESS_CH1 -----: - -----:
ITEM_LEAF_WETNESS_CH2 -----: - -----:
ITEM_LEAF_WETNESS_CH3 -----: - -----:
ITEM_LEAF_WETNESS_CH4 -----: - -----:
ITEM_LEAF_WETNESS_CH5 -----: - -----:
ITEM_LEAF_WETNESS_CH6 -----: - -----:
ITEM_LEAF_WETNESS_CH7 -----: - -----:
ITEM_LEAF_WETNESS_CH8 -----: - -----:
------------------
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
08:30:08 AM [ LIVEDATA ]
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x72 0x09 0x27 0xC1
0x02 0x00 0xAD 0x07 0x46 0x0A 0x00 0x64
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0xA9 0x88 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x20 0x51 0x01
0xEA 0x4E 0x00 0xCE 0x2C 0x3B 0x2E 0x25
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD7 0x22
0x3F 0x1B 0x00 0xC4 0x23 0x3C 0x1C 0x00
0xD4 0x24 0x3C 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xC9 0x26 0x36 0x1F 0x00 0xC7
0x27 0x39 0x20 0x00 0xDF 0x28 0x36 0x21
0x00 0xBB 0x29 0x3C 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDE 0x2E 0x00 0x30 0x00
0x70 0x00 0x2B 0x00 0x6C 0x01 0xF7 0x02
0x58 0x00 0x25 0x00 0x63 0x00 0x2E 0x00
0x6F 0x06 0x6C 0x00 0x02 0x49 0x38 0xF1
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x72 0x09 0x27 0xC1
0x02 0x00 0xAD 0x07 0x46 0x0A 0x00 0x64
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0xA9 0x88 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x20 0x51 0x01
0xEA 0x4E 0x00 0xCE 0x2C 0x3B 0x2E 0x25
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD7 0x22
0x3F 0x1B 0x00 0xC4 0x23 0x3C 0x1C 0x00
0xD4 0x24 0x3C 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xC9 0x26 0x36 0x1F 0x00 0xC7
0x27 0x39 0x20 0x00 0xDF 0x28 0x36 0x21
0x00 0xBB 0x29 0x3C 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDE 0x2E 0x00 0x30 0x00
0x70 0x00 0x2B 0x00 0x6C 0x01 0xF7 0x02
0x58 0x00 0x25 0x00 0x63 0x00 0x2E 0x00
0x6F 0x06 0x6C 0x00 0x02 0x49 0x38 0xF1
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
@admin
nachstehend eine API response mit vorhandenem WH46 (marker 0x6B) - dummerweise kommt kurz danach eine 0x70, was ein WH45 sein könnte aber nicht muss. Da es nur entweder einen WH45 oder einen WH46 gibt, müsste m.E. die API response zuerst auf das Vorkommen des 0x6B Markers untersucht werden.
Below is an API response with an existing WH46 (marker 0x6B) - unfortunately, a 0x70 appears shortly afterwards, which could be a WH45 but does not have to be. Since there is only either a WH45 or a WH46 present - never both, the API response should imo first be checked for the presence of the 0x6B marker.
08:30:08 AM [ LIVEDATA ]
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x72 0x09 0x27 0xC1
0x02 0x00 0xAD 0x07 0x46 0x0A 0x00 0x64
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0xA9 0x88 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x20 0x51 0x01
0xEA 0x4E 0x00 0xCE 0x2C 0x3B 0x2E 0x25
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD7 0x22
0x3F 0x1B 0x00 0xC4 0x23 0x3C 0x1C 0x00
0xD4 0x24 0x3C 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xC9 0x26 0x36 0x1F 0x00 0xC7
0x27 0x39 0x20 0x00 0xDF 0x28 0x36 0x21
0x00 0xBB 0x29 0x3C 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDE 0x2E 0x00 0x30 0x00 0xDE = 222 = 22.2 °C; 0x2E = 46 = 46 % humidity; 30 = 48 = 4.8 ug/m3 PM10 etc. 24 bytes
0x70 0x00 0x2B 0x00 0x6C 0x01 0xF7 0x02
0x58 0x00 0x25 0x00 0x63 0x00 0x2E 0x00
0x6F 0x06 0x6C 0x00 0x02 0x49 0x38 0xF1 last byte of the 24 bytes after 0x6B: - battery status 6 = on DC - 0x6C is the marker for free heap stroage (4 bytes data), last byte of the complete response: checksum
the 0x70 response (WH45) is 16 bytes long (excluding the marker), the 0x6B response (WH46) is 24 bytes long (4 additional sensor values at 2 bytes each)
nachstehend eine API response mit vorhandenem WH46 (marker 0x6B) - dummerweise kommt kurz danach eine 0x70, was ein WH45 sein könnte aber nicht muss. Da es nur entweder einen WH45 oder einen WH46 gibt, müsste m.E. die API response zuerst auf das Vorkommen des 0x6B Markers untersucht werden.
Below is an API response with an existing WH46 (marker 0x6B) - unfortunately, a 0x70 appears shortly afterwards, which could be a WH45 but does not have to be. Since there is only either a WH45 or a WH46 present - never both, the API response should imo first be checked for the presence of the 0x6B marker.
08:30:08 AM [ LIVEDATA ]
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x72 0x09 0x27 0xC1
0x02 0x00 0xAD 0x07 0x46 0x0A 0x00 0x64
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0xA9 0x88 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x20 0x51 0x01
0xEA 0x4E 0x00 0xCE 0x2C 0x3B 0x2E 0x25
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD7 0x22
0x3F 0x1B 0x00 0xC4 0x23 0x3C 0x1C 0x00
0xD4 0x24 0x3C 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xC9 0x26 0x36 0x1F 0x00 0xC7
0x27 0x39 0x20 0x00 0xDF 0x28 0x36 0x21
0x00 0xBB 0x29 0x3C 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDE 0x2E 0x00 0x30 0x00 0xDE = 222 = 22.2 °C; 0x2E = 46 = 46 % humidity; 30 = 48 = 4.8 ug/m3 PM10 etc. 24 bytes
0x70 0x00 0x2B 0x00 0x6C 0x01 0xF7 0x02
0x58 0x00 0x25 0x00 0x63 0x00 0x2E 0x00
0x6F 0x06 0x6C 0x00 0x02 0x49 0x38 0xF1 last byte of the 24 bytes after 0x6B: - battery status 6 = on DC - 0x6C is the marker for free heap stroage (4 bytes data), last byte of the complete response: checksum
the 0x70 response (WH45) is 16 bytes long (excluding the marker), the 0x6B response (WH46) is 24 bytes long (4 additional sensor values at 2 bytes each)
Last edited by Gyvate on Sat Jun 01, 2024 4:10 pm, edited 3 times in total.
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
This is from the gw 2000 app. I Was using the wrong app for prior post. Sorry
08:30:08 AM [ LIVEDATA ]
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
08:49:37 AM [ LIVEDATA ]
OK
FIRMWARE: GW2000B_V3.1.3
Size: 174 bytes
Last Update : 08:49:40 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x74 0x09 0x27 0xC3
0x02 0x00 0xAD 0x07 0x48 0x0A 0x00 0x77
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0x4E 0x84 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x21 0x51 0x02
0xE4 0x4E 0x00 0xD2 0x2C 0x3B 0x2E 0x26
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD8 0x22
0x40 0x1B 0x00 0xC4 0x23 0x3D 0x1C 0x00
0xD7 0x24 0x3D 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xD2 0x26 0x36 0x1F 0x00 0xC8
0x27 0x3A 0x20 0x00 0xE1 0x28 0x35 0x21
0x00 0xBB 0x29 0x3D 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDF 0x2F 0x0A 0x2D 0x00
0x8A 0x09 0x1F 0x00 0x83 0x01 0xFB 0x02
0x57 0x07 0xD3 0x00 0x77 0x09 0xD3 0x00
0x88 0x06 0x6C 0x00 0x02 0x46 0xD8 0x27
08:30:08 AM [ LIVEDATA ]
OK
Size: 174 bytes
Last Update : 08:30:11 AM
┌───────────────────────────────────────┐
08:49:37 AM [ LIVEDATA ]
OK
FIRMWARE: GW2000B_V3.1.3
Size: 174 bytes
Last Update : 08:49:40 AM
┌───────────────────────────────────────┐
0xFF 0xFF 0x27 0x00 0xAE 0x01 0x00 0xD8
0x06 0x37 0x08 0x26 0x74 0x09 0x27 0xC3
0x02 0x00 0xAD 0x07 0x48 0x0A 0x00 0x77
0x0B 0x00 0x00 0x0C 0x00 0x00 0x15 0x00
0x00 0x4E 0x84 0x16 0x00 0x00 0x17 0x00
0x2A 0x00 0x32 0x4D 0x00 0x21 0x51 0x02
0xE4 0x4E 0x00 0xD2 0x2C 0x3B 0x2E 0x26
0x30 0x28 0x32 0x2B 0x1A 0x00 0xD8 0x22
0x40 0x1B 0x00 0xC4 0x23 0x3D 0x1C 0x00
0xD7 0x24 0x3D 0x1D 0x00 0xC7 0x25 0x35
0x1E 0x00 0xD2 0x26 0x36 0x1F 0x00 0xC8
0x27 0x3A 0x20 0x00 0xE1 0x28 0x35 0x21
0x00 0xBB 0x29 0x3D 0x58 0x00 0x59 0x00
0x5A 0x00 0x5B 0x00 0x62 0x00 0x00 0x00
0x00 0x61 0x66 0x56 0x59 0x30 0x60 0x11
0x19 0x00 0x0A 0x0E 0x00 0x00 0x10 0x00
0x00 0x11 0x00 0xFA 0x12 0x00 0x00 0x00
0x00 0x13 0x00 0x00 0x0C 0x29 0x0D 0x00
0x00 0x6B 0x00 0xDF 0x2F 0x0A 0x2D 0x00
0x8A 0x09 0x1F 0x00 0x83 0x01 0xFB 0x02
0x57 0x07 0xD3 0x00 0x77 0x09 0xD3 0x00
0x88 0x06 0x6C 0x00 0x02 0x46 0xD8 0x27
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
no problem, the relevant data are there - and if the temperature has meanwhile changed by 0.1° C is of no importance ... 

WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
Thanks. Ecowitt just provided me with their current API docs and indeed the WH46 is new in there. Response from Ecowitt was really fast. Thanks for that.
I implemented support for WH46 in just released Meteobridge update. When WH45 and WH46 are present last one in the data stream will be right (data gets overwritten). For the moment Meteobridge ignores the PM1 and PM4 data the WH46 provides additionally, PM10 and 2.5 should be good enough.
I implemented support for WH46 in just released Meteobridge update. When WH45 and WH46 are present last one in the data stream will be right (data gets overwritten). For the moment Meteobridge ignores the PM1 and PM4 data the WH46 provides additionally, PM10 and 2.5 should be good enough.
Re: "Meteobridge update 6.0 corrupted when an Ecowitt WH46 sensor is connected"
A WH45 and a WH46 cannot be present/registered at the same time in the same console ! It's either or.admin wrote: Sat Jun 01, 2024 5:44 pm Thanks. Ecowitt just provided me with their current API docs and indeed the WH46 is new in there. Response from Ecowitt was really fast. Thanks for that.
I implemented support for WH46 in just released Meteobridge update. When WH45 and WH46 are present last one in the data stream will be right (data gets overwritten). For the moment Meteobridge ignores the PM1 and PM4 data the WH46 provides additionally, PM10 and 2.5 should be good enough.
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki