Profile Details

Toggle Sidebar
Recent updates
  • Hmm,
    It seems the new version of Domoticz (+ the new version of OpenZWave) uncovered a number of "api missunderstandings" between the two programs. My first hope was to go for a the latest releases of both OpenZWave as well as Domoticz, but they currently do not play along together. A lot of work is ongoing right now to fix this and I will probably wait another week or so until things become much clearer. After all, the current 4.9700 version is rather stable :)

    /Fred

  • Looks as if there will be a new stable release 4.10717 available later today from Domoticz. That version should be better I think. At least the most obvious flaws has been fixed in it. Still, I will wait a little just to be sure before trying to release it in ClearOS.
    /Fred

  • Patrick de Brabander wrote:

    Hi Frederik,

    FYI.
    An new version has been released.

    https://www.domoticz.com/forum/viewtopic.php?f=3&t=27843


    Yes, I know.
    In fact 2 (!) new versions have been released in a couple of days since the first did not work… Same thing goes with OpenZwave library that just fixed their release that did not compile in RHEL/Centos/ClearOS… On top of that they are updating a lot of config files right now (released almost 150 updated files about 6 hours ago), which would be nice to include if possible (I need to test that first).

    I will wait a little bit to be sure these releases are really stable and functioning before trying to release them in ClearOS. We are probably talking about 1-2 weeks.

    /Fred

  • Just got a message from the ClearOS team: The packages have been just been pushed to the repos. It will take 30 minutes or so before it starts to show up at the mirrors.

    /Fred

  • I have asked the ClearOS team to move the packages to the right repos already... So whenever they have time it is just a matter of minutes.

    (I do not have enough authority to do it myself)
    /Fred

  • New version of Domoticz Home Automation 4.9700

    Hi everyone,
    Domoticz version 4.9700 is now available for testing in repo: clearos-contribs-testing It contains a year of added features and bug fixes.

    If no problems shows up, I will try to release it together with an update of the domoticz marketplace app in a couple of weeks.

    Note: The API for logging have changed, so if you decide to test it out before I make the official release, please be aware that logging will not work if you launch/control it with the domoticz marketplace app. After the release, everything shall work as normal.

    /Fred

  • Ok, I found and corrected the problem with the vanishing directory and have issued a new build. Will be released in a day or two.
    /Fred

  • Patrick,
    That should not happen... Not sure why.
    Please make sure domoticz is stopped and then try this from the command line:
    Now I think you should be able to start domoticz in the normal way.

    /Fred

  • How to make your USB devices have persistent /dev/ttyXXXXX address

    Hi everyone,
    If you for instance use Domoticz Home Automation on your ClearOS server, the chance is high that you also have connected one or several USB-dongles for 433MHz communication, Z-wave etc.

    Those USD-dongles that in fact enumerates a traditional serial interface will get an address like

    /dev/ttyACM0 for the first unit and
    /dev/ttyACM1 for the second unit and so on


    Now, by design there will be a race condition at boot time so you can not be 100% sure which physical USB dongle will end up at a specific address. This causes problem in a home automation program such as Domoticz since you need to specify the address for each USB-dongle, and you certainly want your application to continue to work after a server reboot. Similar problem occurs also if you unplug and insert your USB-dongle again. Linux will give it a new address at the insertion if there was an ongoing communication when you unplugged it, why your application will not find it anymore.

    Luckily there is at least one way to bind a USB dongle to a static address (name):
    1. Make sure your USB-dongle is connected to the server
    2. Open a command window and enter:
    3. Note what address the USB-dongle has now (for instance /dev/ttyACM0 )
    4. Find unique identifiers for your USB-dongle (like Manufacturer ID and Product ID) by entering this command (use the address from step 3) The output can look somethings like this:In our case we can see that ATTRS{idVendor}=="0658" and ATTRS{idProduct}=="0200" (which says it is a Z-wave+ UZB USB-dongle from Sigma).
    5. Open/Create a file where we will give this USB-dongle an alias:Enter the following text (using our example):Press Ctrl-o to save and Ctrl-x to exit nano. Note that in this example we used the alias "ttyUSB50", but you could have used "MySigmaUZB" or something. However, I suggest you stick to a "ttyUSBxx" naming convention since that is a "valid" serial port name in Linux so that will save you from some other problems. I also used a "high" number (50) to avoid any potential naming conflict by anything else created in the system.
    6. After reboot of the server our USB-dongle will in addition to its random /dev/ttyACM address now also ALWAYS be found at /dev/ttyUSB50. If you do not want to reboot your server you can enable the new alias by entering the following command: and then unplug/insert your USB-dongle.

    /Fred