Dual gateways - 868Mhz and 433Mhz
Posted: Sun 25 Aug 2024 6:33 pm
Hi guys
Bit of an odd ball here I think... I am using two gateways - one for 433Mhz and one for 868nmhz - however, I would expect that the frequency is irrelevant here.
Primary sensors are all on 868Mhz gateway and all work fine in MX.
Second gateway is setup as extra sensor in MX using cloud API (using same keys as primary gateway as its the same ecowitt account), but second gateway MAC address is entered for extra sensors. I have both air quality and lightning sensors on 433Mhz second gateway. I also set the second gateway up to point to cumulus as a custom server, as per the instructions shown.
All data from all sensors are correct in ecowitt and WS_View apps (868 and 433 devices).
I cannot seem to get the data from the second gateway into MX. The air quality and lightning appear in the "extra sensors " page, but data is zero. The extra sensors from the first gateway appear on the "extra sensors" page and is correct.
Settings, "Extra Sensor Settings" has air quality sensor set as "ecowitt sensor 1" - but I fear its trying to find that on the first gateway....
So - a big clue I think is if I point my browser at the "/station/ecowittextra" path that the second station config points at and I get the error:
"{"Error":"HTTP Station (Ecowitt) is not running}" in the browser. IP and port are correct... and I created the file paths that its pointing to.
If I set the second station to use API not cloud, then I get :
Failed: General error - Object reference not set to an instance of an object. rather tha the previous error when pointing my browser at the /station/ecowittextra path.
Any ideas? - please dont suggest replacing the 433 kit - this should work, else why offer the option for a second ecowitt gateway?!?!
Many thanks for your time guys.
David
Bit of an odd ball here I think... I am using two gateways - one for 433Mhz and one for 868nmhz - however, I would expect that the frequency is irrelevant here.
Primary sensors are all on 868Mhz gateway and all work fine in MX.
Second gateway is setup as extra sensor in MX using cloud API (using same keys as primary gateway as its the same ecowitt account), but second gateway MAC address is entered for extra sensors. I have both air quality and lightning sensors on 433Mhz second gateway. I also set the second gateway up to point to cumulus as a custom server, as per the instructions shown.
All data from all sensors are correct in ecowitt and WS_View apps (868 and 433 devices).
I cannot seem to get the data from the second gateway into MX. The air quality and lightning appear in the "extra sensors " page, but data is zero. The extra sensors from the first gateway appear on the "extra sensors" page and is correct.
Settings, "Extra Sensor Settings" has air quality sensor set as "ecowitt sensor 1" - but I fear its trying to find that on the first gateway....
So - a big clue I think is if I point my browser at the "/station/ecowittextra" path that the second station config points at and I get the error:
"{"Error":"HTTP Station (Ecowitt) is not running}" in the browser. IP and port are correct... and I created the file paths that its pointing to.
If I set the second station to use API not cloud, then I get :
Failed: General error - Object reference not set to an instance of an object. rather tha the previous error when pointing my browser at the /station/ecowittextra path.
Any ideas? - please dont suggest replacing the 433 kit - this should work, else why offer the option for a second ecowitt gateway?!?!
Many thanks for your time guys.
David