Nick Howitt wrote:

@Fredrik, the build has failed. It looks like the certificate for https://pilotfiber.dl.sourceforge.net/project/boost/boost/1.72.0/boost_1_72_0.tar.bz2 has expired.

Yes, that download mirror is no longer good. I have updated the source file to fetch it from another mirror. I pushed the updated files to ClearOS build system, but Koji yet again needs a push from someone...

/Fred

@Fredrik, the build has failed. It looks like the certificate for https://pilotfiber.dl.sourceforge.net/project/boost/boost/1.72.0/boost_1_72_0.tar.bz2 has expired.

Can somebody from Clear get the Koji working so the update will be pushed to the repositories?

Thanks !

Fredrik Fornstad wrote:

Hi,
Actually I have made an update to 2022.1 that I have uploaded during the weekend. However, since quite a while back the build system (Koji) used by ClearOS has some hickups, and now it seems worse than ever and it has therefore not "discovered" my upload at all. In fact it has not built anything for 3 weeks.

When it was fully working it would automatically build and put the Domoticz package in contribs-testing, but for the last year or so, I have had to contact Nick every time so he could get the build going as he had access to systems that I do not. With Nick gone, without anyone else replacing him for the moment, I have reached out to a person that (at least before) used to be involved on an occasional level (once or twice a month I think). He has all the required knowledge to trigger the build.

So I have not given up, I am just waiting for someone on the "inside" to respond.

/Fred

Great. Now waiting on somebody at COS to get in action

Hi,
Actually I have made an update to 2022.1 that I have uploaded during the weekend. However, since quite a while back the build system (Koji) used by ClearOS has some hickups, and now it seems worse than ever and it has therefore not "discovered" my upload at all. In fact it has not built anything for 3 weeks.

When it was fully working it would automatically build and put the Domoticz package in contribs-testing, but for the last year or so, I have had to contact Nick every time so he could get the build going as he had access to systems that I do not. With Nick gone, without anyone else replacing him for the moment, I have reached out to a person that (at least before) used to be involved on an occasional level (once or twice a month I think). He has all the required knowledge to trigger the build.

So I have not given up, I am just waiting for someone on the "inside" to respond.

/Fred

Hi Fred,

Now Nick is not available any more to support us, I was wondering if it still possible to make an update of this package
Are you still intend to make a new package of Domoticz for ClearOS?

If the repositories are now available maybe you can share the rpm. file

The hope for an update relies know a bit on your support

Hi guys,
I am not going to post much more now (unless things change) as Michael has terminated my contract when I declined his mandated new terms.
If you do do something with node.js, there is a bit of a hill to climb. Using npm is a no-no. Then have a look at the Fedora packaging guidelines for node.js.
You'll then have to find someone to release your package. I can't. If Shad responds, he may. At the point my contract was terminated, there was no one else around who could do it.

Glad to hear you're still supporting the pack

Is it possible to make 2 builds?
1 version with Libopenzwave and 1 version with zwave-js.
Then the upgrade for the current users is not an issue and if you want to switch you can do this manually or you can choose which version you want from a new installation
If Libopenzwave is no longer managed, the zwave-js version can be continued for future releases. The Libopenzwave will then no longer be updated

I'm also very interested in the zwave-js version, but since domoticz with Libopenzwave works quite stable, I'm very careful about switching
Also of course installing is difficult because you have to compile the package

If you have time to make a new version, I'll test it again for you

Yes a new version of Domoticz have been released upstsream. This time I think there are no major changes on the build requirements, so I think it should be a fairly easy process. I expect it needs a couple of extra patches but nothing major. And as always, I like to wait a couple of weeks to see that it does not have any major hickups...

But even if it is easy put together the new Domoticz package there is something I want to sort out first:
Many people, including myself, have a z-wave network connected to the Domoticz server. Up until now it has been using libopenzwave as driver (which I also maintain for ClearOS) with a lot of built in functionality in Domoticz itself. But libopenzwave is a more or less abandonned project upstream and the Domoticz team (and others) have moved on to the very new open source initiative zwave-js which is a node-js based driver together with zwavejs2mqtt acting as a mqtt gateway inbetween.

