Domoticz

Posted: **Monday 02 December 2019 19:22**

Hello
sorry to raise a topic that has probably already been discussed but I can't find an answer in the forum (maybe I'm not looking well for it)
I am trying to establish a master-slave relationship between two Domoticz servers and strictly following the indications of the Wiki (Device Sharing)
and in the log I have the following messages:
2019-12-02 18:40:55.122 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-02 18:40:55.127 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-02 18:41:25.132 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-02 18:41:25.137 Error: Domoticz Remote: input buffer out of sync, going to restart!....

Master and slave are on two Rapsberry Pi on the same local network.

Thank for your help

Posted: **Tuesday 03 December 2019 18:56**

Hi,

Could you provide a little bit more information?

Regarding the posted log file:

2019-12-02 18:40:55.122 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-02 18:40:55.127 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-02 18:41:25.132 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-02 18:41:25.137 Error: Domoticz Remote: input buffer out of sync, going to restart!....

Is this logfile your master logfile or your slave logfile?
Which "hardware" devices has been connected to your slave?

Perhaps some screenshots of both master and slave configuration might be helpfull.

Regards

Posted: **Tuesday 03 December 2019 20:45**

This is the log on master side.

I have tested two configuration on slave side :

1) with a real sensor (a Xiaomi Temperature+Humidity Bluetooth sensor) installed as described on
https://franken3d.blog4ever.com/integre ... r-domoticz
which is the French translation of
https://github.com/pFenners/mijia-sensor-domoticz
2) with no hardware (to be sure that the bug doesn't come from python code), the sensor is purely virtual.

In both two configuration the messages in the log are the same.

Attached are some screen shots:

: This screen copy shows how the "hardware" is configured on master side; hardware-master.png (40.24 KiB) Viewed 5281 times

: This screen copy shows how the "hardware" is configured on slave side; hardware-slave.png (35.33 KiB) Viewed 5281 times

: this screen copy shows how device is configured on slave side; device-slave.png (33.49 KiB) Viewed 5281 times

Posted: **Tuesday 03 December 2019 20:48**

Screen copy (continuation)

: The virtual sensor on slave side; virtual-sensor-slave.png (24.12 KiB) Viewed 5281 times

: Th user configuration on slave side (to allows master to connect); user-slave.png (36.47 KiB) Viewed 5281 times

: the user device selection on slave side; user-device-selection-slave.png (20.06 KiB) Viewed 5281 times

Posted: **Tuesday 03 December 2019 20:53**

Additional information

Both two Raspberry Pi have the same version of Domoticz installed (the most recent)
I have read on an old post that it could be an issue of size of a buffer. But which buffer? How to resize it ?

Posted: **Tuesday 03 December 2019 22:50**

Hi.

Both two Raspberry Pi have the same version of Domoticz installed (the most recent)

In your profile, you indicate that you are running the latest version. I assume the latest stable version 4.10717.

As you said earlier, you followed the wiki
Let's do some checks:

1. In the slave you have set a password for the website protection.
2. Remote shared port 6144
3. In "Setup" => "More options" => "Edit Users" you have set a user with the password and gave him admin rights and setup the "Active Menus"
4. In the Master you have specified in "Settings" => "Hardware" the correct values for IP Address, Port (6144) and the previous Username and Password, as configured in the slave.

I suggest that you remove all hardware from your slave and install only "Motherboard Sensors" in your slave.
Do not forget the enable "New Hardware" in your Master.

This should function and you should see new sensors in your Master, representing the Motherboard Sensors of your slave.

Regards

Posted: **Wednesday 04 December 2019 4:20**

As shown below I have done the check you suggest and removed-replaced the hardware on slave side as suggested.
But I have the same error messages in the log of the master

2019-12-04 04:15:20.870 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-04 04:15:20.876 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-04 04:15:50.882 Status: Domoticz Remote: connected to: 192.168.1.66:6144
2019-12-04 04:15:50.886 Error: Domoticz Remote: input buffer out of sync, going to restart!....

See details below

In your profile, you indicate that you are running the latest version. I assume the latest stable version 4.10717

I confirm

1. In the slave you have set a password for the website protection.

YES

2. Remote shared port 6144

YES

In "Setup" => "More options" => "Edit Users" you have set a user etc ...

YES

4. In the Master you have specified in "Settings" => "Hardware" the correct etc ...

YES

I suggest that you remove all hardware from your slave and install only "Motherboard Sensors" in your slave.

DONE, see screen copy

: moter-board-sensors-slave.png (63.6 KiB) Viewed 5269 times

Do not forget the enable "New Hardware" in your Master.

What do you mean ? as on this screen copy ?

: hardware-master.png (40.24 KiB) Viewed 5269 times

Posted: **Wednesday 04 December 2019 8:10**

Something strange ...

Looking the log on master side this message is supposed to mean that the master is connected to slave

2019-12-04 08:03:44.695 Status: Domoticz Remote: connected to: 192.168.1.66:6144

But looking the log on salve side I can see only one incoming connection : this is the connection of my laptop.

2019-12-04 08:07:06.763 Status: Incoming connection from: 192.168.1.47

Should I see the master's connection (192.168.1.39) or is it treated separately?

Posted: **Wednesday 04 December 2019 14:57**

Hi

1. What I mean with:

Do not forget to enable "New Hardware" in your Master.

is the following:

In "Setup" => "Settings", you have the following option:

: Checkbox_Enable_hardware.png (69.95 KiB) Viewed 5247 times

Click the checkbox, marked "Accept new Hardware Devices" or click "Allow for 5 Minutes".

And don't forget in "Setup" => "Devices" to click the green arrow for your devices, so that it turns to blue
Otherwise you will not see the devices under the "Temperature" and "Utility" tab.

: Add_devices.png (4.29 KiB) Viewed 5247 times

You asked:

But looking the log on slave side I can see only one incoming connection : this is the connection of my laptop.

2019-12-04 08:07:06.763 Status: Incoming connection from: 192.168.1.47

Should I see the master's connection (192.168.1.39) or is it treated separately?

Yes, if you startup the Domoticz process in your slave you should see in "All" the following:

Code: Select all

2019-12-04 13:41:27.507 Sunrise: 08:28:00 SunSet: 16:28:00
2019-12-04 13:41:27.507 Day length: 07:60:00 Sun at south: 12:28:00
2019-12-04 13:41:27.507 Civil twilight start: 07:48:00 Civil twilight end: 17:08:00
2019-12-04 13:41:27.507 Nautical twilight start: 07:05:00 Nautical twilight end: 17:51:00
2019-12-04 13:41:27.507 Astronomical twilight start: 06:24:00 Astronomical twilight end: 18:32:00
2019-12-04 13:41:26.989 Status: Domoticz V4.11549 (c)2012-2019 GizMoCuz
2019-12-04 13:41:27.003 Status: Build Hash: 132e26f88, Date: 2019-12-04 11:18:39
2019-12-04 13:41:27.008 Status: Startup Path: /home/pi/domoticz/
2019-12-04 13:41:28.706 Active notification Subsystems: email (1/13)
2019-12-04 13:41:28.757 Starting shared server on: :::6144
2019-12-04 13:41:28.639 Status: PluginSystem: Started, Python version '3.5.3'.
2019-12-04 13:41:28.713 Status: WebServer(HTTP) started on address: :: with port 8080
2019-12-04 13:41:28.738 Status: WebServer(SSL) started on address: :: with port 443
2019-12-04 13:41:28.760 Status: TCPServer: shared server started...
2019-12-04 13:41:28.761 Status: RxQueue: queue worker started...
2019-12-04 13:41:30.766 Status: Hardware Monitor: Started
2019-12-04 13:41:30.798 Status: EventSystem: reset all events...
2019-12-04 13:41:30.800 Status: EventSystem: reset all device statuses...
2019-12-04 13:41:31.033 Status: PluginSystem: Entering work loop.
2019-12-04 13:41:31.672 Status: Python EventSystem: Initalizing event module.
2019-12-04 13:41:31.675 Status: EventSystem: Queue thread started...
2019-12-04 13:41:31.676 Status: EventSystem: Started
2019-12-04 13:41:57.792 Status: Incoming Domoticz connection from: 192.168.10.50
2019-12-04 13:43:48.789 Status: Incoming connection from: 127.0.0.1
2019-12-04 14:00:00.958 Status: Starting automatic database backup procedure...
2019-12-04 14:00:01.872 Status: Ending automatic database backup procedure...

In my case the "Master" has IP address: 192.168.10.50.

On the "Master", you see a line in the log, like:

2019-12-04 13:43:55.057 Status: Domoticz Remote: connected to: 192.168.10.51:6144

In my case the "Slave" has IP address: 192.168.10.51.

So in both machines you should see, that the "Master" is connected to the "Slave".

If the "Master" is updated, you should see in the "Master" log, lines, like:

2019-12-04 13:46:36.203 (Raspberry Pi 1) General/Percentage (Raspberry Pi 1 CPU_Usage)
2019-12-04 13:48:06.399 (Raspberry Pi 1) Temp (Raspberry Pi 1 Int. Temperature)
2019-12-04 13:48:06.416 (Raspberry Pi 1) General/Percentage (Raspberry Pi 1 CPU_Usage)
2019-12-04 13:49:36.558 (Raspberry Pi 1) General/Percentage (Raspberry Pi 1 HDD /boot)
2019-12-04 13:49:36.581 (Raspberry Pi 1) General/Percentage (Raspberry Pi 1 HDD /)

(Raspberry Pi 1 is the name of my "Slave")
You don't see anything on your "Slave".

So obviously, as you see only the connection of your laptop and not the Incoming Domoticz connection from your Domoticz "Master", I think that the connection not has been made. Strange.

Is there anything in your "Slave" that may prevent, that a connection is made?

Regards

Posted: **Wednesday 04 December 2019 21:13**

Thank you so much for your help.
I followed all your recommendations but the problem is persistent.

I suspect that this comes from my slave who also performs data transfers to the master using the MQTT (Mosquitto) protocol which can generate a conflict with device sharing.

Or maybe a problem on the master side running on a Raspberry type B which is a little obsolete. I will try an experiment with two other Rapsberry Pi dedicated exclusively to device sharing...

Posted: **Wednesday 04 December 2019 21:35**

No, that cannot be the reason.

My Domoticz "Slave" is a Raspberry Pi 1B, the first generation.
On that Pi, I have installed Mosquitto, Node-Red and Domoticz (latest beta)
I have multiple flows in Node Red communicating with my Domoticz "Master", using MQTT.
On Domoticz "Slave" I have only the Motherboard Sensors installed, and thats why I asked you to do the same. I have also MQTT communication with a Raspberry Pi 3+.

My Domoticz "Master" is a Raspberry Pi 2B.

So, I'm communicating between a RPi 1B and a RPi 2B with MQTT and Domoticz Remote server in parallel as well.

You can try a clean installation on new SD cards.
[Edit] I studied your error message once again.
It could be a buffer issue in your "Slave" RPi.
I suggest that you test with the same hardware, but with the latest beta release.
Buffers has been increased since 4.11079

Regards

Posted: **Thursday 05 December 2019 0:10**

Right : moving on new Rpi's doesn't change anything.

I have updated both master and slave with the last beta version

Now the log on master (a Rpi Zero W) is

2019-12-04 23:06:01.257 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-04 23:06:31.278 (Device Sharing) Security (Unknown)
2019-12-04 23:06:31.264 Status: Domoticz Remote: connected to: 192.168.1.87:6144
2019-12-04 23:06:31.277 Status: Domoticz Remote: disconnected from: 192.168.1.87:6144
2019-12-04 23:06:31.278 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-04 23:07:01.298 (Device Sharing) Security (Unknown)
2019-12-04 23:07:01.282 Status: Domoticz Remote: connected to: 192.168.1.87:6144
2019-12-04 23:07:01.299 Status: Domoticz Remote: disconnected from: 192.168.1.87:6144
2019-12-04 23:07:01.299 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-04 23:07:32.380 (Device Sharing) Security (Unknown)
2019-12-04 23:07:32.365 Status: Domoticz Remote: connected to: 192.168.1.87:6144
2019-12-04 23:07:32.372 Status: Domoticz Remote: disconnected from: 192.168.1.87:6144
2019-12-04 23:07:32.380 Error: UNHANDLED PACKET TYPE: FS20 68

And the log on slave (a Rpi model 3+) is

2019-12-04 23:01:31.096 Error: Error parsing http request.
2019-12-04 23:02:01.112 Error: Error parsing http request.
2019-12-04 23:02:31.130 Error: Error parsing http request.
2019-12-04 23:03:01.146 Error: Error parsing http request.
2019-12-04 23:03:31.163 Error: Error parsing http request.
2019-12-04 23:04:01.180 Error: Error parsing http request.
2019-12-04 23:04:31.202 Error: Error parsing http request.
2019-12-04 23:05:01.218 Error: Error parsing http request.
2019-12-04 23:05:31.230 Error: Error parsing http request.
2019-12-04 23:06:01.245 Error: Error parsing http request.
2019-12-04 23:06:31.264 Error: Error parsing http request.
2019-12-04 23:07:01.286 Error: Error parsing http request.
2019-12-04 23:07:32.365 Error: Error parsing http request.
2019-12-04 23:08:02.380 Error: Error parsing http request.
2019-12-04 23:08:32.481 Error: Error parsing http request.

I am really lucky ...

Posted: **Thursday 05 December 2019 0:11**

Seems now that the master connects and immediately disconnects

Posted: **Thursday 05 December 2019 9:44**

For an unknown reason it seems that the connection between master and slave tween cannot complete.
Maybe an issue with the router configuration ...

I will try to build a second independent LAN (using another router I have) and to connect the master and the slave on it.

Regards

Posted: **Thursday 05 December 2019 14:22**

HI,

I have seen that you use as "Master" a Raspberry PI Zero W.
Have you seen this topic: https://www.domoticz.com/forum/viewtopi ... =6&t=30414

I suggest, that you build a small network, consisting of 2 PI's, directly wired (not wireless) together.
And use the latest beta.

Regards

Posted: **Tuesday 10 December 2019 11:52**

Hi

I have done many test in various configuration.
I replaced the Rpi Zero by a Rpi model 3 with ethernet socket.

Both two Rpi run the last Beta version of Domoticz
I tested Wifi and Ethernet connection with my box as router or with another router independent of the box

But it don't work anyway.

So i think I am going to give up ...

Thanks again for your for your help.

Log on side of the master

2019-12-10 11:34:46.557 Status: Domoticz Remote: connected to: 192.168.253.102:6144
2019-12-10 11:34:46.563 Status: Domoticz Remote: disconnected from: 192.168.253.102:6144
2019-12-10 11:34:46.563 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-10 11:35:16.603 (Remote connection) Security ()
2019-12-10 11:35:16.571 Status: Domoticz Remote: connected to: 192.168.253.102:6144
2019-12-10 11:35:16.582 Status: Domoticz Remote: disconnected from: 192.168.253.102:6144
2019-12-10 11:35:16.603 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-10 11:35:46.600 (Remote connection) Security (Unknown)
2019-12-10 11:35:46.592 Status: Domoticz Remote: connected to: 192.168.253.102:6144
2019-12-10 11:35:46.599 Status: Domoticz Remote: disconnected from: 192.168.253.102:6144
2019-12-10 11:35:46.600 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-10 11:36:16.616 (Remote connection) Security (Unknown)
2019-12-10 11:36:16.607 Status: Domoticz Remote: connected to: 192.168.253.102:6144
2019-12-10 11:36:16.614 Status: Domoticz Remote: disconnected from: 192.168.253.102:6144
2019-12-10 11:36:16.616 Error: UNHANDLED PACKET TYPE: FS20 68

Log on side of the slave

2019-12-10 10:31:03.259 Status: Domoticz V4.11563 (c)2012-2019 GizMoCuz
2019-12-10 10:31:03.259 Status: Build Hash: d5e8a14bf, Date: 2019-12-09 19:21:24
2019-12-10 10:31:03.259 Status: Startup Path: /home/pi/domoticz/
2019-12-10 10:31:04.748 Sunrise: 07:33:00 SunSet: 15:54:00
2019-12-10 10:31:04.748 Day length: 08:22:00 Sun at south: 11:43:00
2019-12-10 10:31:04.748 Civil twilight start: 06:56:00 Civil twilight end: 16:31:00
2019-12-10 10:31:04.748 Nautical twilight start: 06:16:00 Nautical twilight end: 17:11:00
2019-12-10 10:31:04.748 Astronomical twilight start: 05:37:00 Astronomical twilight end: 17:49:00
2019-12-10 10:31:04.897 Active notification Subsystems: (0/13)
2019-12-10 10:31:04.880 Status: PluginSystem: Started, Python version '3.5.3'.
2019-12-10 10:31:04.900 Status: WebServer(HTTP) started on address: :: with port 6144
2019-12-10 10:31:04.909 Status: WebServer(SSL) started on address: :: with port 443
2019-12-10 10:31:04.916 Status: RxQueue: queue worker started...
2019-12-10 10:31:04.916 Error: Exception starting shared server: bind: Address already in use
2019-12-10 10:31:06.923 Status: Hardware Monitor: Started
2019-12-10 10:31:06.941 Status: EventSystem: reset all events...
2019-12-10 10:31:06.942 Status: EventSystem: reset all device statuses...
2019-12-10 10:31:07.145 Status: Python EventSystem: Initalizing event module.
2019-12-10 10:31:07.147 Status: EventSystem: Started
2019-12-10 10:31:07.147 Status: EventSystem: Queue thread started...
2019-12-10 10:31:07.250 Status: PluginSystem: Entering work loop.
2019-12-10 10:31:34.711 Error: Error parsing http request.
2019-12-10 10:32:04.735 Error: Error parsing http request.
2019-12-10 10:32:34.749 Error: Error parsing http request.
2019-12-10 10:34:46.560 Error: Error parsing http request.
2019-12-10 10:35:16.578 Error: Error parsing http request.

Posted: **Tuesday 10 December 2019 16:00**

Hi,

You wrote:

So i think I am going to give up ...

That's not in my vocabulary, however I cannot force you to go on.

Let us look to the slave first.

In the log of the slave I see:

2019-12-10 10:31:04.900 Status: WebServer(HTTP) started on address: :: with port 6144

Why did you change the web server's http to another value than 8080?
If there is any valid reason to do so, because you have planned to use this port for something else, you can change it. However do never change it to 6144, because this is the port that is used by Domoticz Remote server.
This will definitively cause a conflict and you will see that 3 lines later:

2019-12-10 10:31:04.916 Error: Exception starting shared server: bind: Address already in use

And this explains also:

2019-12-10 10:31:34.711 Error: Error parsing http request.
2019-12-10 10:32:04.735 Error: Error parsing http request.
2019-12-10 10:32:34.749 Error: Error parsing http request.
2019-12-10 10:34:46.560 Error: Error parsing http request.
2019-12-10 10:35:16.578 Error: Error parsing http request.

So lets change this first and I suggest to use port 8080.

nano /etc/init.d/domoticz.sh
Edit this line, so that it looks like: DAEMON_ARGS="$DAEMON_ARGS -www 8080"
If you open your editor, you will see 6144 as port. Change it to 8080
Leave the editor and give the following commands:
systemctl daemon-reload
service domoticz stop
service domoticz start.

If everything is alright, you will see:

Code: Select all

2019-12-09 21:11:35.866 Status: Domoticz V4.11563 (c)2012-2019 GizMoCuz
2019-12-09 21:11:35.871 Status: Build Hash: d5e8a14bf, Date: 2019-12-09 20:21:24
2019-12-09 21:11:35.873 Status: Startup Path: /home/pi/domoticz/
2019-12-09 21:11:36.281 Sunrise: 08:34:00 SunSet: 16:26:00
2019-12-09 21:11:36.282 Day length: 07:52:00 Sun at south: 12:30:00
2019-12-09 21:11:36.282 Civil twilight start: 07:53:00 Civil twilight end: 17:06:00
2019-12-09 21:11:36.282 Nautical twilight start: 07:10:00 Nautical twilight end: 17:50:00
2019-12-09 21:11:36.282 Astronomical twilight start: 06:29:00 Astronomical twilight end: 18:31:00
2019-12-09 21:11:37.478 Active notification Subsystems: email (1/13)
2019-12-09 21:11:37.584 Starting shared server on: :::6144
2019-12-09 21:11:37.359 Status: PluginSystem: Started, Python version '3.5.3'.
2019-12-09 21:11:37.486 Status: WebServer(HTTP) started on address: :: with port 8080
2019-12-09 21:11:37.544 Status: WebServer(SSL) started on address: :: with port 443
2019-12-09 21:11:37.593 Status: TCPServer: shared server started...
2019-12-09 21:11:37.593 Status: RxQueue: queue worker started...
2019-12-09 21:11:39.599 Status: Hardware Monitor: Started
2019-12-09 21:11:39.630 Status: EventSystem: reset all events...
2019-12-09 21:11:39.635 Status: EventSystem: reset all device statuses...
2019-12-09 21:11:39.804 Status: PluginSystem: Entering work loop.
2019-12-09 21:11:40.346 Status: Python EventSystem: Initalizing event module.
2019-12-09 21:11:40.349 Status: EventSystem: Queue thread started...
2019-12-09 21:11:40.350 Status: EventSystem: Started
2019-12-09 21:12:06.563 Status: Incoming Domoticz connection from: 192.168.10.50

Let"s try this first.

Regards

Posted: **Tuesday 10 December 2019 16:32**

Hi,

That's not in my vocabulary, however I cannot force you to go on.

Generally it's not in my vocabulary too

Ok let's continue ...

I will apply your recommendations and let you know ...

Write you later.

Best regards

Posted: **Tuesday 10 December 2019 23:15**

Done as you recommended.
See log below.
Note that

Error: Error parsing http request.

appears only after upgrading to the beta version

Log on slave (ip=192.168.253.100)

2019-12-10 21:49:43.907 Status: Domoticz V4.11563 (c)2012-2019 GizMoCuz
2019-12-10 21:49:43.909 Status: Build Hash: d5e8a14bf, Date: 2019-12-09 19:21:24
2019-12-10 21:49:43.911 Status: Startup Path: /home/pi/domoticz/
2019-12-10 21:49:49.101 Sunrise: 07:33:00 SunSet: 15:54:00
2019-12-10 21:49:49.102 Day length: 08:22:00 Sun at south: 11:43:00
2019-12-10 21:49:49.102 Civil twilight start: 06:56:00 Civil twilight end: 16:31:00
2019-12-10 21:49:49.102 Nautical twilight start: 06:16:00 Nautical twilight end: 17:11:00
2019-12-10 21:49:49.102 Astronomical twilight start: 05:37:00 Astronomical twilight end: 17:49:00
2019-12-10 21:49:49.351 Active notification Subsystems: (0/13)
2019-12-10 21:49:49.367 Starting shared server on: :::6144
2019-12-10 21:49:49.334 Status: PluginSystem: Started, Python version '3.5.3'.
2019-12-10 21:49:49.353 Status: WebServer(HTTP) started on address: :: with port 8080
2019-12-10 21:49:49.362 Status: WebServer(SSL) started on address: :: with port 443
2019-12-10 21:49:49.368 Status: RxQueue: queue worker started...
2019-12-10 21:49:49.368 Status: TCPServer: shared server started...
2019-12-10 21:49:51.369 Status: EventSystem: reset all events...
2019-12-10 21:49:51.370 Status: EventSystem: reset all device statuses...
2019-12-10 21:49:51.513 Status: Python EventSystem: Initalizing event module.
2019-12-10 21:49:51.513 Status: EventSystem: Started
2019-12-10 21:49:51.513 Status: EventSystem: Queue thread started...
2019-12-10 21:49:51.603 Status: PluginSystem: Entering work loop.
2019-12-10 21:54:23.953 Status: Hardware Monitor: Started
2019-12-10 21:54:51.775 Error: Error parsing http request.
2019-12-10 21:55:21.790 Error: Error parsing http request.
2019-12-10 21:55:51.806 Error: Error parsing http request.
2019-12-10 21:56:21.822 Error: Error parsing http request.
2019-12-10 21:56:51.838 Error: Error parsing http request.

Log on master (ip=192.168.253.101)

2019-12-10 22:53:46.560 Sunrise: 08:33:00 SunSet: 16:54:00
2019-12-10 22:53:46.560 Day length: 08:22:00 Sun at south: 12:43:00
2019-12-10 22:53:46.560 Civil twilight start: 07:56:00 Civil twilight end: 17:31:00
2019-12-10 22:53:46.560 Nautical twilight start: 07:16:00 Nautical twilight end: 18:11:00
2019-12-10 22:53:46.560 Astronomical twilight start: 06:37:00 Astronomical twilight end: 18:49:00
2019-12-10 22:53:46.569 Active notification Subsystems: (0/13)
2019-12-10 22:53:46.581 Starting shared server on: :::6144
2019-12-10 22:53:46.524 Status: Domoticz V4.11563 (c)2012-2019 GizMoCuz
2019-12-10 22:53:46.524 Status: Build Hash: d5e8a14bf, Date: 2019-12-09 20:21:24
2019-12-10 22:53:46.524 Status: Startup Path: /home/pi/domoticz/
2019-12-10 22:53:46.560 Status: PluginSystem: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.
2019-12-10 22:53:46.572 Status: WebServer(HTTP) started on address: :: with port 8080
2019-12-10 22:53:46.579 Status: WebServer(SSL) started on address: :: with port 443
2019-12-10 22:53:46.582 Status: RxQueue: queue worker started...
2019-12-10 22:53:46.582 Status: TCPServer: shared server started...
2019-12-10 22:53:48.584 Status: EventSystem: reset all events...
2019-12-10 22:53:48.585 Status: EventSystem: reset all device statuses...
2019-12-10 22:53:48.586 Status: EventSystem - Python: Failed dynamic library load, install the latest libpython3.x library that is available for your platform.
2019-12-10 22:53:48.587 Status: EventSystem: Started
2019-12-10 22:53:48.587 Status: EventSystem: Queue thread started...
2019-12-10 22:54:51.775 Status: Domoticz Remote: connected to: 192.168.253.100:8080
2019-12-10 22:54:51.781 Status: Domoticz Remote: disconnected from: 192.168.253.100:8080
2019-12-10 22:54:51.781 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-10 22:55:21.811 (Master) Security ()
2019-12-10 22:55:21.789 Status: Domoticz Remote: connected to: 192.168.253.100:8080
2019-12-10 22:55:21.795 Status: Domoticz Remote: disconnected from: 192.168.253.100:8080
2019-12-10 22:55:21.811 Error: UNHANDLED PACKET TYPE: FS20 68
2019-12-10 22:55:51.814 (Master) Security (Unknown)
2019-12-10 22:55:51.805 Status: Domoticz Remote: connected to: 192.168.253.100:8080
2019-12-10 22:55:51.811 Status: Domoticz Remote: disconnected from: 192.168.253.100:8080

Note the message

Python: Failed dynamic library load, install the latest libpython3.x library ...

Seems to be an old bug discussed on the forum

Posted: **Tuesday 10 December 2019 23:40**

Hi,

For the moment I suggest that you disconnect your master from your network. I wonder who is making a http request. It is exactly 30 seconds.
Is there anything else that tries to connect with the slave? Another Pi? Wireless?

Regards

Domoticz

Device Sharing

Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing

Re: Device Sharing