Python Plugin : Broadlink RM2 V4

Python and python framework

Moderator: leecollings

Gerwin
Posts: 84
Joined: Friday 12 August 2016 13:08
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by Gerwin »

What a great plugin
it works great
thanks Zak45

Gerwin
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

Gerwin wrote: Sunday 14 April 2019 18:09 What a great plugin
it works great
thanks Zak45

Gerwin
you're welcome.
Happy to see you appreciate it.
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

Hi all,
thanks again zak for this awesome plugin!

It works perfectly for me, just the remote doesn't work.
I didn't find any other post with my issue, I hope I searched well.

If I click on the switch remote it gives me an error, below the log:
Spoiler: show
2019-04-12 15:50:50.196 Status: Closing application!...
2019-04-12 15:50:50.196 Status: Stopping worker...
2019-04-12 15:50:50.196 Status: RxQueue: queue worker stopped...
2019-04-12 15:50:53.380 Status: Domoticz V4.10602 (c)2012-2019 GizMoCuz
2019-04-12 15:50:53.380 Status: Build Hash: ce68fa52, Date: 2019-04-04 19:51:02
2019-04-12 15:50:53.381 Status: Startup Path: /home/pi/domoticz/
2019-04-12 15:50:53.462 Status: EventSystem: reset all events...
2019-04-12 15:50:53.612 Status: PluginSystem: Started, Python version '3.5.3'.
2019-04-12 15:50:53.612 Status: COpenWebNetTCP: scan devices DISABLED!
2019-04-12 15:50:53.627 Status: WebServer(HTTP) started on address: :: with port 8080
2019-04-12 15:50:53.631 Status: WebServer(SSL) started on address: :: with port 443
2019-04-12 15:50:53.633 Status: Proxymanager started.
2019-04-12 15:50:53.634 Status: TCPServer: shared server started...
2019-04-12 15:50:53.635 Status: RxQueue: queue worker started...
2019-04-12 15:50:55.636 Status: (Broadlink RM2) Started.
2019-04-12 15:50:55.636 Status: EventSystem: reset all events...
2019-04-12 15:50:55.637 Status: EventSystem: reset all device statuses...
2019-04-12 15:50:55.894 Status: Python EventSystem: Initalizing event module.
2019-04-12 15:50:55.894 Status: EventSystem: Started
2019-04-12 15:50:55.895 Status: EventSystem: Queue thread started...
2019-04-12 15:50:55.964 Status: PluginSystem: Entering work loop.

... all Broadlink devices ...
2019-04-12 15:50:56.270 (Broadlink RM2) Pushing 'PollIntervalDirective' on to queue
2019-04-12 15:50:56.270 (Broadlink RM2 - Import) Updating device from 0:'Off' to have values 0:'Off'.
2019-04-12 15:50:56.275 (Broadlink RM2) Update 0:'Off' (Broadlink RM2 - Import)
2019-04-12 15:50:56.275 (Broadlink RM2) Connecting to: XXX.XXX.X.XX:780F77FD3BB0
2019-04-12 15:50:56.338 (Broadlink RM2) Connected to Broadlink device: XXX.XXX.X.XX
2019-04-12 15:50:56.353 (Broadlink RM2) Processing 'PollIntervalDirective' message
2019-04-12 15:50:56.353 (Broadlink RM2) Heartbeat interval set to: 30.
2019-04-12 15:50:56.254 Status: (Broadlink RM2) Entering work loop.
2019-04-12 15:50:56.254 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'

2019-04-12 15:50:56.353 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read

... other stuffs ...
2019-04-12 12:49:28.356 (Broadlink RM2) Pushing 'onCommandCallback' on to queue
2019-04-12 12:49:28.387 (Broadlink RM2) Processing 'onCommandCallback' message
2019-04-12 12:49:28.387 (Broadlink RM2) Calling message handler 'onCommand'.
2019-04-12 12:49:28.387 (Broadlink RM2) onCommand called for Unit 254: Parameter 'On', Level: 0 , Connected : True
2019-04-12 12:49:28.387 (Broadlink RM2) Generate on Command for learned code stored on unit/ini :254
2019-04-12 12:49:28.356 Status: User: Admin initiated a switch command (28/Broadlink RM2 - Remote/On)
2019-04-12 12:49:28.390 Error: (Broadlink RM2) 'onCommand' failed 'MissingSectionHeaderError'.
2019-04-12 12:49:28.390 Error: (Broadlink RM2) ----> Line 317 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onCommand
2019-04-12 12:49:28.390 Error: (Broadlink RM2) ----> Line 529 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genCommand
2019-04-12 12:49:28.390 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-12 12:49:28.390 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read
pi@raspberrypi:~ $ sudo pip3 show broadlink

Name: broadlink
Version: 0.9
Summary: Python API for controlling Broadlink IR controllers
Home-page: http://github.com/mjg59/python-broadlink
Author: Matthew Garrett
Author-email: [email protected]
License: UNKNOWN
Location: /usr/local/lib/python3.5/dist-packages
Requires: PyCRC, pycryptodome
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

arcpaqua wrote: Monday 15 April 2019 10:58 Hi all,
thanks again zak for this awesome plugin!

It works perfectly for me, just the remote doesn't work.
I didn't find any other post with my issue, I hope I searched well.

If I click on the switch remote it gives me an error, below the log:
2019-04-12 15:50:56.353 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-12 15:50:56.353 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read

pi@raspberrypi:~ $ sudo pip3 show broadlink

Name: broadlink
Version: 0.9
Summary: Python API for controlling Broadlink IR controllers
Home-page: http://github.com/mjg59/python-broadlink
Author: Matthew Garrett
Author-email: [email protected]
License: UNKNOWN
Location: /usr/local/lib/python3.5/dist-packages
Requires: PyCRC, pycryptodome
The MissingSectionHeaderError mean you have a bad format on your ini file.(the one for your remote)
this one need to be like that :

[Custom]
command = xx,yy,....
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

Thank you Zak,
the ini file is correct (I followed the guide).

[Custom]
command = 27,5,2,8,4,9,10,6,16,13,,11,16,,15,14,,12,,,,,

I tried also with:
[Custom]
command = 27,5,2,8,4,9,10,6,16,13

and:
[Custom]
Command = 27,5,2,8,4,9,10,6,16,13

There is a strange thing, in the guide and in the python file (plugin.py) it's written that the ini file for remote should be in remote folder (for me /home/pi/domoticz/plugins/BroadlinkRM2/log/remote) and his name should be plugin_remote_<<hardwareid>>.ini (so for me /home/pi/domoticz/plugins/BroadlinkRM2/log/remote/plugin_remote_5.ini).
But in fact, if I create the file and put it in the correct folder as shown in the guide, Domoticz tell me:
2019-04-15 17:32:24.419 Error: (Broadlink RM2 Soggiorno) ini file not found: /home/pi/domoticz/plugins/BroadlinkRM2/log/BroadlinkRM2-5-254.ini
So I renamed my file and placed it in the folder shown by the Domoticz log and it happens what I wrote in my previous post.

What I do wrong?

Thank you very much

[EDIT]
I create the ini file by copying one of the learned codes, so the format should be correct.
The character Coding is UTF-8
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

@arcpaqua
this file need to be under remote folder.
Verify that you put correct right on it.. just to validate, you can start with chmod 777
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

