Domoticz

2 Raspberries with Domoticz in operation:
1*Raspberry_B and 1*Raspberry_3B+
Both have same (latest) release of Domoticz.
Raspberry_B has DarkSky-widgets for longer time.
Today installed DarkSky-widgets on the Raspberrry_3B+, with same API and same Geo-location as for the Raspberry_B.

A number of common, 'normal' widgets, but to my surprise also a difference in widgets:
- Raspberry_B has SolarRadiation
- Raspberry_3B+ has Ozone.
For both Raspberries have looked under 'Unused Devices' for the apparently, missing device, but negative.

Anybody an explanation for this difference?
And a simple, remedy to get alignment of the DarkSky-widgets on the 2 Raspberries?

Notes
For my Raspberry_3B+ the Ozone-info is an interesting addition, because it might have value for the processing on that machine of the measured dust-info, if info is available about the meaning/background of the ozone-value].

Rummaging through the DarkSky-website, also see that Cloudcover-info is available from DarkSky, apparently not (yet) included under the Domoticz-hardware: not a big deal, but why yourself dissect the JSON-file from DarkSky, or why call the hourly Ogimet data like in this script to calculate solar radiation, if Domoticz easier may provide more frequent info from Darksky?
Obviously under the provision that Darksky-info is at least of same quality as 'official' Ogimet.

Hello,
Are you sure you use the same Domoticz version in the two Raspberry? I use two Domoticz versions (4.97 and 3.5877) in two different platforms and see the same thing as you: in 3.5877 version there is a solar radiation device and in 4.97 this device is ozone. If you look further you will see the values for these two devices are the same. I've concluded at least in my environment that Darksky implementation is wrong in 3.5877 version because the device seems actually an ozone one.

On my Raspberry 2B i have the DarkSky Forecast Ozone Sensor widget with Domoticz V4.79

On both Raspberries I have latest beta-release Domoticz = v4.10619
Indeed, it is strange that the numeric values for Solar Radiation and for Ozone are identical:
that cannot be correct.
In hindsight, that kind of 'discrepancies' for me were reason in the past to discard DarkSky as serious reference info, not considering whether the background reason is errors in the Domoticz-implementation or in DarkSky itself.

I assume you've installed Darksky in a previous version of Domoticz and then upgrade Domoticz up to the latest beta. In the Domoticz platform where you have the wrong solar radiation sensor, remove Darksky and then install again Darksky. After that, I assume you will have the ozone sensor instead of the wrong solar radiation one.

@Antori91

Thanks for the hint.
Always assumed that plugins would be updated/aligned with the releases, but apparently not .......

For read-out from DarkSky is desired for SolarRadiation and CloudCover (etc.), I will have to make my own, separate software for data-extraction from DarkSky and for translation to a Virtual Sensor in Domoticz.

In hindsight good arguments why I did not believe the info from the older installation:
SolarRadiation should be 0 at night, while Ozone also at night is fluctuating around a >>0 level.
However, such experience breeds suspicion.