Ecowitt rejected WN32 device

[Automation_Ken]

My Ecowitt system has a WS90 (7 in 1 Weather Station), and a WN32 (Outdoor Temperature & Humidity).

When I install the Ecowitt devices on HE, I received the message:
"The PWS should be the only outdoor sensor"

The WN32 does not show up as a child device under the Ecowitt WiFi Gateway.

It appears that for some (unknown) reason, the Ecowitt App on HE doesn't like having both the WS90 and the WN32 both operational.

I see no reason that the WN32 could not be made available, just like it allows multiple WN31 indoor units to be accessed.

On my Ecowitt HP2560_C Display Unit, I am able to use the temperature and humidity from the WN32 and the other data sets from the WS90.

[tray_e]

You would probably have more luck catching the developer's attention and others that use the same devices in the release post. You could also search the post for references to WN32. In a short read, I did see that the app only appears to allow one outdoor sensor. But I did not read much further.

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

If you are considering venturing into weather sensors and including them in your home automation setup, EcoWitt offer a range of relatively inexpensive weather sensors that can be integrated into Hubitat using a local data feed (no Internet needed). How Does It Work? EcoWitt develop various weather sensors and weather stations, including sensors for indoor / outdoor temperature and humidity, wind speed and direction, rainfall and rain rate, UV, air pressure and air quality. These sensors can …

[Automation_Ken]

@tray_e

You would probably have more luck catching the developer's attention and others that use the same devices in the release post. You could also search the post for references to WN32. In a short read, I did see that the app only appears to allow one outdoor sensor. But I did not read much further.

I know from the error message that it only allows one outdoor sensor. What I'm saying is that this should not be the case. If obviously found the device and knows what it is. I don't see any reason to block this information from HE.

When I search the topic you referenced, and then click on the matches, I don't get to see the matching posts, I see other non-matching posts. I don't know if this is a problem with my browser (Firefox/Windows-10) or the web page. Maybe the web site is getting a bit lost on a topic with 2,000 posts.

I have been on this forum for less than 2 weeks, and the help I have received has been fantastic. However, I have been on other forums for more years than I can count and the rules on other forums tend to be that if you have a specific problem, you start a new topic, rather than add to one that has been going on for years and has 2,000 posts.

Are you saying that the practice here is to lump everything to do with one app in one single topic?

[hydro311]

@Automation_Ken

Are you saying that the practice here is to lump everything to do with one app in one single topic?

For community-developed apps & drivers, yes. There aren't running threads for stock/native apps & drivers, so creating a new post for those questions is the way to go.

For community-developed stuff, keeping questions & responses in one place helps consolidate all that info, and posting there will most effectively attract the attention of the respective developer and fellow active users.

[Automation_Ken]

Different forums, different rules. Thanks to the pointer, I'll re-post over there.

[marktheknife]

It’s not a hard rule, per se.

It’s a longstanding recommendation for troubleshooting custom apps and drivers, primarily for the reason @tray_e alluded to above:

@tray_e

You would probably have more luck catching the developer's attention and others that use the same devices in the release post.

[tray_e]

@marktheknife

It’s not a hard rule, per se.

It’s a longstanding recommendation for troubleshooting custom apps

This....

Wasn't saying you have to. But was also saying that you would likely get faster repsonse and resolution. Also, you might find that the questions you have were already answered (again.... I did not read thoroughly. I just saw mention of it. However, I do not have the WN32 and I am not the developer, so my input would be moot)

[snell]

It also helps because some things (like Ecowitt) have multiple different community-developed drivers, and there might be differences in how they handle such things. If you make a general question, that can delay a good result in cases where people need to figure out whose driver you are using in the first place.

[sburke781]

Most importantly....

@hydro311

fellow active users.