If I move the file in remote folder it doesn't work
2019-04-15 17:32:24.419 Error: (Broadlink RM2 Soggiorno) ini file not found: /home/pi/domoticz/plugins/BroadlinkRM2/log/BroadlinkRM2-5-254.ini
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

this need to be on the remote folder.
when you start the plugin, you should see something like that :
2019-04-15 22:17:59.650 (RM2 Salon) ini file read....C:/BroadlinkRM2/remote/plugin_remote_13.ini
2019-04-15 22:17:59.650 (RM2 Salon) Custom Commands: 4,70,72,74,86
2019-04-15 22:17:59.650 (RM2 Salon) Device Number begin to : 11

of course, this is only one example.
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

If I do as you write I have this error message:
2019-04-15 23:54:41.011 Status: (Broadlink RM2) Stop directive received.
2019-04-15 23:54:41.011 Status: (Broadlink RM2) Exiting work loop.
2019-04-15 23:54:41.111 Status: (Broadlink RM2) Stopping threads.
2019-04-15 23:54:41.111 Status: (Broadlink RM2) Stopped.
2019-04-15 23:54:41.111 Status: (Broadlink RM2) Started.
2019-04-15 23:54:41.381 Status: (Broadlink RM2) Entering work loop.
2019-04-15 23:54:41.381 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'

2019-04-15 23:54:41.486 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-15 23:54:41.486 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-15 23:54:41.486 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-15 23:54:41.486 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-15 23:54:41.486 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-15 23:54:41.486 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read


After that, if I click on the remote switch:
2019-04-15 23:55:13.511 Status: User: Admin initiated a switch command (28/Broadlink RM2 Soggiorno - Remote/On)
2019-04-15 23:55:13.544 Error: (Broadlink RM2 Soggiorno) ini file not found: /home/pi/domoticz/plugins/BroadlinkRM2/BroadlinkRM2-5-254.ini

So as you can see Domoticz doesn't search on remote folder and the file name isn't plugin_remote_5.ini

Why does it happen to me?

You can find attached the folder structure
Attachments
BroadlinkError_002.jpg
BroadlinkError_002.jpg (114.01 KiB) Viewed 2874 times
BroadlinkError_001.jpg
BroadlinkError_001.jpg (185.51 KiB) Viewed 2874 times
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

@arcpaqua

At one moment you said to have this error:
2019-04-15 17:32:24.419 Error: (Broadlink RM2 Soggiorno) ini file not found: /home/pi/domoticz/plugins/BroadlinkRM2/log/BroadlinkRM2-5-254.ini

but I do not see any log folder on your screenshot....

put the plugin on debug mode.
and post Domoticz log from start.
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

I'm sorry @zak45

It's because I just made some experiment by changing folders.
The question is the same in both (with and without log folder).

Below the log with the following actions: reboot system, restart domoticz service, restart (update) hardware Broadlink and click on remote button switch.

It's a bit long... sorry
Spoiler: show

Code: Select all

2019-04-16 14:09:04.662 Status: Domoticz V4.10603 (c)2012-2019 GizMoCuz
2019-04-16 14:09:04.671 Status: Build Hash: 08d470ce, Date: 2019-04-15 08:30:21
2019-04-16 14:09:04.673 Status: Startup Path: /home/pi/domoticz/
2019-04-16 14:09:04.992 Status: EventSystem: reset all events...
2019-04-16 14:09:05.735 Status: PluginSystem: Started, Python version '3.5.3'.
2019-04-16 14:09:05.747 Status: COpenWebNetTCP: scan devices DISABLED!
2019-04-16 14:09:05.992 Status: WebServer(HTTP) started on address: :: with port 8080
2019-04-16 14:09:06.040 Status: WebServer(SSL) started on address: :: with port 443
2019-04-16 14:09:06.044 Status: Proxymanager started.
2019-04-16 14:09:06.046 Status: TCPServer: shared server started...
2019-04-16 14:09:06.047 Status: RxQueue: queue worker started...
2019-04-16 14:09:08.942 (Broadlink RM2) Device Name: 'T_8'
2019-04-16 14:09:08.942 (Broadlink RM2) Device nValue: 0
2019-04-16 14:09:08.942 (Broadlink RM2) Device sValue: ''
2019-04-16 14:09:08.942 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.942 (Broadlink RM2) Device: 25 - ID: 59, Name: 'T_9', nValue: 0, sValue: ''
2019-04-16 14:09:08.942 (Broadlink RM2) Device ID: '59'
2019-04-16 14:09:08.942 (Broadlink RM2) Device Name: 'T_9'
2019-04-16 14:09:08.942 (Broadlink RM2) Device nValue: 0
2019-04-16 14:09:08.942 (Broadlink RM2) Device sValue: ''
2019-04-16 14:09:08.942 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device: 26 - ID: 60, Name: 'T_0', nValue: 0, sValue: ''
2019-04-16 14:09:08.943 (Broadlink RM2) Device ID: '60'
2019-04-16 14:09:08.943 (Broadlink RM2) Device Name: 'T_0'
2019-04-16 14:09:08.943 (Broadlink RM2) Device nValue: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device sValue: ''
2019-04-16 14:09:08.943 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device: 27 - ID: 61, Name: 'T_Home', nValue: 1, sValue: 'On-3'
2019-04-16 14:09:08.943 (Broadlink RM2) Device ID: '61'
2019-04-16 14:09:08.943 (Broadlink RM2) Device Name: 'T_Home'
2019-04-16 14:09:08.943 (Broadlink RM2) Device nValue: 1
2019-04-16 14:09:08.943 (Broadlink RM2) Device sValue: 'On-3'
2019-04-16 14:09:08.943 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device: 254 - ID: 28, Name: 'Broadlink RM2 - Remote', nValue: 0, sValue: ''
2019-04-16 14:09:08.943 (Broadlink RM2) Device ID: '28'
2019-04-16 14:09:08.943 (Broadlink RM2) Device Name: 'Broadlink RM2 - Remote'
2019-04-16 14:09:08.943 (Broadlink RM2) Device nValue: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device sValue: ''
2019-04-16 14:09:08.943 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device: 255 - ID: 29, Name: 'Broadlink RM2 - Import', nValue: 0, sValue: 'Off'
2019-04-16 14:09:08.943 (Broadlink RM2) Device ID: '29'
2019-04-16 14:09:08.943 (Broadlink RM2) Device Name: 'Broadlink RM2 - Import'
2019-04-16 14:09:08.943 (Broadlink RM2) Device nValue: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Device sValue: 'Off'
2019-04-16 14:09:08.943 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:09:08.943 (Broadlink RM2) Pushing 'PollIntervalDirective' on to queue
2019-04-16 14:09:08.943 (Broadlink RM2 - Import) Updating device from 0:'Off' to have values 0:'Off'.
2019-04-16 14:09:08.954 (Broadlink RM2) Update 0:'Off' (Broadlink RM2 - Import)
2019-04-16 14:09:08.954 (Broadlink RM2) Connecting to: 192.168.1.15:780F77FD3BB0
2019-04-16 14:09:08.956 (Broadlink RM2 - Command) Updating device from 1:'10' to have values 0:'Off'.
2019-04-16 14:09:08.963 (Broadlink RM2) Update 0:'Off' (Broadlink RM2 - Command)
2019-04-16 14:09:08.984 (Broadlink RM2) Processing 'PollIntervalDirective' message
2019-04-16 14:09:08.984 (Broadlink RM2) Heartbeat interval set to: 30.
2019-04-16 14:09:08.048 Status: (Broadlink RM2) Started.
2019-04-16 14:09:08.049 Status: EventSystem: reset all events...
2019-04-16 14:09:08.049 Status: EventSystem: reset all device statuses...
2019-04-16 14:09:08.078 Status: PluginSystem: Entering work loop.
2019-04-16 14:09:08.804 Status: (Broadlink RM2) Entering work loop.
2019-04-16 14:09:08.805 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'
2019-04-16 14:09:08.925 Status: Python EventSystem: Initalizing event module.
2019-04-16 14:09:08.927 Status: EventSystem: Started
2019-04-16 14:09:08.927 Status: EventSystem: Queue thread started...
2019-04-16 14:09:08.956 Error: (Broadlink RM2) Error Connecting to Broadlink device....192.168.1.15
2019-04-16 14:09:08.984 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-16 14:09:08.984 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-16 14:09:08.984 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-16 14:09:08.984 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-16 14:09:08.984 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-16 14:09:08.984 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read
2019-04-16 14:09:09.050 Status: MQTT: Connecting to 192.168.1.100:1883
2019-04-16 14:11:44.447 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:44.456 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:44.464 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:44.513 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:54.477 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:54.486 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:54.499 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:54.508 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:58.405 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:11:58.440 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:11:58.440 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:12:04.457 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:12:04.466 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:12:04.495 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:12:04.504 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:12:12.547 Status: COpenWebNetTCP: received=*#13**22*14*11*04*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:12:12.547 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:12:14.409 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:12:14.419 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:12:14.451 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:12:14.459 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:12:24.467 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:12:24.476 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:12:24.486 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:12:24.495 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:12:28.410 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:12:28.442 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:12:28.442 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:12:34.447 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:12:34.457 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:12:34.481 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:12:34.489 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:12:42.610 Status: COpenWebNetTCP: received=*#13**22*14*11*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:12:42.610 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:12:44.477 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:12:44.482 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:12:44.515 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:12:44.521 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:13:04.609 Status: Domoticz V4.10603 (c)2012-2019 GizMoCuz
2019-04-16 14:13:04.610 Status: Build Hash: 08d470ce, Date: 2019-04-15 08:30:21
2019-04-16 14:13:04.612 Status: Startup Path: /home/pi/domoticz/
2019-04-16 14:13:04.684 Status: EventSystem: reset all events...
2019-04-16 14:13:04.808 Status: PluginSystem: Started, Python version '3.5.3'.
2019-04-16 14:13:04.809 Status: COpenWebNetTCP: scan devices DISABLED!
2019-04-16 14:13:04.824 Status: WebServer(HTTP) started on address: :: with port 8080
2019-04-16 14:13:04.829 Status: WebServer(SSL) started on address: :: with port 443
2019-04-16 14:13:04.830 Status: Proxymanager started.
2019-04-16 14:13:04.832 Status: TCPServer: shared server started...
2019-04-16 14:13:04.832 Status: RxQueue: queue worker started...
2019-04-16 14:13:06.833 Status: (Broadlink RM2) Started.
2019-04-16 14:13:06.834 Status: EventSystem: reset all events...
2019-04-16 14:13:06.835 Status: EventSystem: reset all device statuses...
2019-04-16 14:13:07.491 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.491 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.491 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.491 (Broadlink RM2) Device: 15 - ID: 49, Name: 'T_Muto', nValue: 0, sValue: ''
2019-04-16 14:13:07.491 (Broadlink RM2) Device ID: '49'
2019-04-16 14:13:07.491 (Broadlink RM2) Device Name: 'T_Muto'
2019-04-16 14:13:07.491 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.491 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.491 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.491 (Broadlink RM2) Device: 16 - ID: 50, Name: 'T_Guida', nValue: 0, sValue: ''
2019-04-16 14:13:07.491 (Broadlink RM2) Device ID: '50'
2019-04-16 14:13:07.491 (Broadlink RM2) Device Name: 'T_Guida'
2019-04-16 14:13:07.491 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.491 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 17 - ID: 51, Name: 'T_1', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '51'
2019-04-16 14:13:07.492 (Broadlink RM2) Device Name: 'T_1'
2019-04-16 14:13:07.492 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 18 - ID: 52, Name: 'T_2', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '52'
2019-04-16 14:13:07.492 (Broadlink RM2) Device Name: 'T_2'
2019-04-16 14:13:07.492 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 19 - ID: 53, Name: 'T_3', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '53'
2019-04-16 14:13:07.492 (Broadlink RM2) Device Name: 'T_3'
2019-04-16 14:13:07.492 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 20 - ID: 54, Name: 'T_4', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '54'
2019-04-16 14:13:07.492 (Broadlink RM2) Device Name: 'T_4'
2019-04-16 14:13:07.492 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 21 - ID: 55, Name: 'T_5', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '55'
2019-04-16 14:13:07.492 (Broadlink RM2) Device Name: 'T_5'
2019-04-16 14:13:07.492 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.492 (Broadlink RM2) Device: 22 - ID: 56, Name: 'T_6', nValue: 0, sValue: ''
2019-04-16 14:13:07.492 (Broadlink RM2) Device ID: '56'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_6'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device: 23 - ID: 57, Name: 'T_7', nValue: 0, sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device ID: '57'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_7'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device: 24 - ID: 58, Name: 'T_8', nValue: 0, sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device ID: '58'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_8'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device: 25 - ID: 59, Name: 'T_9', nValue: 0, sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device ID: '59'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_9'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device: 26 - ID: 60, Name: 'T_0', nValue: 0, sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device ID: '60'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_0'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.493 (Broadlink RM2) Device: 27 - ID: 61, Name: 'T_Home', nValue: 1, sValue: 'On-3'
2019-04-16 14:13:07.493 (Broadlink RM2) Device ID: '61'
2019-04-16 14:13:07.493 (Broadlink RM2) Device Name: 'T_Home'
2019-04-16 14:13:07.493 (Broadlink RM2) Device nValue: 1
2019-04-16 14:13:07.493 (Broadlink RM2) Device sValue: 'On-3'
2019-04-16 14:13:07.493 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.494 (Broadlink RM2) Device: 254 - ID: 28, Name: 'Broadlink RM2 - Remote', nValue: 0, sValue: ''
2019-04-16 14:13:07.494 (Broadlink RM2) Device ID: '28'
2019-04-16 14:13:07.494 (Broadlink RM2) Device Name: 'Broadlink RM2 - Remote'
2019-04-16 14:13:07.494 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.494 (Broadlink RM2) Device sValue: ''
2019-04-16 14:13:07.494 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.494 (Broadlink RM2) Device: 255 - ID: 29, Name: 'Broadlink RM2 - Import', nValue: 0, sValue: 'Off'
2019-04-16 14:13:07.494 (Broadlink RM2) Device ID: '29'
2019-04-16 14:13:07.494 (Broadlink RM2) Device Name: 'Broadlink RM2 - Import'
2019-04-16 14:13:07.494 (Broadlink RM2) Device nValue: 0
2019-04-16 14:13:07.494 (Broadlink RM2) Device sValue: 'Off'
2019-04-16 14:13:07.494 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:13:07.494 (Broadlink RM2) Pushing 'PollIntervalDirective' on to queue
2019-04-16 14:13:07.494 (Broadlink RM2 - Import) Updating device from 0:'Off' to have values 0:'Off'.
2019-04-16 14:13:07.499 (Broadlink RM2) Update 0:'Off' (Broadlink RM2 - Import)
2019-04-16 14:13:07.499 (Broadlink RM2) Connecting to: 192.168.1.15:780F77FD3BB0
2019-04-16 14:13:07.562 (Broadlink RM2) Connected to Broadlink device: 192.168.1.15
2019-04-16 14:13:07.577 (Broadlink RM2) Processing 'PollIntervalDirective' message
2019-04-16 14:13:07.577 (Broadlink RM2) Heartbeat interval set to: 30.
2019-04-16 14:13:07.100 Status: Python EventSystem: Initalizing event module.
2019-04-16 14:13:07.100 Status: EventSystem: Started
2019-04-16 14:13:07.100 Status: EventSystem: Queue thread started...
2019-04-16 14:13:07.186 Status: PluginSystem: Entering work loop.
2019-04-16 14:13:07.478 Status: (Broadlink RM2) Entering work loop.
2019-04-16 14:13:07.479 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'
2019-04-16 14:13:07.834 Status: MQTT: Connecting to 192.168.1.100:1883
2019-04-16 14:13:07.840 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:07.934 Status: MQTT: connected to: 192.168.1.100:1883
2019-04-16 14:13:07.577 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read
2019-04-16 14:13:08.006 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.035 Status: MQTT: Subscribed
2019-04-16 14:13:08.085 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:14.468 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:13:14.473 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:13:14.503 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:13:14.508 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:13:17.480 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:13:17.490 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:13:17.490 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:13:42.570 Status: COpenWebNetTCP: received=*#13**22*14*12*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:13:42.571 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:13:04.609 Status: Domoticz V4.10603 (c)2012-2019 GizMoCuz
2019-04-16 14:13:04.610 Status: Build Hash: 08d470ce, Date: 2019-04-15 08:30:21
2019-04-16 14:13:04.612 Status: Startup Path: /home/pi/domoticz/
2019-04-16 14:13:04.684 Status: EventSystem: reset all events...
2019-04-16 14:13:04.808 Status: PluginSystem: Started, Python version '3.5.3'.
2019-04-16 14:13:04.809 Status: COpenWebNetTCP: scan devices DISABLED!
2019-04-16 14:13:04.824 Status: WebServer(HTTP) started on address: :: with port 8080
2019-04-16 14:13:04.829 Status: WebServer(SSL) started on address: :: with port 443
2019-04-16 14:13:04.830 Status: Proxymanager started.
2019-04-16 14:13:04.832 Status: TCPServer: shared server started...
2019-04-16 14:13:04.832 Status: RxQueue: queue worker started...
2019-04-16 14:13:06.833 Status: (Broadlink RM2) Started.
2019-04-16 14:13:06.834 Status: EventSystem: reset all events...
2019-04-16 14:13:06.835 Status: EventSystem: reset all device statuses...
2019-04-16 14:13:07.100 Status: Python EventSystem: Initalizing event module.
2019-04-16 14:13:07.100 Status: EventSystem: Started
2019-04-16 14:13:07.100 Status: EventSystem: Queue thread started...
2019-04-16 14:13:07.186 Status: PluginSystem: Entering work loop.
2019-04-16 14:13:07.478 Status: (Broadlink RM2) Entering work loop.
2019-04-16 14:13:07.479 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'
2019-04-16 14:13:07.834 Status: MQTT: Connecting to 192.168.1.100:1883
2019-04-16 14:13:07.840 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:07.924 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:07.934 Status: MQTT: connected to: 192.168.1.100:1883
2019-04-16 14:13:07.577 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-16 14:13:07.577 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read
2019-04-16 14:13:08.006 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.035 Status: MQTT: Subscribed
2019-04-16 14:13:08.085 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.165 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.245 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.325 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:08.778 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:09.785 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:10.798 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:11.805 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:12.823 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:30.006 Status: COpenWebNetTCP: Monitor session connected to: 192.168.1.40:20000
2019-04-16 14:13:30.824 Status: COpenWebNetTCP: scanning automation/lighting...
2019-04-16 14:13:30.830 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:30.932 Status: COpenWebNetTCP: received=*1*0*11## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 1
2019-04-16 14:13:30.994 Status: COpenWebNetTCP: received=*1*0*21## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 1
2019-04-16 14:13:30.996 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:30.996 Status: COpenWebNetTCP: request burglar alarm status...
2019-04-16 14:13:31.010 Status: COpenWebNetTCP: received=*1*0*12## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 2
2019-04-16 14:13:31.070 Status: COpenWebNetTCP: received=*1*0*22## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 2
2019-04-16 14:13:31.084 Status: COpenWebNetTCP: received=*1*0*13## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 3
2019-04-16 14:13:31.085 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:13:31.086 Status: COpenWebNetTCP: scan device complete, wait all the update data..
2019-04-16 14:13:31.151 Status: COpenWebNetTCP: received=*1*0*14## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 4
2019-04-16 14:13:31.233 Status: COpenWebNetTCP: received=*1*0*23## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 3
2019-04-16 14:13:31.262 Status: COpenWebNetTCP: received=*1*0*24## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 4
2019-04-16 14:13:31.359 Status: COpenWebNetTCP: received=*#2*91*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:31.403 Status: COpenWebNetTCP: received=*2*0*91## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 1
2019-04-16 14:13:31.448 Status: COpenWebNetTCP: received=*#2*92*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:31.493 Status: COpenWebNetTCP: received=*2*0*92## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 2
2019-04-16 14:13:31.548 Status: COpenWebNetTCP: received=*#2*93*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:31.583 Status: COpenWebNetTCP: received=*2*0*93## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 3
2019-04-16 14:13:31.638 Status: COpenWebNetTCP: received=*#2*94*10*10*100*001*0## : MEASURE FRAME
2019-04-16 14:13:31.683 Status: COpenWebNetTCP: received=*2*0*94## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 4
2019-04-16 14:13:31.724 Status: COpenWebNetTCP: received=*1*0*15## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 5
2019-04-16 14:13:31.751 Status: COpenWebNetTCP: received=*1*0*25## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 5
2019-04-16 14:13:31.801 Status: COpenWebNetTCP: received=*1*0*16## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 6
2019-04-16 14:13:31.841 Status: COpenWebNetTCP: received=*1*0*26## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 6
2019-04-16 14:13:31.881 Status: COpenWebNetTCP: received=*1*0*17## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 7
2019-04-16 14:13:31.919 Status: COpenWebNetTCP: received=*1*0*27## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 7
2019-04-16 14:13:31.969 Status: COpenWebNetTCP: received=*1*0*18## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 8
2019-04-16 14:13:32.009 Status: COpenWebNetTCP: received=*1*0*28## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 8
2019-04-16 14:13:32.058 Status: COpenWebNetTCP: received=*#2*95*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:32.112 Status: COpenWebNetTCP: received=*2*0*95## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 5
2019-04-16 14:13:32.160 Status: COpenWebNetTCP: received=*#2*96*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:32.210 Status: COpenWebNetTCP: received=*2*0*96## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 6
2019-04-16 14:13:32.270 Status: COpenWebNetTCP: received=*#2*97*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:32.320 Status: COpenWebNetTCP: received=*2*0*97## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 7
2019-04-16 14:13:32.380 Status: COpenWebNetTCP: received=*#2*98*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:32.429 Status: COpenWebNetTCP: received=*2*0*98## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 8
2019-04-16 14:13:32.491 Status: COpenWebNetTCP: received=*#2*99*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:13:32.540 Status: COpenWebNetTCP: received=*2*0*99## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 9
2019-04-16 14:13:42.570 Status: COpenWebNetTCP: received=*#13**22*14*12*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:13:42.571 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:14:12.676 Status: COpenWebNetTCP: received=*#13**22*14*13*04*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:14:12.676 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:14:35.988 Status: (Broadlink RM2) Stop directive received.
2019-04-16 14:14:35.988 Status: (Broadlink RM2) Exiting work loop.
2019-04-16 14:14:36.434 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device: 15 - ID: 49, Name: 'T_Muto', nValue: 0, sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device ID: '49'
2019-04-16 14:14:36.434 (Broadlink RM2) Device Name: 'T_Muto'
2019-04-16 14:14:36.434 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device: 16 - ID: 50, Name: 'T_Guida', nValue: 0, sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device ID: '50'
2019-04-16 14:14:36.434 (Broadlink RM2) Device Name: 'T_Guida'
2019-04-16 14:14:36.434 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device: 17 - ID: 51, Name: 'T_1', nValue: 0, sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device ID: '51'
2019-04-16 14:14:36.434 (Broadlink RM2) Device Name: 'T_1'
2019-04-16 14:14:36.434 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.434 (Broadlink RM2) Device: 18 - ID: 52, Name: 'T_2', nValue: 0, sValue: ''
2019-04-16 14:14:36.434 (Broadlink RM2) Device ID: '52'
2019-04-16 14:14:36.434 (Broadlink RM2) Device Name: 'T_2'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 19 - ID: 53, Name: 'T_3', nValue: 0, sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device ID: '53'
2019-04-16 14:14:36.435 (Broadlink RM2) Device Name: 'T_3'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 20 - ID: 54, Name: 'T_4', nValue: 0, sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device ID: '54'
2019-04-16 14:14:36.435 (Broadlink RM2) Device Name: 'T_4'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 21 - ID: 55, Name: 'T_5', nValue: 0, sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device ID: '55'
2019-04-16 14:14:36.435 (Broadlink RM2) Device Name: 'T_5'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 22 - ID: 56, Name: 'T_6', nValue: 0, sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device ID: '56'
2019-04-16 14:14:36.435 (Broadlink RM2) Device Name: 'T_6'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 23 - ID: 57, Name: 'T_7', nValue: 0, sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device ID: '57'
2019-04-16 14:14:36.435 (Broadlink RM2) Device Name: 'T_7'
2019-04-16 14:14:36.435 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.435 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.435 (Broadlink RM2) Device: 24 - ID: 58, Name: 'T_8', nValue: 0, sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '58'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'T_8'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device: 25 - ID: 59, Name: 'T_9', nValue: 0, sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '59'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'T_9'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device: 26 - ID: 60, Name: 'T_0', nValue: 0, sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '60'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'T_0'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device: 27 - ID: 61, Name: 'T_Home', nValue: 1, sValue: 'On-3'
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '61'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'T_Home'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 1
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: 'On-3'
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device: 254 - ID: 28, Name: 'Broadlink RM2 - Remote', nValue: 0, sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '28'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'Broadlink RM2 - Remote'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: ''
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device: 255 - ID: 29, Name: 'Broadlink RM2 - Import', nValue: 0, sValue: 'Off'
2019-04-16 14:14:36.436 (Broadlink RM2) Device ID: '29'
2019-04-16 14:14:36.436 (Broadlink RM2) Device Name: 'Broadlink RM2 - Import'
2019-04-16 14:14:36.436 (Broadlink RM2) Device nValue: 0
2019-04-16 14:14:36.436 (Broadlink RM2) Device sValue: 'Off'
2019-04-16 14:14:36.436 (Broadlink RM2) Device LastLevel: 0
2019-04-16 14:14:36.437 (Broadlink RM2) Pushing 'PollIntervalDirective' on to queue
2019-04-16 14:14:36.437 (Broadlink RM2 - Import) Updating device from 0:'Off' to have values 0:'Off'.
2019-04-16 14:14:36.442 (Broadlink RM2) Update 0:'Off' (Broadlink RM2 - Import)
2019-04-16 14:14:36.442 (Broadlink RM2) Connecting to: 192.168.1.15:780F77FD3BB0
2019-04-16 14:14:36.505 (Broadlink RM2) Connected to Broadlink device: 192.168.1.15
2019-04-16 14:14:36.509 (Broadlink RM2) Processing 'PollIntervalDirective' message
2019-04-16 14:14:36.509 (Broadlink RM2) Heartbeat interval set to: 30.
2019-04-16 14:14:36.189 Status: (Broadlink RM2) Stopping threads.
2019-04-16 14:14:36.189 Status: (Broadlink RM2) Stopped.
2019-04-16 14:14:36.189 Status: (Broadlink RM2) Started.
2019-04-16 14:14:36.421 Status: (Broadlink RM2) Entering work loop.
2019-04-16 14:14:36.422 Status: (Broadlink RM2) Initialized version 4.2.0, author 'zak45'
2019-04-16 14:14:36.509 Error: (Broadlink RM2) 'onStart' failed 'MissingSectionHeaderError'.
2019-04-16 14:14:36.509 Error: (Broadlink RM2) ----> Line 218 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function onStart
2019-04-16 14:14:36.509 Error: (Broadlink RM2) ----> Line 978 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function genRemote
2019-04-16 14:14:36.509 Error: (Broadlink RM2) ----> Line 960 in '/home/pi/domoticz/plugins/BroadlinkRM2/plugin.py', function get_remoteconfig
2019-04-16 14:14:36.509 Error: (Broadlink RM2) ----> Line 698 in '/usr/lib/python3.5/configparser.py', function read
2019-04-16 14:14:36.509 Error: (Broadlink RM2) ----> Line 1077 in '/usr/lib/python3.5/configparser.py', function _read
2019-04-16 14:14:42.740 Status: COpenWebNetTCP: received=*#13**22*14*13*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:14:42.740 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:14:44.487 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:14:44.496 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:14:44.525 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:14:44.534 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:14:46.423 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:14:46.427 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:14:46.428 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:15:12.798 Status: COpenWebNetTCP: received=*#13**22*14*14*04*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:15:12.798 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:15:14.476 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:15:14.486 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:15:14.510 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:15:14.518 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:15:16.430 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:15:16.477 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:15:16.477 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:15:16.541 (Broadlink RM2) Connected to Broadlink device: 192.168.1.15
2019-04-16 14:15:42.863 Status: COpenWebNetTCP: received=*#13**22*14*14*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:15:42.863 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:15:44.477 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:15:44.486 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:15:44.494 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:15:44.503 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:15:46.435 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:15:46.443 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:15:46.443 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:16:12.925 Status: COpenWebNetTCP: received=*#13**22*14*15*04*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:16:12.925 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:16:14.487 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:16:14.497 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:16:14.529 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:16:14.538 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:16:16.440 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:16:16.445 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:16:16.445 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:16:20.582 (Broadlink RM2) Pushing 'onCommandCallback' on to queue
2019-04-16 14:16:20.602 (Broadlink RM2) Processing 'onCommandCallback' message
2019-04-16 14:16:20.602 (Broadlink RM2) Calling message handler 'onCommand'.
2019-04-16 14:16:20.602 (Broadlink RM2) onCommand called for Unit 254: Parameter 'On', Level: 0 , Connected : True
2019-04-16 14:16:20.602 (Broadlink RM2) Generate on Command for learned code stored on unit/ini :254
2019-04-16 14:16:20.581 Status: User: Admin initiated a switch command (28/Broadlink RM2 - Remote/On)
2019-04-16 14:16:20.603 Error: (Broadlink RM2) ini file not found: /home/pi/domoticz/plugins/BroadlinkRM2/BroadlinkRM2-5-254.ini
2019-04-16 14:16:24.468 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:16:24.477 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:16:24.485 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:16:24.534 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:16:34.447 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:16:34.457 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:16:34.481 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:16:34.489 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:16:42.985 Status: COpenWebNetTCP: received=*#13**22*14*15*34*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:16:42.985 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:16:44.467 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.1","Battery":62,"RSSI":7}
2019-04-16 14:16:44.476 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:16:44.516 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:16:44.524 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:16:46.445 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:16:46.447 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:16:46.447 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:09:18.805 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:09:18.854 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:09:18.854 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:09:37.476 Status: Incoming connection from: 62.86.168.114
2019-04-16 14:09:43.705 Status: Incoming connection from: 62.86.168.114
2019-04-16 14:09:47.652 Status: MQTT: Connecting to 192.168.1.100:1883
2019-04-16 14:09:47.753 Status: MQTT: connected to: 192.168.1.100:1883
2019-04-16 14:09:47.853 Status: MQTT: Subscribed
2019-04-16 14:09:54.560 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:09:54.575 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:09:54.614 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:09:54.625 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:09:58.386 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:09:58.423 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:09:58.423 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:10:00.006 Status: COpenWebNetTCP: Monitor session connected to: 192.168.1.40:20000
2019-04-16 14:10:00.630 Status: COpenWebNetTCP: scanning automation/lighting...
2019-04-16 14:10:00.636 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:10:00.740 Status: COpenWebNetTCP: received=*1*0*11## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 1
2019-04-16 14:10:00.787 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:10:00.787 Status: COpenWebNetTCP: request burglar alarm status...
2019-04-16 14:10:00.859 Status: COpenWebNetTCP: Command session connected to: 192.168.1.40:20000
2019-04-16 14:10:00.859 Status: COpenWebNetTCP: scan device complete, wait all the update data..
2019-04-16 14:10:03.471 Status: COpenWebNetTCP: received=*1*0*21## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 1
2019-04-16 14:10:03.472 Status: COpenWebNetTCP: received=*1*0*12## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 2
2019-04-16 14:10:03.472 Status: COpenWebNetTCP: received=*1*0*22## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 2
2019-04-16 14:10:03.473 Status: COpenWebNetTCP: received=*1*0*13## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 3
2019-04-16 14:10:03.474 Status: COpenWebNetTCP: received=*1*0*14## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 4
2019-04-16 14:10:03.513 Status: COpenWebNetTCP: received=*1*0*23## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 3
2019-04-16 14:10:03.514 Status: COpenWebNetTCP: received=*1*0*24## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 4
2019-04-16 14:10:03.514 Status: COpenWebNetTCP: received=*#2*91*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.515 Status: COpenWebNetTCP: received=*2*0*91## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 1
2019-04-16 14:10:03.516 Status: COpenWebNetTCP: received=*#2*92*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.516 Status: COpenWebNetTCP: received=*2*0*92## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 2
2019-04-16 14:10:03.526 Status: COpenWebNetTCP: received=*#2*93*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.527 Status: COpenWebNetTCP: received=*2*0*93## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 3
2019-04-16 14:10:03.527 Status: COpenWebNetTCP: received=*#2*94*10*10*100*001*0## : MEASURE FRAME
2019-04-16 14:10:03.527 Status: COpenWebNetTCP: received=*2*0*94## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 4
2019-04-16 14:10:03.528 Status: COpenWebNetTCP: received=*1*0*15## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 5
2019-04-16 14:10:03.528 Status: COpenWebNetTCP: received=*1*0*25## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 5
2019-04-16 14:10:03.528 Status: COpenWebNetTCP: received=*1*0*16## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 6
2019-04-16 14:10:03.529 Status: COpenWebNetTCP: received=*1*0*26## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 6
2019-04-16 14:10:03.529 Status: COpenWebNetTCP: received=*1*0*17## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 7
2019-04-16 14:10:03.529 Status: COpenWebNetTCP: received=*1*0*27## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 7
2019-04-16 14:10:03.529 Status: COpenWebNetTCP: received=*1*0*18## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 1, point of light 8
2019-04-16 14:10:03.530 Status: COpenWebNetTCP: received=*1*0*28## : NORMAL FRAME - who=Lighting - what=Turn off - where=room 2, point of light 8
2019-04-16 14:10:03.530 Status: COpenWebNetTCP: received=*#2*95*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.530 Status: COpenWebNetTCP: received=*2*0*95## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 5
2019-04-16 14:10:03.531 Status: COpenWebNetTCP: received=*#2*96*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.531 Status: COpenWebNetTCP: received=*2*0*96## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 6
2019-04-16 14:10:03.531 Status: COpenWebNetTCP: received=*#2*97*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.532 Status: COpenWebNetTCP: received=*2*0*97## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 7
2019-04-16 14:10:03.532 Status: COpenWebNetTCP: received=*#2*98*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.532 Status: COpenWebNetTCP: received=*2*0*98## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 8
2019-04-16 14:10:03.533 Status: COpenWebNetTCP: received=*#2*99*10*10*0*001*0## : MEASURE FRAME
2019-04-16 14:10:03.533 Status: COpenWebNetTCP: received=*2*0*99## : NORMAL FRAME - who=Automation - what=Stop - where=room 9, point of light 9
2019-04-16 14:10:04.400 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:04.409 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:04.451 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:04.461 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:12.277 Status: COpenWebNetTCP: received=*#13**22*14*09*03*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:10:12.277 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:10:14.457 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:14.467 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:14.488 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:14.497 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:24.437 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:24.446 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:24.485 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:24.493 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:28.391 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:10:28.423 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:10:28.423 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:10:28.577 (Broadlink RM2) Connected to Broadlink device: 192.168.1.15
2019-04-16 14:10:28.578 (Broadlink RM2 - Command) Updating device from 0:'Off' to have values 1:'10'.
2019-04-16 14:10:28.587 (Broadlink RM2) Update 1:'10' (Broadlink RM2 - Command)
2019-04-16 14:10:34.460 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:34.469 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:34.480 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:34.488 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:42.369 Status: COpenWebNetTCP: received=*#13**22*14*09*33*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:10:42.369 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:10:44.438 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:44.447 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:44.476 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:44.484 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:54.467 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:10:54.476 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:10:54.514 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:10:54.522 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:10:57.535 Error: WebServer:443 thread seems to have ended unexpectedly (last update 70.000000 seconds ago)
2019-04-16 14:10:58.396 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:10:58.438 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:10:58.438 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:11:04.447 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:04.456 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:04.479 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:04.487 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:12.429 Status: COpenWebNetTCP: received=*#13**22*14*10*03*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:11:12.429 Error: COpenWebNetTCP: Who=13 not yet supported!
2019-04-16 14:11:14.493 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:14.502 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:14.515 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:14.524 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:24.477 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"1;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:24.486 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:24.512 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:24.521 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:28.400 (Broadlink RM2) Pushing 'onHeartbeatCallback' on to queue
2019-04-16 14:11:28.439 (Broadlink RM2) Processing 'onHeartbeatCallback' message
2019-04-16 14:11:28.439 (Broadlink RM2) Calling message handler 'onHeartbeat'.
2019-04-16 14:11:34.461 MQTT: Topic: domoticz/in, Message: {"idx":26,"nvalue":0,"svalue":"0;15174.0","Battery":62,"RSSI":7}
2019-04-16 14:11:34.470 EventSystem: Event triggered: TV_Bose_1
2019-04-16 14:11:34.508 (Sonoff POW R2) Light/Switch (TV)
2019-04-16 14:11:34.517 (Sonoff POW R2) Light/Switch (Bose)
2019-04-16 14:11:42.487 Status: COpenWebNetTCP: received=*#13**22*14*10*33*000*02*16*04*2019## : MEASURE FRAME
2019-04-16 14:11:42.487 Error: COpenWebNetTCP: Who=13 not yet supported!
arcpaqua
Posts: 16
Joined: Saturday 23 June 2018 20:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10338
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by arcpaqua »

arcpaqua wrote: Tuesday 16 April 2019 15:26 I'm sorry @zak45

It's because I just made some experiment by changing folders.
The question is the same in both (with and without log folder).

Below the log with the following actions: reboot system, restart domoticz service, restart (update) hardware Broadlink and click on remote button switch.
For now, I solved with a little trick: I created 4 switch selector with all TV commands.
KodiLike.jpg
KodiLike.jpg (78.29 KiB) Viewed 2833 times
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

@arcpaqua
Do you have verified right settings on your ini / folder ?
User running Domoticz need to have at minima read authorization.
Loky31
Posts: 40
Joined: Monday 11 March 2019 13:46
Target OS: -
Domoticz version:
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by Loky31 »

Hello Zak45,

I'm posting in the right place then :)

When trying to launch it by command line i have the folowing:

File "plugin_http.sh", line 1
nohup python /Domoticz/plugins/BroadlinkRM2/plugin_http.py $1 $2 $3 &
^
SyntaxError: invalid syntax

Looking everywhere in this plugin but didn't figure out what went wrong...

How do I check port usage under debian? ( silly question but I'm more a windows guy :) )


Edit : somehow something changed ! the nohup.out now indicates :
python: can't open file '/Domoticz/plugins/BroadlinkRM2/plugin_http.py': [Errno 13] Permission denied

wheras before it was a path error saying that such file or directory did not exist.
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

Loky31 wrote: Thursday 02 May 2019 10:12 Hello Zak45,

I'm posting in the right place then :)

When trying to launch it by command line i have the folowing:

File "plugin_http.sh", line 1
nohup python /Domoticz/plugins/BroadlinkRM2/plugin_http.py $1 $2 $3 &
^
SyntaxError: invalid syntax

Looking everywhere in this plugin but didn't figure out what went wrong...

How do I check port usage under debian? ( silly question but I'm more a windows guy :) )


Edit : somehow something changed ! the nohup.out now indicates :
python: can't open file '/Domoticz/plugins/BroadlinkRM2/plugin_http.py': [Errno 13] Permission denied

wheras before it was a path error saying that such file or directory did not exist.
fine :-)

verify when you do python from a terminal session that it load python v3.x and not 2.x.
If loading 2.x then replace python by python3 into plugin_http.sh
And yes, check again all rights on the file.
Loky31
Posts: 40
Joined: Monday 11 March 2019 13:46
Target OS: -
Domoticz version:
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by Loky31 »

noob question, how do I do this check?
I thought that installing it by pip3 was enough to get sure of that.

Regarding the rights on the file, by any chance can you tell me which of the numerous directory of BroadlinkRM2 over the system are the executed files pick from?
As I got path error I explore and discover there are a lot different directories for the broadlink...
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

Loky31 wrote: Thursday 02 May 2019 16:05 noob question, how do I do this check?
I thought that installing it by pip3 was enough to get sure of that.

Regarding the rights on the file, by any chance can you tell me which of the numerous directory of BroadlinkRM2 over the system are the executed files pick from?
As I got path error I explore and discover there are a lot different directories for the broadlink...
put debug mode 'on' for the plugin and post domoticz log from start.
Loky31
Posts: 40
Joined: Monday 11 March 2019 13:46
Target OS: -
Domoticz version:
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by Loky31 »

Ok so it's done :)

I can confirm that I'm running python 3.5.3:
2019-05-03 22:45:36.360 Status: PluginSystem: Started, Python version '3.5.3'.

Regarding what the RM plugin log , here it is :

2019-05-03 22:46:20.326 (RM salon) Debug logging mask set to: PYTHON PLUGIN QUEUE IMAGE DEVICE CONNECTION MESSAGE ALL
2019-05-03 22:46:20.326 (RM salon) 'Mode1':'780f77182d75'
2019-05-03 22:46:20.326 (RM salon) 'DomoticzBuildTime':'2019-05-02 18:46:22'
2019-05-03 22:46:20.326 (RM salon) 'Database':'/home/pi/domoticz/domoticz.db'
2019-05-03 22:46:20.326 (RM salon) 'DomoticzHash':'281a59b7'
2019-05-03 22:46:20.326 (RM salon) 'Address':'192.168.1.97'
2019-05-03 22:46:20.327 (RM salon) 'HardwareID':'16'
2019-05-03 22:46:20.327 (RM salon) 'Author':'zak45'
2019-05-03 22:46:20.327 (RM salon) 'Mode3':'RM2'
2019-05-03 22:46:20.327 (RM salon) 'Key':'BroadlinkRM2'
2019-05-03 22:46:20.327 (RM salon) 'HomeFolder':'/home/pi/domoticz/plugins/BroadlinkRM2/'
2019-05-03 22:46:20.327 (RM salon) 'Port':'0'
2019-05-03 22:46:20.327 (RM salon) 'Version':'4.2.0'
2019-05-03 22:46:20.327 (RM salon) 'DomoticzVersion':'4.10666'
2019-05-03 22:46:20.327 (RM salon) 'Name':'RM salon'
2019-05-03 22:46:20.327 (RM salon) 'StartupFolder':'/home/pi/domoticz/'
2019-05-03 22:46:20.327 (RM salon) 'Mode5':'9000'
2019-05-03 22:46:20.327 (RM salon) 'Mode6':'Debug'
2019-05-03 22:46:20.327 (RM salon) 'Mode2':'/home/domoticz/plugins/BroadlinkRM2'
2019-05-03 22:46:20.327 (RM salon) 'Mode4':'yes'
2019-05-03 22:46:20.327 (RM salon) 'Language':'fr'
2019-05-03 22:46:20.327 (RM salon) 'UserDataFolder':'/home/pi/domoticz/'
2019-05-03 22:46:20.328 (RM salon) Device count: 8
2019-05-03 22:46:20.328 (RM salon) Device: 1 - ID: 44, Name: 'RM salon - Command', nValue: 1, sValue: '10'
2019-05-03 22:46:20.328 (RM salon) Device ID: '44'
2019-05-03 22:46:20.328 (RM salon) Device Name: 'RM salon - Command'
2019-05-03 22:46:20.328 (RM salon) Device nValue: 1
2019-05-03 22:46:20.328 (RM salon) Device sValue: '10'
2019-05-03 22:46:20.328 (RM salon) Device LastLevel: 10
2019-05-03 22:46:20.328 (RM salon) Device: 2 - ID: 47, Name: 'Ecran montée', nValue: 1, sValue: 'On-7'
2019-05-03 22:46:20.328 (RM salon) Device ID: '47'
2019-05-03 22:46:20.328 (RM salon) Device Name: 'Ecran montée'
2019-05-03 22:46:20.328 (RM salon) Device nValue: 1
2019-05-03 22:46:20.328 (RM salon) Device sValue: 'On-7'
2019-05-03 22:46:20.328 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.328 (RM salon) Device: 3 - ID: 48, Name: 'Ecran descente', nValue: 1, sValue: 'On-6'
2019-05-03 22:46:20.328 (RM salon) Device ID: '48'
2019-05-03 22:46:20.328 (RM salon) Device Name: 'Ecran descente'
2019-05-03 22:46:20.329 (RM salon) Device nValue: 1
2019-05-03 22:46:20.329 (RM salon) Device sValue: 'On-6'
2019-05-03 22:46:20.329 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.329 (RM salon) Device: 5 - ID: 50, Name: 'TV on/off', nValue: 1, sValue: 'On-2'
2019-05-03 22:46:20.329 (RM salon) Device ID: '50'
2019-05-03 22:46:20.329 (RM salon) Device Name: 'TV on/off'
2019-05-03 22:46:20.329 (RM salon) Device nValue: 1
2019-05-03 22:46:20.329 (RM salon) Device sValue: 'On-2'
2019-05-03 22:46:20.329 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.329 (RM salon) Device: 7 - ID: 52, Name: 'Projo on', nValue: 1, sValue: 'On-5'
2019-05-03 22:46:20.329 (RM salon) Device ID: '52'
2019-05-03 22:46:20.329 (RM salon) Device Name: 'Projo on'
2019-05-03 22:46:20.329 (RM salon) Device nValue: 1
2019-05-03 22:46:20.329 (RM salon) Device sValue: 'On-5'
2019-05-03 22:46:20.329 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.329 (RM salon) Device: 8 - ID: 53, Name: 'Projo off', nValue: 1, sValue: 'On-9'
2019-05-03 22:46:20.329 (RM salon) Device ID: '53'
2019-05-03 22:46:20.330 (RM salon) Device Name: 'Projo off'
2019-05-03 22:46:20.330 (RM salon) Device nValue: 1
2019-05-03 22:46:20.330 (RM salon) Device sValue: 'On-9'
2019-05-03 22:46:20.330 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.330 (RM salon) Device: 254 - ID: 45, Name: 'RM salon - Remote', nValue: 0, sValue: ''
2019-05-03 22:46:20.330 (RM salon) Device ID: '45'
2019-05-03 22:46:20.330 (RM salon) Device Name: 'RM salon - Remote'
2019-05-03 22:46:20.330 (RM salon) Device nValue: 0
2019-05-03 22:46:20.330 (RM salon) Device sValue: ''
2019-05-03 22:46:20.330 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.330 (RM salon) Device: 255 - ID: 46, Name: 'RM salon - Import', nValue: 0, sValue: 'Off'
2019-05-03 22:46:20.330 (RM salon) Device ID: '46'
2019-05-03 22:46:20.330 (RM salon) Device Name: 'RM salon - Import'
2019-05-03 22:46:20.330 (RM salon) Device nValue: 0
2019-05-03 22:46:20.330 (RM salon) Device sValue: 'Off'
2019-05-03 22:46:20.330 (RM salon) Device LastLevel: 0
2019-05-03 22:46:20.330 (RM salon) Pushing 'PollIntervalDirective' on to queue
2019-05-03 22:46:20.331 (RM salon - Import) Updating device from 0:'Off' to have values 0:'Off'.
2019-05-03 22:46:20.351 (RM salon) Update 0:'Off' (RM salon - Import)
2019-05-03 22:46:20.351 (RM salon) Connecting to: 192.168.1.97:780f77182d75
2019-05-03 22:46:20.942 (RM salon) Connected to Broadlink device: 192.168.1.97
2019-05-03 22:46:20.981 (RM salon) No ini file :/home/domoticz/plugins/BroadlinkRM2/remote/plugin_remote_16.ini
2019-05-03 22:46:20.981 (RM salon) Custom Commands for Remote not managed
2019-05-03 22:46:20.981 (RM salon) Device Number begin to : 6
and then :
2019-05-03 22:46:27.547 (RM salon) Processing 'PollIntervalDirective' message
2019-05-03 22:46:27.547 (RM salon) Heartbeat interval set to: 30.
2019-05-03 22:46:36.552 (RM salon) Pushing 'onHeartbeatCallback' on to queue
2019-05-03 22:46:36.603 (RM salon) Processing 'onHeartbeatCallback' message
2019-05-03 22:46:36.604 (RM salon) Calling message handler 'onHeartbeat'.

So I don't get what is making it wrong when it comes to start the web server...
Regarding teh rights, what is to be checked exactly to be correct?
zak45
Posts: 953
Joined: Sunday 22 January 2017 11:37
Target OS: Windows
Domoticz version: V2024.4
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by zak45 »

Loky31 wrote: Friday 03 May 2019 22:52
So I don't get what is making it wrong when it comes to start the web server...
Regarding teh rights, what is to be checked exactly to be correct?
yep, but necesary to me to be able to provide some help.
here is an example of what you should have (more or less)
usr@amlogic:~/domoticz/plugins/BroadlinkRM2$ ls -altr
total 88

-rw-r--r-- 1 usr root 43486 Feb 19 21:41 plugin.py
-rw-r--r-- 1 usr root 1518 Feb 22 16:57 plugin_send.py
-rw-r--r-- 1 usr root 58 Feb 22 16:57 plugin_send.cmd
-rw-r--r-- 1 usr root 11469 Feb 22 16:57 plugin_http.py
-rw-r--r-- 1 usr root 76 Feb 22 16:57 plugin_http.cmd
drwxr-xr-x 2 usr root 4096 Apr 20 10:16 __pycache__
-rwxr-xr-x 1 usr root 87 May 4 10:10 plugin_http.sh
drwxr-xr-x 3 usr root 4096 May 4 10:11 .
-rw-r--r-- 1 usr root 1480 May 4 10:13 nohup.out
usr@amlogic:~/domoticz/plugins/BroadlinkRM2$ cat plugin_http.sh
nohup python3 /home/usr/domoticz/plugins/BroadlinkRM2/plugin_http.py $1 $2 $3 $4 $5 &

usr@amlogic:~/domoticz/plugins/BroadlinkRM2$

This mean for you:
your plugin_http.sh file need to be under : /home/pi/domoticz/plugins/BroadlinkRM2/
you can put the same rights as in the example
the content of the .sh file need to have this :
nohup python3 /home/pi/domoticz/plugins/BroadlinkRM2/plugin_http.py $1 $2 $3 $4 $5 &

to test if this work, open terminal session and go to /home/pi/domoticz/plugins/BroadlinkRM2/
enter this command : nohup plugin_http.sh 0.0.0.0 9000 /home/pi/domoticz/

if something goes wrong, your will see it into nohup.out.
Loky31
Posts: 40
Joined: Monday 11 March 2019 13:46
Target OS: -
Domoticz version:
Contact:

Re: Python Plugin : Broadlink RM2 V4

Post by Loky31 »

Many Thanks, will try that asap but likely to be next weekend. Keep you posted of course ;)
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest