Wow, that NG Driver is a really mess and the whole sensor readings are wrong mapped in the driver.

I analyzed the issue, and my device returns two additional answers on the Humidity request:

[2022-08-01T11:53:12.973 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] sendCloudwatcherCommand(V!,2) "
[2022-08-01T11:53:13.964 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] getCloudWatcherAnswer(!w 0! 0,2) = valid "
[2022-08-01T11:53:13.965 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] sendCloudwatcherCommand(h!,2) "
[2022-08-01T11:53:14.188 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] skip answer !d 255!e 255 2 "
[2022-08-01T11:53:14.236 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] skip answer !f 255!g 255 2 "
[2022-08-01T11:53:14.268 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] getCloudWatcherAnswer(!hh 65535! 0,2) = valid "
[2022-08-01T11:53:14.269 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] sendCloudwatcherCommand(p!,2) "
[2022-08-01T11:53:14.317 UTC DEBG ][ org.kde.kstars.indi] - AAG Cloud Watcher NG : "[DEBUG] getCloudWatcherAnswer(!p 65535! 0,2) = valid "

Read More...