Topic: Use more then 8 WH31 with 2 GW1000 possible?

[bekesizl]

Hello,

it is not a usual scenario for weather sensing, but as you can use up to 8 WH31 indoor temperature sensors with a GW1000, it is also usable for smart home applications.
Maybe someone can answer it here.

If I would like to have more than 8 WH31 sensors in my home, would it be possible to have 2 GW1000 and assign a sensor to the first gateway and another to a second gateway?

Being in Europe it is possible to use both 433MHz and 868MHz simultaneously, but having only one type of sensors would be a simpler way.

Best regards,
Zoltán

[galfert]

Yes, I would recommend one be 433 MHz and the other 868 MHz. I think that would be simpler to have one of each frequency because you wouldn't need to manually register the IDs for each sensor. Every time you change battery the sensor will get a new ID. This ID needs to be registered with the corresponding GW1000. Normally this happens automatically. But with two GW1000 with the same frequency then you need to do the registration manually. The registration sticks through firmware updates. So you wouldn't need to do this manual registration often. It is therefore manageable to do it manually. It is just a one time extra step every time you need new batteries (1 to 2 years). It is up to you. You can do it either way.

Do keep in mind that most software will only work with one GW1000. Therefore you will need to deal with each GW1000 separately, as in a separate software install for each. The WS View mobile app will work with both at the same time.

[lemuba]

Hello,

it is not a usual scenario for weather sensing, but as you can use up to 8 WH31 indoor temperature sensors with a GW1000, it is also usable for smart home applications.
Maybe someone can answer it here.

Best regards,
Zoltán

Which kind of Homeautomation do you intend to use? If e.g. Iobroker, and more than 8 sensors needed, you possible do better with Zigbee Temp. and Humidity sensors?
Iobroker supports those devices via a Zugbee Stick and an Iobroker Adapter - not in my use, but very common...

For the GW1000/Froggit DP1500 in use with Iobroker, I get all sensor Data points via a simple Iobroker-Node-Red Adapter Flow, which can be easily extended for additional sensors:
https://forum.iobroker.net/topic/32877/froggit-dp1500-ecowitt-gw1000-usb-dongle-node-red-flow/17

Matthias

[bekesizl]

Thank you both!

I still have to consider if 8 sensors are enough or not, it was a theoretical question.

My home automation system is a Phoenix Contact PLC which can communicate over Modbus TCP with the outside world.
I does most of the control jobs, but has no visualization of the information.
I was rather thinking of Home Assistant (running on a Pi3) for using as visualization and a simple SBC (probably OrangePi One) to act as a Gateway between MQTT and Modbus.
I need a separate computer as the Opensprinkler Weather Service node.js app and the hardware is rather picky to communicate over Port 80 and my current Pi is already using it. Not being a professional Linux/webserver admin I couldn't figure out how to set it up, running that service and something only acting as a gateway on a separate computer is an easier solution for me.

Thank you also for that forum post from ioBroker. I found it already somewhere and this is a possible way to get the data to my PLC.
Maybe use the FOSHKPlugin to replicate the telegrams to use in different application.

This Ecowitt/Froggit gateway seems simple enough for me to use. I mostly need the outdoor weather station sensor signals, but as it is also usable with the indoor temperature sensors, it seems like a good solution.
At the moment I don't want to play with another system like Zigbee.

Zoltán

[ramblinche81]

Every time you change battery the sensor will get a new ID. This ID needs to be registered with the corresponding GW1000. Normally this happens automatically.

While I am a newbie novice, i don't think the device id changes with battery change. When I read the gw1000 how to replace a failed sensor, instructions refer to updating sensor id manually.  Write over old id with new id.  The old id does not go away and this implies you can manually associate a sensor to a system and position in multi sensor setups. 

My soil moisture sensors have hex type id assigned and labeled.. The temp sensors are by channel and I have not looked as closely. 

Since gw1000 looks for devices to synch, you might have to go offsite well out of range for gw#1 to associate sensors 9-16 with gw#2

[AlphaBeta123]

I am in the same situation where I need more than 8 sensors. I have a GW1000 and a GW1100. Both on 915MHz.

Today I was able to get sensors paired to different gateways. This is how I did it.
1) I disabled all unused sensor ports on both gateways. Right now I have 8 WH31 sensors on GW1000 and 8 disabled WH31 ports on GW1100 so none of current WH31s connect to GW1100
2) I disabled WH31 sensor on Ch8 on GW1000 and changed that WH31 to CH1 and enabled CH1 on GW1100. GW1100 registered it just fine. Now I have two different sensors on CH1 of each gateway.

This week I will get a few more WH31 and also try to connect two WH32s, one to each gateway.

[Gyvate]

that's in principle how it can be done.
I recommend taking a screen copy of the sensor IDs of each console (GW1x00) so you can actively reconnect them in case of a reboot - and not only the WH31 (1-8) to GW1x00 (1) but also WH31 (9-16) to GW1x000 (2).
Automatic reconnect may not always work in the desired way.
They may get otherwise messed up in between the consoles when the console(s) reconnect(s)...
(because your CH1 of GW1000(1) could also be registered by GW1000(2) etc. )

[bekesizl]

I finally use two GW1000.
One for the outdoor unit located outside my house.
One for 8 WH31 indoor temperature sensors, all located inside the house.
I disabled all WH31 on the outdoor unit and paired them with the indoor unit.[/img]

[AlphaBeta123]

They may get otherwise messed up in between the consoles when the console(s) reconnect(s)...
(because your CH1 of GW1000(1) could also be registered by GW1000(2) etc. )

Good point, didn't realize gateway doesn't remember IDs between reboots.