Hi,

Yes, you got it right, you can also have a look at this topic:
viewtopic.php?f=17&t=1103&start=40

ratjenl wrote: ↑Sunday 13 August 2017 14:54 mine does 5 volt all the time, got it connected on pin40 (GPIO21)

so by putting 5v on a pin that is meant to receive 3.3v you potentially break your pi.

https://learn.sparkfun.com/tutorials/vo ... ll?print=1

Really? Aren't the gpio input pins specified as 3.3v max, not 5v. Measured with an multimeter it says 5.12 v. That's the output pin, you have 5v output. I was talking about the input pin, the wire you connect on PIN 19 as input, is max 3.3volt. How much does the NPN output on that pin when it ...

Do you know if there are any resistors or other components involved in this setup? No resistor needed, just the 3 wires connected to the pi. I ordered this from Ali http://s.aliexpress.com/yUFbiQBZ, makes the connection much easier. Really? Aren't the gpio input pins specified as 3.3v max, not 5v ...

Hi, am reading this on my phone so a bit difficult to see the code properly formatted. Your levelname formatting looks a bit weird. Strcode in brackets with new appended? Other than that is looks ok. Domoticz should not hang by executing the python code. That the web interface does not update is ...

You need python 3

The directory name does not matter. Any name will do as long as the files are readable by the user under which Domoticz runs. The files do not need to be executable, chmod +r is enough.

Verstuurd vanaf mijn XT1562 met Tapatalk

Please read the following post: https://www.domoticz.com/forum/viewtopi ... 65&t=16692

Already did so last weekend
https://www.domoticz.com/wiki/index.php ... oldid=8211

Correct, as the Python plugin system is not part of a stable Domoticz release yet, I replaced the previous functionality with this new one.

Hi all, The latest beta as of today contains a breaking change for plugin authors that use selectors with customer level names. The previous build used base64 encoded string as options variable, the new code is a Python dictionary. Example: Options = {"LevelActions": "||||", "LevelNames": "Off|Video ...

That was the whole idea of the pull request. For C++, plugins did not need to base64 encode/decode options as the core already contained convenience methods for it. Now they are reused by the Python plugins also. About the python branch, that's the playground of Dnpwwo. Up to him to merge it there ...

Keep in mind that modifying the options after creation is not updated immediately in the webinterface. One needs to reload the page and/or switch to another page and come back. I'm not sure if (and how) a signal is send to the webbrowser to reload the control and if this can be initiated from a ...

When my pull request is merged, you get access to the Options setting from within the Python plugin system. Have a look at the modified example script. Variable Options is a dict which contains the levelnames.

https://github.com/domoticz/domoticz/pull/1360

If it's just to check when domoticz has crashed (ie exited) and if your system uses systemd, then use the following: (change the execstart parameters to your own usage) [Unit] Description=Domoticz Home Automation After=network.target [Service] Type=forking User=pi Group=pi WorkingDirectory=/home/pi ...

When you use these devices, do you need to make changes to your heating system? Currently I have a central thermostat device in my living room that controls the ground level floor heating and when that is switched on, the radiators on the first and second floor also work. But when the central ...

I have switched to this one also. Nicely done.

I have one suggestion.
Maybe add a couple of pixels space between the table and the buttons: Cheers

You need to rename to plugin.py

I see you're making some code breaking changes by improving onNotification. I would prefer also for more Pythonic naming conventions. In Python Class names use CapWord Module level functions use lower_case_with_underscores Function arguments use short lower case names, underscores if needed Which ...

Thanks :) Some more tips on the python plugin base template: global _plugin _plugin = BasePlugin() def onXXX(...): global _plugin _plugin.onXXX(...) The global keyword is unnecessary here. By defining _plugin at the module level it is already global. Referring to a module level variable (or function ...