In CLI mode seems to be ok. Learning RF Frequency, press and hold the button to learn... Found RF Frequency - 1 of 2! You can now let go of the button Press enter to continue... To complete learning, single press the button you want to learn Found RF Frequency - 2 of 2 ...

Done already several times, unsuccessfully. Mustr be something related to plugin configuration, as over IR it works.
Broadlink focus on the right frequency, as if I press remote when in Sweep mode, Learn button is activated.

If I click on LEARN after is already activated from the previous step, LEARN goes off. If I press again on it, nothing happen when I press the button on the remote.
No mater what I try, Test button cannot be activated, same for Save.

I press on Sweep and click on RF remote button. Learn button is activated and red light on the RP Pro goes off. I press again the RF remote button, but nothing happen. Learn button remain activated.

This is what I said, I cannot learn/save a RF command. When I click on Sweep and then press a button on the RF X10 remote, the Learn button is activated. Pressing on it do nothing, same if pressing on Save. What's the right procedure to learn RF devices? For IR devices seems to work.

For me the interface looks different.

I have a RM2 Pro and installed the plugin successfully. I want to add a new RF device (an X10rf remote), but no device is created after clicking on save. What's the normal procedure to add a new RF command?

Thank you.

I've solved the issue based on the suggestion from here: https://github.com/YosysHQ/nextpnr/issues/214 It was just about removing the file CMakeCache.txt and rebuilding the release version. Now I get the following when compiling. -- Found PythonInterp: /usr/bin/python3.4 (found suitable version "3.4 ...

Is enabled in CMakeLists.txt. option(USE_PYTHON "Use Python for Plugins and Event-Scripts" YES) IF(USE_PYTHON) find_package(PythonInterp 3.4) find_package(PythonLibs 3.4) IF(PYTHONLIBS_FOUND) MESSAGE(STATUS "Python3 includes found at: ${PYTHON_INCLUDE_PATH}") INCLUDE_DIRECTORIES(${PYTHON_INCLUDE ...

Yes, both are enabled.
I have two Domoticz installations on two separate CentOS 7 servers and the behavior is the same. Python installation is not recognized.

As you can see, nothing about plugins. 2019-09-05 10:50:04.356 Status: Startup Path: /home/domo/domoticz/ 2019-09-05 10:50:04.366 Status: WebServer(HTTP) started on address: :: with port 8282 2019-09-05 10:50:04.368 Status: WebServer(SSL) started on address: :: with port 4343 2019-09-05 10:50:04.369 ...

I cannot compile the beta version because of some errors. I've tried release version on a different CentOS 7 server with the same results: python installation not recognized. I have both python 34 and 36 (including libs and devel). What is needed for a python installation in order to be recognized ...

No, I didn't tried. Can I revert to the stable version, if something is going wrong, without losing the configuration?

Hi, I'm struggling for weeks to make the plugins work on my Domoticz installation. I'm using CentOS 7(3.10.0-957.27.2.el7.x86_64), Domoticz 4.10726 and the following python packages installed: python36-3.6.8-1.el7.x86_64 python36-libs-3.6.8-1.el7.x86_64 python36-devel-3.6.8-1.el7.x86_64 # python3 -V ...