-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problems with wazigate last version #168
Comments
@teegwende can you confirm that the weather station is sending different atmospheric and windspeed values that what appear on the WaziGate Dashboard. |
@SolomonGithu yes, the values are different. Sorry for late reply. Hope you are still going to help me fix the problem. I use raspberry pi 3 model B. Maybe this precision could helpful. |
@teegwende can you use ChirpStack to check the uplink device data. Particularly the sensor values, and if they are different from the values on the WaziGate dashboard. Also, which codec does your weather station use? Is it a custom codec or the ones available on the gateway (JSON, XLPP, LPP)? From your screenshot, the sensor types are being received correctly but the values are different. Maybe the codec is doing some "conversion" with the sensor values |
Unfortunately, I have flashed the SD card with the version 2.2.0, So I am not able to provide you the data you want. Effectively, I didn't pay attention to the codec. I will try again the version 2.3.2 by making sure that I am going to select XLPP codec. I hope things are going to be OK now because I have some issues with the version 2.2.0. The gateway stops running after a period of time and does not emit the SSID. |
Hello @teegwende
Maybe XLPP is not the correct codec for it |
I use the sparkfun Weather Meter Kit. the link of device description is : https://www.sparkfun.com/products/15901. Find attached a snapshot of values collected when i use the version 2.2.0 of wazigate. Maybe it could be helpful. |
the weather station is named stationMeteo. The atmospheric pressure is barometer 1 |
Hello @teegwende
This SparkFun documentation is a LoRaWAN tutorial for one of their LoRaWAN boards. In the tutorial they use the
There is a WaziGate documentation on how to add your custom codecs. To add this SparkFun codec you can put the Decoder function to the JSON body in the POST codec request, that is:
Afterwards run the JavaScript and the custom codec will be available in the device settings: After adding the custom decoder to WaziGate, you need to ensure that there is a JavaScript runtime on the WaziGate(Raspberry Pi) like NodeJS. Please note that these instructions are for the latest WaziGate version |
Hello @SolomonGithu, thank you for your answer. You are right the documentation doesn't cover LoRaWAN. Please find attached the code I use for weather station. |
Hello @teegwende I looked at your code and it is okay. Please use the latest WaziGate version, 2.3.2, and it should work fine. Also, the codec for the WaziGate Dashboard device should be XLPP. Regarding the issue of not being able to see or modify actuator values this is because there is an issue with the endpoints being used by the Edge API Swagger Docs. Sorry about this. The actuator endpoints to set an actuator's value is You can make the POST request to the WaziGate without using the Edge API DOCs by:
Make sure to replace Your can use curl or other codes to make the API requests. |
Hello @SolomonGithu, thanks for your support. I will give a try again. Best regards !! |
Hello,
I have installed the new version of wazigate on a RPI 3 model B. I have to some difficulties.
1- I have assembled a weather station and deployed it. The value of atmospheric pressure is negative and there many numbers after the decimal point in the value of wind speed.
2- I have tried to modify the value of an actuator I created. I used the API of wazigate to do that, but I wasn't able to do that. It is said that the actuator doesn't exist, but it does.
Find attached some snapshots that illustrate what I have explained. the term Pompe designates the device that contains the actuator.
Best regards !!
The text was updated successfully, but these errors were encountered: