Forums

Resolved
0 votes
Hi everyone,
Yesterday domoticz 2021.1 was released upstream. Historically, whenever there has been a stable domoticz release and it is rolled out there are things showing up as broken, and therefore yet another stable release has been made within a month from the first one fixing these problems. I do not know how it is going to be this time, but I have no intention to rush a release in ClearOS given these historic experiences.

That being said, I am about to build the new domoticz 2021.1 and have it sitting in the clear7-contribs-testing repo for anyone that want to try it out. For those of you who want to try, please understand that the new domoticz version will update the underlying domoticz database to a new format, which makes it impossible to go back to the old version without restoring the database at the same time. This will require a bit of manual work, or else your existing configuration will be lost.

I have successfully built the new domoticz version locally on my development machine. However, there are still some tweaks needed in the ClearOS build system before the new domoticz package is possible to build for the clear7-contirbs-tesing repo, and I will make another post in this thread when it is ready. Hopefully it is resolved within a couple of days.

/Fred
Sunday, April 18 2021, 05:59 PM
Like
1
Share this post:
Responses (16)
  • Accepted Answer

    Saturday, November 20 2021, 08:47 AM - #Permalink
    Resolved
    0 votes
    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 !!
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 08 2021, 08:36 PM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 08 2021, 06:23 AM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 07 2021, 04:06 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, November 07 2021, 08:26 AM - #Permalink
    Resolved
    0 votes
    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 ?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 22 2021, 03:15 PM - #Permalink
    Resolved
    0 votes
    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
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 07 2021, 12:37 PM - #Permalink
    Resolved
    0 votes
    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 :D
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 07 2021, 11:43 AM - #Permalink
    Resolved
    0 votes
    @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
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 07 2021, 09:36 AM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Friday, May 07 2021, 09:19 AM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 06 2021, 05:21 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 06 2021, 10:53 AM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, May 05 2021, 09:51 PM - #Permalink
    Resolved
    0 votes
    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
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, May 05 2021, 07:17 PM - #Permalink
    Resolved
    0 votes
    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.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, May 05 2021, 01:50 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 18 2021, 06:22 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
Your Reply