Topic: HP2551 console (FW 1.8.7) and 2+ WH41/43 PM2.5 sensors: display error

[Gyvate]

I recently noticed (having two WH41 PM2.5 sensors connected to my HP2551 console) that when the sensor registered as channel one drops out  (runs out of battery) the sensor registered on channel 2 is no longer diplayed either even though it still has enough battery (to be seen in my GW1x00/GW2000 consoles in WS View Plus).

I have reported this observation already in January to Ecowitt and it was in a first assessment classified as a firmware bug - to be solved with the next (?) device firmware release.

Just to let everybody know who has a similar constellation and and might (or might not yet) have noticed the same behaviour.

[Platokidd]

Interesting. I'll let #1 go dead and see what happens.

I'm running 2 AW pm2.5's (badged as wh42's) and 1 ecowitt wh41.

When 1 of the aw pm2.5 goes dead it's a real pain. The ID changes on re-start and has to be reset on all consoles.
Also have 3 aw wh31's that have the same issue. Must be old stuff.

[Wooks61]

I seem to have a similar problem.
After a battery change, the unit will not re-register on the HP2551 console (v1.9.1).
It does however show up on the GW1000A.
I have tried deleting/re-registering but still no joy.
Powered off for half an hour. Updated firmware (on console)
Battery status for the assigned unit is always saying "LOW BATTERY" (on HP2551).
Unit works fine on GW100A
Any ideas....

[Gyvate]

sounds strange - can you take out the batteries from the WH41 for a minute and re-insert.
Also disable WH41 channel 2-4 in the Sensors ID section of the console.

If the issue persists, disable channel one and register* the WH41 on channel 2 in the HP2550 console (remove the sensor batteries before, re-insert) -  switch on "enable", enter the sensor ID (printed on a label on the housing [or from your GW1100]) and press save - wait for the success message.

*) register ? you actively do that as described before, don't put the console in learning mode and let it search - might not work

[Rover1822]

I know, this may not be germaine, but when you make these changes , the sending from the units can be up to 10 minutes, so you have to be patient a bit.

I know I have had to.

[Wooks61]

I have three PM2.5 sensors.
The battery died on one of them (CH2 ID60) whilst I was away.
On my return replaced the dead ones for a new set.
Normally the sensors reconnect with no problem as they have done many times before.

However, I later noticed on the Ecowitt site and app that the HP2551 had "lost" the channel 2 sensor. The GW1000 was still reporting correctly.
Another observation was the the Battery Low warning on the Ecowitt site was still showing.
Initially suspected that the replacement set weren't full so replaced again.
Still the same indications.

followed Gyvates suggestions of Disabling each channel and re-enabling...
Same problem.

Swapped all three units around on different channels (on both HP2551 and GW1000).
This managed to clear the Battery low indicator.
The Unit ID60 failed to register on any channels of the HP2551 but registered on all of the channels of the GW1000.

After rebooting  the GW1000 and HP2551;
Taking batteries out of all three sensors;
Swapping channels around on all devices.
Recharging sensors via USB.

All above steps with and without long pauses to allow all devices to go dead...

Same problem:
The one sensor (ID60) registers and reports via the GW1000 but will not register on the HP2551. !!!

[Gyvate]

does maybe this "stubborn" WH41 sensor have  an unfortunate positioning with reference to the HP2550 console ... ?
Did you place it near to the HP2550 ? About 1 m distance ?
The HP2550 is more sensitive to reception obstacles (and there are also tweaks to overcome this).
Looks like this WH41 is the only misfit here.

[Wooks61]

I thought you may ask this.
I meant to add that at the time of the tests, the "stubborn sensor" and a "good one" were in the same room as the HP2550.
I'm just in the process of shutting down the gateways and restarting both the gateways and the sensors. I am going to place the stubborn one alongside the good one to compare the values received over a number of checks.

[Rover1822]

If you have at least one gateway that appears to be working , the GW1000. Then the issue in my mind is an issue with the the one that doesn't.  Really no issue with the actual sensors, but with the one gateway.

What complicates matters is that at one point it did work. I  hate to say this but I would do a full reset on the troublesome gateway, I mean a factory reset. I know most of us shy away from this as you have to set up everything again, and it is a last resort thing.

