Mapping to Cloud Service - Bug
Posted: Mon Aug 14, 2023 7:36 pm
Hi -
I think there still might be a bug regarding mapped sensors being reported to the Meteplug Cloud Service. I have the following 3 soil moisture sensors mapped to soil0hum, soil1hum and soil2hum but they appear on Meteoplug as soil/moist # 20, soil/moist # 21 and soil/moist # 22 with no sensor ID. The data appears to be logging to Meteoplug but does not appear on the "Inspect Sensor" page.
Here is my mapping on Meteobridge:
Here is the Meteoplug sensor list:
Sensors are an Ambient Weather products that are run through the GW1000
Running the following on my RPi:
Platform: Raspberry Pi 3 Model B+
RAM: 941 MB total, 792 MB free (15% used)
Storage: WD SLC, 29.3 GB total, 26.8 GB free (9% used, 1881.1 yrs)
SW Version: Meteobridge 5.7 (Aug 10 2023, build 2772), FW 1.3
Thanks
g
I think there still might be a bug regarding mapped sensors being reported to the Meteplug Cloud Service. I have the following 3 soil moisture sensors mapped to soil0hum, soil1hum and soil2hum but they appear on Meteoplug as soil/moist # 20, soil/moist # 21 and soil/moist # 22 with no sensor ID. The data appears to be logging to Meteoplug but does not appear on the "Inspect Sensor" page.
Here is my mapping on Meteobridge:
- Screenshot 2023-08-14 at 1.27.24 PM.png (18.02 KiB) Viewed 32768 times
Here is the Meteoplug sensor list:
- Screenshot 2023-08-14 at 1.30.20 PM.png (19.86 KiB) Viewed 32768 times
Running the following on my RPi:
Platform: Raspberry Pi 3 Model B+
RAM: 941 MB total, 792 MB free (15% used)
Storage: WD SLC, 29.3 GB total, 26.8 GB free (9% used, 1881.1 yrs)
SW Version: Meteobridge 5.7 (Aug 10 2023, build 2772), FW 1.3
Thanks
g