Not sure if I am the right guy to try to answer your question(s). But to maybe better understand how things work I will try to describe below a bit more detailed than you asked for...
I develop/maintain the "wrapper" that installs Serviio using the ClearOS marketplace. It is called "app-serviio" and I update it if/when Serviio (or ClearOS) changes so installations and controlling (enable/disable the serviio service from the ClearOS webconfig page) is still possible. For the last few releases Serviio has not changed its behaviour so there has not been any reason for me to make any update of app-serviio. The app-serviio version number is NOT the same as the version number of the actual serviio program. The Serviio Pro license is connected to Serviio, not to app-serviio.
The serviio program itself, and its roadmap is entirely done upstream. I do however, package it into a serviio.rpm package for ClearOS whenever upstream releases a new version. Now, a bit more than a year ago, upstream decided to go for a Serviio 2.0 release. With it came also the requirement to buy a new Pro license as the old from "1.x" is not valid for "2.x". I did what I normally do: packaged the new serviio-2.0.rpm but faced a problem that is a bit problematic: The way ClearOS is setup (for most users) is that there will be automatic updates whenever a newer package is available in the ClearOS repos, and there is "no way back". IF I would have requested the ClearOS team to put the new serviio 2.0 package in the normal contribs repo (and subsequently contribs-verified later on), that would have forced anyone with a Pro licence on a ClearOS platform to having to buy a new license even if they were happy to stay where they were.
My solution at the time, and this is still the situation, was to "just" build serviio-2.0.rpm and leave it sitting in the contribs-testing repo (from which no one should do automatic installations from). In that way, anyone who really wanted the 2.0 (and now 2.1) version could manually upgrade if they wanted to, but it would be a very active decision from their point of view. And yes, it does require a bit of command line. Regarding the stability, I have not tested it personally on a Home (or business) system so I can not make a firm promise. But I do not see any problem as the serviio package itself is pretty stand-alone from the rest of the system.
Now, I did have a discussion with Nick a month or two ago, if it is about time to "force" the Serviio 2.x upon all the ClearOS users by moving it to the contribs repo. We never really finished that discussion, and maybe it is time to take an active decision.
The ClearOS Serviio "webconfig-app" is just a shell to start/stop and control Serviio in the ClearOS environment. Since there is no API-change in Serviio 2.x from the 1.x versions, this shell did not need any update, so it is still version 1.8 (its versioning is not really connected to serviio releases).
So everything is as it is meant to be.
In the latest update of app-domoticz, available as a paid app in the ClearOS marketplace, there is now support for using a RTL2832 based DVB-T USB dongle together with Domoticz. It will use the TV dongle as a software defined radio, and receive data from just about any temp, humidity, wind speed and pressure sensor operating at 433 MHzr that you may have in your home. Depending on your antenna and the location, the range can be up to 100 meters or so. Most(?) cheap wireless temperature and weather stations, like the ones from Oregon Scientific etc, operate at 433 MHz unencrypted and can therefore be detected with this setup. Depending on your needs this can be very helpful to include in your home automation project when designing rules that should take weather data into consideration.
What you need:
- Domoticz from the ClearOS marketplace running on a physical computer at your location
- RTL-2832 based USB dongle. You can find cheap ones from USD 10, but I would recommend RTL-SDR Blog V3 which cost around USD 20.
- Antenna (typically for 433 MHz, but there are sensors operating at other frequncies too such as 866 MHz). Try to get a bundled antenna with the USB stick but any cheap antenna (for the right ferquency) works, or in worst case just a insulated wire about 34 cm (a foot) long connected to the center pin of the antenna connector (for 433 MHz)
How to use: IMPORTANT: do not install the USB stick before step 2.
1. First in ClearOS webinterface, navigate to Server -> Applications -> Domoticz Home Automation
2. Edit the configuration page and make sure "Enable RTL_SDR" = "true" , press save
3. Now you can insert the RTL2832 based USB dongle into your computer. NOTE: If you inserted the USB-dongle before setting "Enable RTL_SDR" = "true" then do NOT remove it when your machine is running, as it then using the built in Linux drivers for the TV receiver. Removing it in that state may cause kernel panic... Instead power-off your computer and then remove it.
4.Open a window to Domoticz own webinterface -> go to hardware and add your USB stick. Scroll down to "Rtl433 RTL-SDR receiver" in the list of hardware and give it a name. If you are going to use it att 433 MHz you do not need to enter any additional parameters.
5. Within a minute or two you should see new devices pop up in the device tab. The signal strength (0-11) gives you an indication of how good the reception is. 4 is "OK", higher is better.
PLEASE NOTE: depending on your location, you might pick up sensors belonging to your neighbours or tire pressure sensors from cars driving by. Please check laws and regulations in your country to be sure that you only do legal stuff.
6. In the device tab include the sensors that you are interested in and they can then be shown on the dashboard (See example pictures) or used in your house automation rules.
Welcome to the world of software defined radio and house automation
An updated Domoticz has just been released together with updated ClearOS domoticz-app for it. It is still version 2020.2 but has been patched to allow for using a TV-USB stick (RTL-2832 based) to receive wireless sensor data from for instance weather sensors etc in ClearOS. No other change has been made.
I will describe the added functionality in a separate thread.
Serviio version 2.1 is now available for ClearOS 7. If you want to update your existing serviio version you will have to do it manually from command line:
NOTE: Any "Pro licence" that you may have for Serviio 1.x will NOT work with Serviio 2.x , so if you update and still want the Pro-features, then you need to go to http://serviio.org and purchase a new licence.
Since the 2.1 version will make any 1.0 licence unusable, I am planning to keep Serviio 2.1 in contribs-testing and not release it into the normal contribs repo (because then the update will be forced upon everyone that has auto-update on).
OpenZwave have corrected a few issues why I have built a new version. As a bonus, I also fixed so that the log in domoticz now also shows the libopenzwave version correctly. If nothing else pops up within a week or two, then I plan to release the domoticz 2020.2-1 and libopenzwave 1.6.1132-2 packages to the contribs-repo.
To test the new libopenzwave package run:
Domoticz have now been updated to 2020.2.
For the next couple of weeks it will be sitting in contribs-testing for people to try it out before it will be released. Please download and test it. Report any issues in this thread.
To install do this from the ClearOS machine commandline:
OK. the 2020-2 version is on its way.
In order for this to build correctly I had to make a new libopenzwave that does not work with domoticz 2020-1 or earlier versions. This means that during a (hopefully short) time period between the build of libopenzwave and a successful build of the new domoticz that you can not install domoticz from clearos-contribs-testing. Installations of the old domoticz from the standard contribs library works without problem.
The new libopenzwave is just built in contribs-testing and on its way to the mirrors. When that is done and it is also available in the build system, I will starting the build of domoticz 2020-2.
Upstream Domoticz have now released 2020.2 as a "Stable HotFix". Turns out that it is not just a minor adjustment to 2020.1. In the process a number of modules have now been moved outside the software package itself. In principle what has been done is a good thing, but it is (again) a major change that requires quite a bit of adjustment to make it work on ClearOS.
After a few days trouble shooting I think got it working now. I have just updated a local machine that I have and I will run domoticz on it a few days to check that it is stable. It it works OK, then I will try to build it in the ClearOS build system and put it in contribs-testing for a couple of weeks before releasing it.