[Gyvate]

you may still consider to move the HP2550 console close to the sensor (but not too close - 1 m) rather than bringing the sensor close to the console.
The console may be in a strange EMI situation ...

the troublesome "gateway" here is the HP2551 console.
If you decide to go for a factory reset, before a factory reset you should
- make a full backup of the data in memory to a SD card (option under Settings --> More [settings])
- note down any calibration values you use
- note down your rain totals
- save custom server data if used
all this data will get lost in a factory reset

if all this doesn't help, the culprit is likely to be the WH41. Then write to Ecowitt support and ask for replacement.

[Wooks61]

Just to satisfy my curiosity...
Am I right to assume that Froggit HP1000SE is the same firmware as the Ecowitt HP2551?
Or is this my problem?

I am leaning toward the gateway as I now have a battery indication for CH4 even though CH4 is disabled. ( I used CH4 last night whilst swapping sensors/channels)
Also the PM2.5 sensors are Froggit branded DP200.

[Gyvate]

why don't you read our MUST READ thread and find the answer there ? 
https://www.wxforum.net/index.php?topic=40730.0
or/and
as you are obviously German, read the Ecowitt Weather Station WiKi at
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-stationen
you won't find the nice picture matrix there as you do in our MUST READ thread, but as for the rest, they are +/- identical or very similar.
Firmware is the same for all FineOffset consoles of the same type - version may be different - latest is 1.9.1 for a HP2550 etc. --> MUST READ

[Wooks61]

 

OK....
Rolled back Firmware to 1.8.6.
Same results.
Tests carried out with two PM2.5 sensors (ID60 and ID62).
GW1000A and HP1000SE co-located in same room and in separate locations

So my conclusion:

On the HP1000SE:
PM2.5 sensor with ID62 registers on any channel and displays data correctly.
PM2.5 sensor with ID60 will not register and display no data on any channels although Battery Level Indicator displayed on Ecowitt web page.
The HP1000SE appears to be receiving on all four channels
So suspect there is a problem with PM2.5 sensor with ID60.

On GW1000A:
PM2.5 sensor with ID60 registers and displays data correctly on any channel.
So doesn't appear to be a problem with PM2.5 sensor with ID60,

Maybe I should just get another sensor.....

[Rover1822]

On GW1000A:
PM2.5 sensor with ID60 registers and displays data correctly on any channel.
So doesn't appear to be a problem with PM2.5 sensor with ID60,

And I assume , as you have stated , it also gets all the others.
If so, I fail to see a sensor issue.
Edit: Just trying to stop you from spending money on a new sensor , that may also have the same issue. This is based on it all worked at one point.
Edit2: If you did not have a gateway that did not receive the sensor data , then yes , by all means, it is the sensor. But unless I read it wrong , you have just one console/gateway that has the issue, the other has no problem.

[Gyvate]

Maybe I should just get another sensor.....

1. put your HP1000SE Pro back to 1.9.1  - 1.8.6 has still issues with WH41 sensors in certain constellations - solved with 1.9.0/1.9.1
2. if your WH41/DP200 was purchased within the last year, ask for a replacement
don't mention the GW1100, it will only complicate things

[Wooks61]

why don't you read our MUST READ thread and find the answer there ? 
https://www.wxforum.net/index.php?topic=40730.0
or/and
as you are obviously German, read the Ecowitt Weather Station WiKi at
https://www.wetterstationsforum.info/wiki/doku.php?id=wiki:wetterstationen:ecowitt-stationen
you won't find the nice picture matrix there as you do in our MUST READ thread, but as for the rest, they are +/- identical or very similar.
Firmware is the same for all FineOffset consoles of the same type - version may be different - latest is 1.9.1 for a HP2550 etc. --> MUST READ

I also read: https://www.wxforum.net/index.php?topic=41770.msg429663#msg429663
"Hi!

No problem at all - the HP1000SE Pro is just a labeled HP2551C. So it uses the same firmware. You also should check with WS View app whether there's a new WIFI-firmware available.

Regards , Oliver"

