NINA Safety monitor doesn't reflect safe/unsafe state once connected to Lunatico AAG CW safety driver

Stefan Berg Nighttime Imaging 'N' Astronomy (N.I.N.A. / NINA) The ASCOM Initiative ASCOM Troubleshooting
6 replies•195 views
Frédéric Ruciak avatar
Frédéric Ruciak avatar

Hi,

for those of you having a lunatico AAG cloudwatcher station, I have a strange problem and I am looking for fellows having had the same issue and solved it.

I installed my remote setup last week. I have a Lunatico AAG cloudwatcher and the SOLO device. I operate with NINA remotely. The ascom driver of lunatico for the AAG CW is installed. I can connect the weather station tab in NINA to AAG CW, I use a mapped drive, point the .json file check the data and receive “data looks great” and it works. When I connect the safety monitor tab in NINA to AAG CW with the ASCOM driver of AAG CW for safety, I point to the same file, check the data and receive “data looks great” connect, and is shows it is connected BUT the “is safe” never changes and stays unsafe despite I can read in the .json file that it is safe. So I cannot open the roof with NINA whereas I can open it with the dedicated software that is also linked to AAG CW independently and recognised the safe status.

Does it look like the problem somebody had already or like a similar problem once of you had?

Thank you for reading,

CS Frédéric

Helpful Respectful Concise
Jean-Michel Hirschi avatar
Jean-Michel Hirschi avatar

Hi Frédéric,

I’m using the same setup and don’t have any issue. Here is my settings in the CloudWatcher ASCOM Setup. Can you check if you connect the same .json file ?

Jean-Michel

📷 image.pngimage.png

Helpful Respectful Concise Supportive
Frédéric Ruciak avatar
Frédéric Ruciak avatar

Hi Jean Michel,

it seems that my ascom driver is not the same than yours. I have the solo and the AAG CW but the solo is just an convenient way to access to it over the web. The ascom driver I have is the last one and works for the weather conditions and for safety. This is how it looks. When I check the json file I have “data looks great” but the is safe never turns to a green tick.

Do you still have the ascom driver as you downloaded it? is it possible to share it to make a try on my config?

thank you for your help, Frédéric

The json file looks like this

{

"dataGMTTime" : "2026/06/17 20:34:27",

"cwinfo" : "Serial: 3306, FW: 5.89",

"slddata" : "2026-06-17 22:34:27.00 C K -8.4 23.6 23.6 4.0 68 17.3 10 0 0 00000 046190.94059 1 1 1 1 0 0 +15.59",

"clouds" : -8.420000,

"cloudsSafe" : "Safe",

"temp" : 23.590000,

"wind" : 4,

"windSafe" : "Safe",

"gust" : 4,

"rain" : 3200,

"rainSafe" : "Safe",

"lightmpsas" : 15.59,

"lightSafe" : "Safe",

"switch" : 1,

"safe" : 1,

"hum" : 68,

"humSafe" : "Safe",

"dewp" : 17.340000,

"rawir" : 0.620000,

"abspress" : 957.437500,

"relpress" : 1023.970925,

"pressureSafe" : "Safe"

}

📷 Capture d’écran 2026-06-17 à 23.46.07.pngCapture d’écran 2026-06-17 à 23.46.07.png

Respectful
Alex Nicholas avatar
Alex Nicholas avatar

The only thing in the file there that stands out, is that all sensors have a sensorSafe property, that is set to ”Safe” except for "gust" which is set to "4", but has no corresponding "gustSafe": "Safe"

Helpful Concise
Frédéric Ruciak avatar
Frédéric Ruciak avatar

Jean-Michel, I don’t think it is coming from this because there is no trigger for windgust but only wind and the wind limit is set to 29 km/h “windsafe”: “safe” and the aggregated indicator in this json file is “safe” and shows 1. It is the only one looked at by the safety monitor. Do you still have the AAG CW ASCOM driver?

Jon Woodhead avatar
Jon Woodhead avatar

Frédéric - I have the exact same set-up (Cloudwatcher-Solo-NINA) and no issues. My ‘Cloudwatcher ASCOM set-up’ screen looks like Jean-Michel’s and unlike yours… I guess this strongly implicates the most recent driver in your problem?

Probably best to contact LunaticoAstro if you can’t find any relevant info on their forum?

Jon

Well written Helpful Respectful Concise Engaging Supportive
Frédéric Ruciak avatar
Frédéric Ruciak avatar

Hi all, thank you for your answers I found the solution thanks to Gemini (neither claude nor OpenAi pointed out the potential problem).

The symptom:

I have the solo and I point the json file which is on a mapped drive as it is on the solo connected on the LAN.

Once the weather station was connected, windows locks the file. Consequently, the safety monitor cannot access it despite the message “data looks great”

The solution:

let the safety monitor and weather conditions access to the file with two different mechanisim:

The safety monitor is connected to the file with the AAG safety monitor, points the file, “data looks great” connect and the safe tick immediately apperas :-)

the weather conditions is connected to the file with the observing conditions hub of ASCOM. in the configuration window, every item is associated with the AAG weather conditions driver check the data “data looks great” and then connect

Now both equipements works weather conditions and safety monitor.

According to gemini the ideal would have been to connect directly on the lan but for an unknown reason there is no way to get the lan address of my solo to be recognized in the dedicated line of the driver either with the lan address or the name of my solo.

But I found a way to configure and let it work.

By the way, I chose to have the direct link from the Roll Over Roof controler Talon6 to my 10micron mount with a TAPI interface and whatever happens, AAG CW will trigger an unsafe condition to Talon6 that will first park the mount and once parked (detected with magnetic sensors) it closes the roof.

Clear skies, Frédéric