I had the same problem with Weather Radio and Arduino Nano since the WiFi feature has been implemented. There must be something in the code (WiFi related probably) that causes that. Wolfgang, the author of Weather Radio, may be able to shed some light.
Since I had some WEMOS D1 Mini, I used one and I got Weather Radio working correctly with INDI. If you have access to one, you can give it a try.
thanks for the response.
You can find in attachment all the files.
I want really use your program to control my observatory because for me the weather is a real problem.
So, I hope that you will found quicly the pb or release the 1.4 for all.
I have people of my association that they want to try kstar + indi + ekos to manage their observatory and they waiting I finish mine!
Tank you very much for the job, it's a great project and I am fan!!
PS: for information, I have modify the BME280.h file to use my velleman sensor. It's not an Adafruits.
I also join the log file with the errors (I try twice).
Si I have send the same ino file to the arduino and when I click several time I succed to connect the driver but I have erros.
I join screenshots.
the version is 1.3 as expected.
When I am connected I see that the value don't resfresh as expected all the 60s...
OK, so in principle it connects and reads the values, but it runs quite often into timeout problems. With version 1.4 I've introduced caching into the firmware, which partially at least speeds up reading.
Maybe the first thing you should change: set the update period to 60 seconds (in French: Mettre à jour). It is currently set to 10 seconds. This could lead to flooding the serial connection via USB.
Typically, you experience these timeouts from long running sensor readouts. For example, reading the TSL2591 at night might take 2 seconds or more. If one of the other sensors shows similar behavior, it could be beyond the interface timeout of 5 seconds. Additionally, it seems that the serial interfaces queues requests and responses, so it might happen that after a timeout everything gets out of sync.
This is not so easy to resolve, since Arduino does not have really a concept for concurrency. So I cannot have two threads or processes in parallel, one answering requests by reading from a cache and the other one updating the cache.
I personally have very good experience with a Wemos D1, which has a WiFi interface integrated. Meanwhile I only use the WiFi connection, which is running flawlessly now for more than two weeks. With the USB interface, I had problems from time to time.
Regarding the pressure: that's intentionally, that it shows a different value than the raw value. The shown value is the calculated pressure on sea level taking the location that you have setup in KStars/INDI.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | ASI 1600mm pro + 6200mm pro | KStars/INDI on Raspberry Pi 4/Intel NUC with Raspbian 10
Sorry for not replying since yesterday, was on the road.
Since I moved to using a Wemos D1 Mini, I haven't had any problem but my Weather Radio (version 1.3) has been offline for sometime since I am (very) slowly working on finishing my observatory. I must admit that I much prefer the way Weather Radio is impletemented vs MeteoStation, based on 'firmata', which is heavier and makes difficult adding functionnality. Furthermore, I had more and more connection problems with MeteoStation, which made the change to Weather Radio a welcomed solution.
From what I vaguely remember with my Arduino Nano version of the later versions of Weather Radio, even issuing commands directly, using the serial console of the Arduino IDE, did not work well. The first command sent returned the correct info but further commands seemed to be queued somewhere and never be replied to or returned invalid data.
As far as referencing the pressure to sea level value, that's the logical thing to do.
Thanks for the response with details. It's very nice.
But, My project is already assembly and if it's possible, I prefere don't retry from 0.
This is not the price of a wemos D1 mini but just I haven't the time to retry.
Like as G_Gagnon, I have a similar problem with the serial command. If i send P I have the good values but if I send just next W I have problem to receive value.
For the delay of sensor response, with the example arduino firmware, the values are instantaneous.
But, if the 5s are long, is it possible to change for 10s for example?
Also, for the 10s I have change for test but i have put 60s by default and the pb are the same.
if I succed to connect to ekos (and it's a very challange!!) the values don't change.
And for the pressure, I forgot this detail with the seal level !! thanks to explain me
And sorry for my bad english...I'm newbie with this language ^^