This creates a few things to consider:
1. zwave-js and zwavejs2mqtt needs to be packaged for the ClearOS environment. But since they are based on node-js based they cannot just be compiled and released as if they would have been written in C or similar. They need the node-js environment too. I have a feeling that running these in a docker container would be the easiest thing, but then docker is needed... I myself have no expericence with Docker and I guess it will need to be tested for different scenarios including when the whole ClearOS machine is runnning in a container. Is it bad to run a docker system inside a docker container?
2. Domoticz can not run libopenzwave and zwave-js in parallell, so any old user will need to do a "hard" switch if they want to use the new setup. General instructions are found on the Internet, but still I feel I need to make sure that an upgrade does not "kill a working system" for someone that just happen to receive the new Domoticz release in an auto-update.
3. Zwave-js have recently also added a websocket interface, omitting the need for a mqtt gateway running. This is actually the recommended way to use it by the people that develop zwave-js if I understand it correctly. However, status right now is that Domoticz has not implemented support for that and have just fixed an autodiscovery MQTT implementation leading up to the release a few days ago. I would hate to see a switch by the Domoticz team to the websocket method if/when I just have implemented the mqtt way in ClearOS... (Do not want to bet on the wrong horse)
4. Since this new setup means adding Docker (likely), zwave-js and zwavejs2mqtt into the equation, Therefore I also need to think about if the app-domoticz in ClearOS needs to be expanded with new functionality to run and manage the whole "domoticz environment".
5. On the (very) positive side though is that zwave-js has a very active community and have managed in a very short time period to implement many more functions than what libopenzwave provides. Also, compared to libopenzwave that was built by reverse engineering the z-wave protocol, the zwave-js developers have had access to the now publicly available zwave specifications allowing them to build it in a proper way. From the reports that I have seen it seems to perform better than libopenzwave already today. I did take it for a test-spin a couple of weeks ago and it did work without problems for my small test system. However I did notice new behaviours compared to libopenzwave that I did not like for some sensors even if I am pretty sure zwave-js do it by the book and it is actually libopenzwave doing it wrong...

So to sumarize: Yes you can expect a new release of Domoticz in ClearOS. I just need to think and play around with it a little bit first.

/Fred

Hio Fred,

Maybe you have seen it already, but there is a new release of Domoticz stable
Are you still able to make a COS7 version or are we getting dependency problems?

Fredrik Fornstad wrote:

OK, just as I expected: For some reason the fail2ban process no longer identify itself as "f2b" anymore. Instead it now uses "fail2ban". I therefore need to change app-domoticz so it check if "fail2ban" is running instead of "f2b". I will try to fix this early next week.

Note: There are no "real" problem here. As long as fail2ban is running, everything is fine. It is just that app-domoticz is indicating a "false" alarm when it can not find "f2b" running...

/Fred

Hi Fred,

The app has been update to v4.3 and the message is now disappeared.

Thanks !!

OK, just as I expected: For some reason the fail2ban process no longer identify itself as "f2b" anymore. Instead it now uses "fail2ban". I therefore need to change app-domoticz so it check if "fail2ban" is running instead of "f2b". I will try to fix this early next week.

Note: There are no "real" problem here. As long as fail2ban is running, everything is fine. It is just that app-domoticz is indicating a "false" alarm when it can not find "f2b" running...

/Fred

Most likely fail2ban have changed something so that app-domoticz no longer detect if it is running or not. I will try to look into this tonight.

/Fred

I don't know if it is relevant, but f2b recently updated twice and introduced some bugs. There is now a fix but I have no idea when it will be pushed into EPEL upstream.

Hello Frederik,

The Domoticz server is still running very stabel on my ClearOS system.
I noticed recently a message within the app-domoticz the attack-detector was not running, but the fail2ban service is running

Attack Detector for Domoticz is enabled but the Attack Detector service is not running.

service fail2ban status

Redirecting to /bin/systemctl status fail2ban.service

● fail2ban.service - Fail2Ban Service

   Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled)

   Active: active (running) since Wed 2021-11-03 09:59:16 CET; 3 days ago

     Docs: man:fail2ban(1)

 Main PID: 16293 (fail2ban-server)

   CGroup: /system.slice/fail2ban.service

           └─16293 /usr/bin/python2 -s /usr/bin/fail2ban-server -xf start

