|
Post by doxidad on Mar 27, 2019 5:43:16 GMT -8
blynkinit is looking for a file called EnglishMetric.txt to see how you want to display your values - English or Metric. If it doesn't find this file it gives you the error you are seeing and then defaults to english. The file, if I recall correctly, either has a "1" or a "0" in it to specify which to use.
Blynk works without this file and defaults to English.
|
|
|
Post by SDL on Mar 28, 2019 6:48:20 GMT -8
If you set it to metric, it will write that file out eliminating the error.
BP
|
|
|
Post by rassilon on Mar 31, 2019 13:49:33 GMT -8
I have blynk connected to the pi, but cannot figure out how to get the weather on it, the servers are running but I get weather is offline when I run it on blynk. I am totally new to blynk.
|
|
|
Post by triggerfish on Apr 1, 2019 12:29:14 GMT -8
I have blynk connected to the pi, but cannot figure out how to get the weather on it, the servers are running but I get weather is offline when I run it on blynk. I am totally new to blynk.
Rather straight-forward.
|
|
|
Post by rassilon on Apr 2, 2019 15:52:18 GMT -8
Thank you I totally forgot about the qr code. up n running thanx
|
|
|
Post by triggerfish on Apr 4, 2019 6:03:48 GMT -8
Woohoo! You find everything Peter. It takes about 30 seconds for it to turn off. Did you hit it once and then wait? BP I was aware of the delay. I hit the button, wait a minute minimal and see what happens. It was a time consuming test
- Default oled is on, switch shows on - Hit switch -> off - wait 1 minute -> nothing happens. - Hit switch -> on - within 30 seconds, oled switches off, 30 seconds later switches on again - wait again, nothing changes anymore. oled is on, switch shows on (basically correct)
- continue above and second dash
I put some more debug code in and it seems like the turnOLEDOn and trunOLEDOff functions are called when needed. Still Off does nothing, On switches it off and it will automatically switch on again without one of the functions being called apparently...
Question 1: The powersave has three connections, the middle being the control the the Pi2Grove board. Does it matter where the OLEd is connected on the other two? Is there an IN and an OUT on both other connections?
Question 2: Could it be that the true and false do other thing than expected? IE reversing those values in the turnOLEDxxx function would fix it?
That does not explain the apparently automatically turning on again, but...
Question 3: If turned off, will writing a line to the OLED, turn it on again?
|
|
|
Post by triggerfish on Apr 4, 2019 8:53:05 GMT -8
Never mind... I switched the two cables and now it seems to work as designed. I found a schematic of the powersave board indicating an IN and OUT port. The orientation of the connectors is the only indication at the pcb itself. Anyway, I can switch the OLED off and on with blynk.
|
|
|
Post by SDL on Apr 5, 2019 8:44:45 GMT -8
You Rock!
BTW, new Kickstarter launching in a few days. SkyWeather. We will be selling an upgrade kit from GWP to SkyWeather. Has a camera!
BP
|
|
|
Post by triggerfish on Apr 6, 2019 0:30:05 GMT -8
You Rock! BTW, new Kickstarter launching in a few days. SkyWeather. We will be selling an upgrade kit from GWP to SkyWeather. Has a camera! BP Nice, but I'll wait until the current set is more reliable before adding more And a cam would also mean bigger battery and more solar panels I guess... Never mind... I switched the two cables and now it seems to work as designed. I found a schematic of the powersave board indicating an IN and OUT port. The orientation of the connectors is the only indication at the pcb itself. Anyway, I can switch the OLED off and on with blynk. No the switching works as it should, is there a way to default the OLED to off. Now it stays on after each 48 hour reboot.
|
|
|
Post by SDL on Apr 6, 2019 11:03:15 GMT -8
You could change the GWP software to turn the OLED Off.
BP
|
|