Forums

Resolved
0 votes
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 and report back in this thread if you were successful or had any problems.

To install (or update your existing testinstallation) do this from the ClearOS machine commandline:
yum install --enablerepo=clearos-contribs-testing domoticz libopenzwave


/Fred
Saturday, May 09 2020, 03:36 PM
Share this post:
Responses (14)
  • Accepted Answer

    Wednesday, April 14 2021, 04:21 PM - #Permalink
    Resolved
    0 votes
    Fredrik Fornstad wrote:

    @Nick,
    1. As I suspected there are some packages that needs to be made available in Koji/mock before the new build will succeed. I sent an email request.

    Replied. I think the spec file may need adjusting.

    2. I will try to take a look at your stellar spec file (the gitlab link is access restricted, but I can download the src.rpm from "updates-testing" repo and unpack it) during the weekend or so. But please understand that I am not an expert ;) . Here is a good documentation on packaging: Fedora packaging Guidelines where you will find good info. For %build and other scriptslets, look here: RPM Scriptlets.
    Just about anyone is more expert than me! I've poured over docs in the past and I find it heavy going. As far as I can make out, %build is just a section header rather than a macro. I've added it to my builds at home, but don't want to push as it will need a version bump for such a trivial change.

    [edit]
    I am not sure why the gitlab is restricted. I'll need to look at that.
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 14 2021, 04:03 PM - #Permalink
    Resolved
    0 votes
    @Nick,
    1. As I suspected there are some packages that needs to be made available in Koji/mock before the new build will succeed. I sent an email request.
    2. I will try to take a look at your stellar spec file (the gitlab link is access restricted, but I can download the src.rpm from "updates-testing" repo and unpack it) during the weekend or so. But please understand that I am not an expert ;) . Here is a good documentation on packaging: Fedora packaging Guidelines where you will find good info. For %build and other scriptslets, look here: RPM Scriptlets.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 14 2021, 09:05 AM - #Permalink
    Resolved
    0 votes
    Fredrik Fornstad wrote:

    OK, as I suspected this was not going to be easy. If you really want to build packages yourself my advice is that you start with a much easier package... :)

    Domoticz has always been on the bleeding edge when it comes to dependencies on system components and this time it is "worse" than it ever was. It now requires a much more modern version of C-compiler, Cmake, OpenSSL, Boost library etc than what is (normally) available in ClearOS 7. After hours of trial and errors I think I now have a method do to this in a way that will be compatible with the rest of the ClearOS platform and its Koji build environment.

    But before I go ahead and make a test-build I need to understand if a few additional packages and a clearos-repositoriy that I have not used before are available for my build in Koji.I am currently waiting for some input on that.

    Given this, I will likely make a first test-build in about one week from now, and I expect to face some more challenges at that time too. So my best guess right now is that there might be a Domoticz "beta" version in contribs-testing repo in about 2 weeks from now. I will post in this thread when it is ready for testing.

    /Fred

    Hi Frederick,

    I was already afaid it would not be easy. The previous update was to my knowledge also not easy.
    Would be great i you can succeed, espacially when a new stable version will be released this can be a good test-case ;)
    Centos7 is not helping as far i can see a lot of the packages are outdated at the moment.

    Again, I appreciate your effort a lot.
    Let me know if i can help with something
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 14 2021, 08:25 AM - #Permalink
    Resolved
    0 votes
    Openssl11 is an epel package and seems to be separate from openssl.

    When trying to get stellar-core going, I had to push an update to the mock configs to enable the SCLo repos. This helped the build system and Shad, I think, had to do another tweak.

    BTW, I am still finding my way here. Can you have a quick look at my spec file as I don't have a %build in it, so it looks like everything is after the %prep section. Should I have a %build section before the autogen.sh line? Does %build do anything or is it just a convenient separator?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 14 2021, 08:11 AM - #Permalink
    Resolved
    0 votes
    @Nick,
    Thanks for the info. This is more or less the same method that I have used. However I need the devtoolset-9 and openssl11 packages. And talking about throwing the full book at it: I put the entire %build section in a scl enabled shell...

    Since you obviously have been using the SCLo repos, (and I assume openssl11 from epel is available), then I will go ahead and make a try real soon... :) Just need to prepare for the domoticz build with an updated libopenzwave build that needs to be in place first.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 14 2021, 07:33 AM - #Permalink
    Resolved
    0 votes
    @Fredrik, note that there are more modern compilers available in the SClo repos. I've been using llvm-toolset-7 which has later Clang and C++ in it, I believe. You can see how I did it in the stellar-core app at https://gitlab.com/clearos/clearfoundation/stellar-core/-/blob/master/stellar-core.spec. Note that when I did:
    scl enable llvm-toolset-7 ./autogen.sh
    scl enable llvm-toolset-7 '%{configure} --disable-postgres --docdir=/usr/share/doc/%{name}-%{version}'
    scl enable llvm-toolset-7 make
    I probably didn't need it for all three lines, but as each compile took 1h, I just threw the book at it.

    On my server I also have a version of stellar-core with postgresqs12 from the SCLo repos, this is a bit more more complicated and the relevant bits of the spec file I have are:
    Requires: rh-postgresql12

    BuildRequires: rh-postgresql12-postgresql-devel
    BuildRequires: rh-postgresql12
    BuildRequires: llvm-toolset-7

    export libpq_CFLAGS=/opt/rh/rh-postgresql12/root/usr/lib64/libpq.so.rh-postgresql12-5
    export libpq_LIBS=/opt/rh/rh-postgresql12/root/usr/lib64/libpq.so.rh-postgresql12-5

    scl enable llvm-toolset-7 rh-postgresql12 ./autogen.sh
    scl enable llvm-toolset-7 rh-postgresql12 '%{configure} --docdir=/usr/share/doc/%{name}-%{version}'
    scl enable llvm-toolset-7 rh-postgresql12 make
    I have the first running building through the build system OK. I have not tried the second in the build system as I am hoping to be able to just use the sqlite3 database as it makes things easier. The second builds fine in mock and I see no reason that it would not build OK in koji.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, April 13 2021, 06:58 PM - #Permalink
    Resolved
    0 votes
    OK, as I suspected this was not going to be easy. If you really want to build packages yourself my advice is that you start with a much easier package... :)

    Domoticz has always been on the bleeding edge when it comes to dependencies on system components and this time it is "worse" than it ever was. It now requires a much more modern version of C-compiler, Cmake, OpenSSL, Boost library etc than what is (normally) available in ClearOS 7. After hours of trial and errors I think I now have a method do to this in a way that will be compatible with the rest of the ClearOS platform and its Koji build environment.

    But before I go ahead and make a test-build I need to understand if a few additional packages and a clearos-repositoriy that I have not used before are available for my build in Koji.I am currently waiting for some input on that.

    Given this, I will likely make a first test-build in about one week from now, and I expect to face some more challenges at that time too. So my best guess right now is that there might be a Domoticz "beta" version in contribs-testing repo in about 2 weeks from now. I will post in this thread when it is ready for testing.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 09 2021, 06:58 AM - #Permalink
    Resolved
    0 votes
    Fredrik Fornstad wrote:

    Building new versions of Domoticz can be quite challenging depending on what have changed. I will take a look at it, but I make no promise...
    /Fred

    Hello Frederik,

    I appreciae your effort very much.
    I've tried to compile it my self, but no luck. It stops in the Make process somewhere
    It was challeges to get all the new version of some packages and it was my first time compiling a packages.
    If you have some guidens i could also try it again.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 08 2021, 08:22 PM - #Permalink
    Resolved
    0 votes
    Building new versions of Domoticz can be quite challenging depending on what have changed. I will take a look at it, but I make no promise...
    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 08 2021, 01:51 PM - #Permalink
    Resolved
    0 votes
    Hello Frederik,

    Is there a possibility to have a recent Beta version of Domoticz od maybe some guidens howto upgrade to a Beta version.
    I'm getting a error within my Domoticz with a plugin which probobly is solved in a Beta version.
    Getting the error is not the biggest problem, but it restart my Domoticz each time.
    The error which is cauisng the restart is :
    Error: Domoticz(pid:35175, tid:35222('Plugin_ASIO')) received fatal signal 11 (Segmentation fault)


    I've found on the French Domoticz forum that this is solved in Build 12934

    This a copy of my error in the log

    2021-04-03 19:02:35.918 Status: User: Admin initiated a switch command (494/Somfy - Erker Blok 2/Off)
    2021-04-03 19:02:35.920 (Dummy Schakelaars) Light/Switch (Somfy - Erker Blok 2)
    2021-04-03 19:02:35.973 Status: dzVents: Info: -=# Screens #=-: ------ Start internal script: Screens Erker Blok 2: Device: "Somfy - Erker Blok 2 (Dummy Schakelaars)", Index: 494
    2021-04-03 19:02:35.975 Status: dzVents: !Info: -=# Screens #=-: Screens Erker blok 2 dicht
    2021-04-03 19:02:35.975 Status: dzVents: Info: -=# Screens #=-: ------ Finished Screens Erker Blok 2
    2021-04-03 19:02:36.012 (Somfy Tahoma) Sending command to tahoma api
    2021-04-03 19:02:36.012 (Somfy Tahoma) Sending command to tahoma api
    2021-04-03 19:02:36.012 (Somfy Tahoma) Sending command to tahoma api
    2021-04-03 19:02:36.828 (Zwave USB) Light/Switch (PIR Sensor)
    2021-04-03 19:02:36.829 Status: OpenZWave: Alarm received (Home Security: Motion Detected at Unknown Location), NodeID: 31 (0x1f)
    2021-04-03 19:02:36.833 (Zwave USB) General/Alarm (PIR Alarm Type: Home Security 7 (0x07))
    2021-04-03 19:02:36.839 (Zwave USB) Light/Switch (PIR Home Security)
    2021-04-03 19:02:36.882 (Zwave USB) Light/Switch (PIR Sensor)
    2021-04-03 19:02:38.220 Error: Domoticz(pid:35175, tid:35222('Plugin_ASIO')) received fatal signal 11 (Segmentation fault)
    2021-04-03 19:02:38.220 Error: siginfo address=0x12b00008967, address=0x7f423ae454fb
    2021-04-03 19:02:38.588 Error: Thread 12 (Thread 0x7f41ff7fe700 (LWP 35222)):
    2021-04-03 19:02:38.588 Error: #0 0x00007f423ae451d9 in waitpid () from /lib64/libpthread.so.0
    2021-04-03 19:02:38.588 Error: #1 0x000000000067c3c5 in dumpstack_gdb(bool) ()
    2021-04-03 19:02:38.588 Error: #2 0x000000000067c96e in signal_handler(int, siginfo_t*, void*) ()
    2021-04-03 19:02:38.588 Error: #3 <signal handler called>
    2021-04-03 19:02:38.588 Error: #4 0x00007f423ae454fb in raise () from /lib64/libpthread.so.0
    2021-04-03 19:02:38.588 Error: #5 <signal handler called>
    2021-04-03 19:02:38.588 Error: #6 0x00007f41e4678560 in ?? ()
    2021-04-03 19:02:38.588 Error: #7 0x00007f423b72e891 in BIO_write () from /lib64/libcrypto.so.10
    2021-04-03 19:02:38.588 Error: #8 0x00000000009bbda6 in boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::executor>, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, Plugins::CPluginTransportTCPSecure, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<Plugins::CPluginTransportTCPSecure*>, boost::arg<1> (*)(), boost::arg<2> (*)()> > >::operator()(boost::system::error_code, unsigned long, int) ()
    2021-04-03 19:02:38.588 Error: #9 0x00000000009bd28b in boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::executor>, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, Plugins::CPluginTransportTCPSecure, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<Plugins::CPluginTransportTCPSecure*>, boost::arg<1> (*)(), boost::arg<2> (*)()> > >, boost::asio::detail::io_object_executor<boost::asio::executor> >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()
    2021-04-03 19:02:38.588 Error: #10 0x000000000077f03c in boost::asio::detail::scheduler::run(boost::system::error_code&;) ()
    2021-04-03 19:02:38.588 Error: #11 0x000000000099dc71 in Plugins::BoostWorkers() ()
    2021-04-03 19:02:38.588 Error: #12 0x0000000000ae6396 in thread_proxy ()
    2021-04-03 19:02:38.588 Error: #13 0x00007f423ae3dea5 in start_thread () from /lib64/libpthread.so.0
    2021-04-03 19:02:38.588 Error: #14 0x00007f42394709fd in clone () from /lib64/libc.so.6
    2021-04-03 19:03:08.878 Status: Domoticz V2020.2 (c)2012-1970 GizMoCuz
    2021-04-03 19:03:08.878 Status: Build Hash: 0, Date: 1970-01-01 01:00:00
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 10 2020, 05:32 PM - #Permalink
    Resolved
    0 votes
    Hi,
    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.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 02 2020, 04:41 PM - #Permalink
    Resolved
    0 votes
    Domoticz-2020.2-1 and libopenzwave-1.6.1114-3 are now released and found in clearos-contribs.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 24 2020, 01:31 PM - #Permalink
    Resolved
    0 votes
    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:
    yum install --enablerepo=clearos-contribs-testing libopenzwave

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 10 2020, 12:26 PM - #Permalink
    Resolved
    0 votes
    Fredrik Fornstad wrote:

    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 and report back in this thread if you were successful or had any problems.

    To install (or update your existing testinstallation) do this from the ClearOS machine commandline:
    yum install --enablerepo=clearos-contribs-testing domoticz libopenzwave


    /Fred

    Hi Fred,

    The update went smootly and until now no problems
    It installed also some dependency packackages

    Dependencies Resolved

    =====================================================================================================================================================================================
    Package Arch Version Repository Size
    =====================================================================================================================================================================================
    Updating:
    domoticz x86_64 2020.2-1.v7 clearos-contribs-testing 10 M
    libopenzwave x86_64 1.6.1114-3.v7 clearos-contribs-testing 11 M
    Installing for dependencies:
    cereal-devel noarch 1.2.2-1.el7 clearos-epel-verified 207 k
    libwebsockets x86_64 3.0.1-2.el7 clearos-epel-verified 118 k
    mosquitto x86_64 1.6.8-1.el7 clearos-epel-verified 283 k



    The devices which i needed to reconnect after the upgrade to 2020.1 are now still alive and working after the upgrade to 2020.2.


    Good job and thanks again
    The reply is currently minimized Show
Your Reply