As for your assumption I am German. I am actually British (Welsh).
I came here on a 2 year secondment 25 years ago...
Loved the place, people and culture so stayed. 

[Wooks61]

The sensor is over 3 years old so not worried about replacing it. I may even upgrade the GW1000.
Would you suggest the GW11xx or GW20xx

[Wooks61]

@Rover: Agree with you. That is what is confusing. If I only had the GW1000A I wouldnt see "a problem". A new sensor would confirm a problem if there is one.

@Gyvate HP1000SE is back to 1.9.1. It was just to see if there was a problem with the fix for PM2.5 display in 1.8.7.

[Gyvate]

The sensor is over 3 years old so not worried about replacing it. I may even upgrade the GW1000.
Would you suggest the GW11xx or GW20xx

the GW2000 is definitely the most powerful device.
It's also the only one which has a WLAN and LAN interface and which so far supports the IoT products of Ecowitt, e.g. the WFC01, the intelligent water valve.

[Wooks61]

Thank you Gyvate and Rover for your help and suggestions.

[Platokidd]

I recently noticed (having two WH41 PM2.5 sensors connected to my HP2551 console) that when the sensor registered as channel one drops out  (runs out of battery) the sensor registered on channel 2 is no longer diplayed either even though it still has enough battery (to be seen in my GW1x00/GW2000 consoles in WS View Plus).

I have reported this observation already in January to Ecowitt and it was in a first assessment classified as a firmware bug - to be solved with the next (?) device firmware release.

Just to let everybody know who has a similar constellation and and might (or might not yet) have noticed the same behaviour.

Confirmed. #1 went dead and #2 does not show on console. (HP2550) Sorry for the late reply. This was about a month ago.

[Gyvate]

I recently noticed (having two WH41 PM2.5 sensors connected to my HP2551 console) that when the sensor registered as channel one drops out  (runs out of battery) the sensor registered on channel 2 is no longer diplayed either even though it still has enough battery (to be seen in my GW1x00/GW2000 consoles in WS View Plus).

I have reported this observation already in January to Ecowitt and it was in a first assessment classified as a firmware bug - to be solved with the next (?) device firmware release.

Just to let everybody know who has a similar constellation and and might (or might not yet) have noticed the same behaviour.

Confirmed. #1 went dead and #2 does not show on console. (HP2550) Sorry for the late reply. This was about a month ago.

with 1.9.1 (most recent device firmware) it should show again - mine does

[Wooks61]

@Rover: Agree with you. That is what is confusing. If I only had the GW1000A I wouldnt see "a problem". A new sensor would confirm a problem if there is one.

@Gyvate HP1000SE is back to 1.9.1. It was just to see if there was a problem with the fix for PM2.5 display in 1.8.7.

UPDATE:
I now have a new PM2.5 sensor and a new GW2000.
The problematic PM2.5 sensor still registers on the GW1000, but will not register with the new GW2000 (or the HP1000SE).
So it seems that the GW2000 and HP1000SE can somehow detect a faulty sensor whereas the GW1000 doesn't. Maybe???

[kheller2]

What happens if you manually enter the ID in the GW2000?
Are they all in the same vicinity?

[Wooks61]

Hi Kheller2,

Various attempts at connecting (see previous post 23 Aug).
Long story cut short:
I had 3 PM2.5 sensors registered to a GW1000A and HP1000SE Pro.

PM2.5  (ID60) after battery failure will register and give indications on any channel on GW1000A but  will not register on any channel on HP1000SE Pro.

I bought a new PM2.5 sensor (so now have 4) and also bought a GW2000A.
All four sensors will connect and display on the GW1000A.
But the suspect PM2.5 sensor (ID60) will not register on the GW2000A or the HP1000SE Pro.

See above posts for details of investigations.
Tests carried out with units in their original locations AND whilst situated  together in the same room.

My conclusion therefore is that the suspect (ID60) is perhaps faulty. Maybe with a GOOD/BAD status flag which the GW1000A ignores whilst the GW2000A and HP1000SE Pro detect and do not allow registration.

The measurements of the suspect displayed on the GW1000A  seems to correspond with the other units when all are situated in the same place. i.e had I not had another gateway/console, I would not have had any suspicions...