What could this be ?

After two months without any major problems reported upstream or in this forum I have asked the ClearOS team to release Domoticz 2021.1 and an updated OpenZwave lib for ClearOS 7 now. It will will show up in the mirrors within 1-2 hours

/Fred

Fredrik Fornstad wrote:

@Patrick:
Maybe what you experienced is related to this:
Domoticz GitHub Issue # 4800

A update from libopenzwave 1.4 to 1.6 is mentioned as a probably cause, but that should not have been in your case as I guess your old libopenzwave version was 1.6.1114-3 (and your new version should be 1.6.1869-1)

/Fred

Almost the same problem.
My hardware with the names and the descriptions are still there.
Only the ID’s are set to 0x0000, but with refresh node they are coming back. Only the battery operated not yet, but still takes more time

I’m indead already on libopenzwave 1.6.
I know there were a lot problems going from 1.4 to 1.6


Other question.
I see the following in rhe About tab

 Version: 2021.1

Build Hash: 0

Compile Date: 1970-01-01 01:00:00

dzVents Version: 3.1.7

Python Version: 3.6.8 (default, Nov 16 2020, 16:55:22) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]

Compile date 1970 ?? Is this your compile date

@Patrick:
Maybe what you experienced is related to this:
Domoticz GitHub Issue # 4800

A update from libopenzwave 1.4 to 1.6 is mentioned as a probably cause, but that should not have been in your case as I guess your old libopenzwave version was 1.6.1114-3 (and your new version should be 1.6.1869-1)

/Fred

Interesting... I have not experienced that.

I have tested on 2 machines, both using an UZB-stick (gen 5) and that have worked without any problems.

Battery powered devices will usually take some time to interview depending on when the wake up next time.

/Fred

I've update my production server today (my clone) and the update was successfull.

The devices are showing up, but they have all

ID 0x0000 and Type 0x000

To resolve this you have to remove the.xml file

service domoticz stop

cp ozwcp.poll.XXXXXX.xml ozwcp.poll.XXXXXX.xml.bak

rm ozwcp.poll.XXXXXX.xml

service domoticz start

After this the file will be rebuild slowly.
Still not all my battery operated devices have been recovered, but they are working.

Ok. First update.

I did a update on a VM image with only clean Domoticz installed (no sensors, etc....) and the update went smoothly

Then I did an update on my test server with a clone of my production server (from 2 months ago) and the update went without any problems.
Domoticz is starting and running. The only thing i noticed is thay my Zwave hardware list is empty. Maybe because the zwave USB is not in the server, but i'm not sure.

Tommorow is will make a new clone of my production server and will check if the zwave devices are still working.

Discussing with Nick right now on how to do this. I think we (or rather Nick...) knows how to do this now. A domoticz package should therefore show up in clearos-contribs-testing soon (maybe even today).

Please remember this is still a beta, so be a bit careful before you do this for a "production environment".

1. Take a backup of all configuration files you have related to domoticz and its sub-components that you may be using. The domoticz update should make its own backup in /var/domoticz, but just to be sure... As stated earlier, the new domoticz does have a different format of the database making it impossible to go back to the old version without also restoring the database to its old state.
2. Logged in as root, Execute the following command:

yum update --enablerepo=clearos-contribs-testing domoticz libopenzwave

(If you are using rtl_433 then I suggest you update that one to by adding " rtl_433" to the command line above

/Fred

Sorry for not responding faster... busy with other stuff. I will try to cooperate with Nick on a workaround ASAP (hours). Nick will then need to do some manual work...
/Fred

There is a problem with the build system to get it to build this package which will take many hours to fix so may not be viable. I gave Fredrik an alternative yesterday and I'm waiting to hear from him.

Hello Frederik,

I was very curious if you have succeed or positive progress in building the new package for COS.
It is not my intention to push you and understand fully this is costing time and that time limited.

Unbelievable Fred that you have managed to make it working on COS7 !
Great job and I agree to wait untill the 2021.1 stable is indeed stable.
The first hotfix has already been released

Hopely you will be succesfull to build it in the repos also.