RPIEasy

[enesbcs]

Thanks for the reply.
Actually I tried to set the intervals to 300, 301, 302, ... 305 seconds, but the logs were created with no intervals set.
I'll give the new version a try tonight.

1 second between BLE devices is not a good choice, as they sometimes needs 1-5 seconds to connect. Leave 5-10 seconds between each other for safety.

[pitias]

I tried the new version tonight. Settings are like you asked them to be (checked "Connect only if BLE local device free" and intervals 91, 101, 111, ...), the effect seems to be the same. It got stuck after 15mins.

Right now I'm trying a new location with an other power supply. The one I used before was a Samsung phone charger with 2.0A, the new one is QC3.0 compatible. The new location is approx. 5m away from the router.
Let's if this makes a difference.

Is there a way to see the RSSI once a device is declared? Or can it only be seen on the hardware tab during the initial scan? I'd like to figure out, if the new location is an overall better place than the original position.

Code: Select all

May 11 22:15:12 RPIEasy RPIEasy: Pi Zero W 40 pins
May 11 22:15:13 RPIEasy RPIEasy: Event: System#Boot
May 11 22:15:13 RPIEasy RPIEasy: Webserver starting at port 80
May 11 22:15:13 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:15
May 11 22:15:17 RPIEasy RPIEasy: Pi Zero W 40 pins
May 11 22:15:18 RPIEasy RPIEasy: Event: System#Boot
May 11 22:15:18 RPIEasy RPIEasy: Webserver starting at port 8080
May 11 22:15:19 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:15
May 11 22:15:19 RPIEasy RPIEasy: Event: Network#Connected
May 11 22:15:19 piHWRzero systemd[1]: Stopping User Manager for UID 1000...
May 11 22:15:19 piHWRzero systemd[22757]: Stopped target Default.
May 11 22:15:19 piHWRzero systemd[22757]: Stopped target Basic System.
May 11 22:15:19 piHWRzero systemd[22757]: Stopped target Sockets.
May 11 22:15:19 piHWRzero systemd[22757]: dirmngr.socket: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Closed GnuPG network certificate management daemon.
May 11 22:15:19 piHWRzero systemd[22757]: gpg-agent-extra.socket: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
May 11 22:15:19 piHWRzero systemd[22757]: gpg-agent.socket: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Closed GnuPG cryptographic agent and passphrase cache.
May 11 22:15:19 piHWRzero systemd[22757]: Stopped target Timers.
May 11 22:15:19 piHWRzero systemd[22757]: Stopped target Paths.
May 11 22:15:19 piHWRzero systemd[22757]: gpg-agent-browser.socket: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
May 11 22:15:19 piHWRzero systemd[22757]: gpg-agent-ssh.socket: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Closed GnuPG cryptographic agent (ssh-agent emulation).
May 11 22:15:19 piHWRzero systemd[22757]: Reached target Shutdown.
May 11 22:15:19 piHWRzero systemd[22757]: systemd-exit.service: Succeeded.
May 11 22:15:19 piHWRzero systemd[22757]: Started Exit the Session.
May 11 22:15:19 piHWRzero systemd[22757]: Reached target Exit the Session.
May 11 22:15:19 piHWRzero systemd[1]: user@1000.service: Succeeded.
May 11 22:15:19 piHWRzero systemd[1]: Stopped User Manager for UID 1000.
May 11 22:15:19 piHWRzero systemd[1]: Stopping User Runtime Directory /run/user/1000...
May 11 22:15:19 piHWRzero systemd[1]: run-user-1000.mount: Succeeded.
May 11 22:15:19 piHWRzero systemd[1]: user-runtime-dir@1000.service: Succeeded.
May 11 22:15:19 piHWRzero systemd[1]: Stopped User Runtime Directory /run/user/1000.
May 11 22:15:19 piHWRzero systemd[1]: Removed slice User Slice of UID 1000.
May 11 22:16:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:16
May 11 22:16:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:16
May 11 22:16:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:16:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:16:47 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:16:49 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:16:49 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:16:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:16:51 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:16:51 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:16:57 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:16:58 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.9
May 11 22:16:58 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:16:58 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:16:58 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:16:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:17
May 11 22:17:00 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:17:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:17
May 11 22:17:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:02 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:17:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:04 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:17:04 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:17:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:05 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:07 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:17:08 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:11 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:17:11 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:17:11 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:17:14 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:17:17 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:17:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:20 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:22 RPIEasy RPIEasy: BLE connection failed a4:c1:38:00:e8:ec
May 11 22:17:22 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:17:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:23 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:24 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:25 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:25 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:17:28 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:17:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:29 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:29 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:33 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:34 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:34 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:17:35 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:17:35 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:40 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:41 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:42 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:42 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:17:43 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:17:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:45 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:17:49 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:17:52 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:17:53 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:54 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:54 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:17:54 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:17:54 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:17:54 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:17:54 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:17:55 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:17:55 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:17:55 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:17:56 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:17:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:18
May 11 22:18:01 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:18
May 11 22:18:01 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:18:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:18:03 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:18:04 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:18:04 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=35.0
May 11 22:18:04 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:18:04 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:18:04 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:18:04 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:18:05 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:18:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:18:12 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:18:13 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:18:14 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:18:17 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:18:17 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:18:17 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:18:17 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:18:17 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:18:18 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:18:18 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:18:18 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:18:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:20 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:18:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:18:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:18:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:18:24 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:18:25 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:28 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:18:29 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:18:29 RPIEasy RPIEasy: Event: xi_fe#Humidity=38.0
May 11 22:18:29 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:18:29 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:18:31 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:31 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:18:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:18:37 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:18:42 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:18:43 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:18:43 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:18:45 RPIEasy RPIEasy: BLE connected to a4:c1:38:4b:8c:5f
May 11 22:18:45 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:18:47 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:18:48 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:18:53 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:18:58 RPIEasy RPIEasy: Event: xiDach#Temperature=24.6
May 11 22:18:58 RPIEasy RPIEasy: Event: xiDach#Humidity=38.0
May 11 22:18:58 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 11 22:18:58 RPIEasy RPIEasy: Sending task 5 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:18:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:18:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:19
May 11 22:19:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:19
May 11 22:19:01 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:02 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:03 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:05 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:05 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:07 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:19:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:09 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:19:09 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:19:09 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:19:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:11 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:11 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:19:18 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:19:22 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:19:22 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:19:22 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:19:22 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:19:22 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:19:22 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:19:42 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:19:51 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:19:52 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:19:56 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:19:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:20:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:20
May 11 22:20:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:20
May 11 22:20:04 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:20:05 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:20:05 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:20:05 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:20:05 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:20:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:20:08 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:20:11 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:20:14 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:20:16 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:20:16 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:20:16 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:20:16 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:20:17 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:20:24 RPIEasy RPIEasy: BLE connected to a4:c1:38:4b:8c:5f
May 11 22:20:26 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:20:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:20:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:20:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:20:28 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:20:38 RPIEasy RPIEasy: Event: xiDach#Temperature=24.6
May 11 22:20:38 RPIEasy RPIEasy: Event: xiDach#Humidity=38.0
May 11 22:20:38 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 11 22:20:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:20:46 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:20:47 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:20:47 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:20:47 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:20:47 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:20:47 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:20:48 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:20:48 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:20:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:20:52 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:20:54 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:20:54 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:20:55 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:20:55 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:20:55 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:20:55 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:20:55 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:20:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:20:57 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:20:58 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:20:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:21
May 11 22:21:00 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:21
May 11 22:21:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:02 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:04 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:21:05 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:06 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:21:09 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:09 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:21:09 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:21:10 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:21:10 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:18 RPIEasy RPIEasy: BLE connected to a4:c1:38:4b:8c:5f
May 11 22:21:20 RPIEasy RPIEasy: Event: xiDach#Temperature=24.7
May 11 22:21:20 RPIEasy RPIEasy: Event: xiDach#Humidity=38.0
May 11 22:21:20 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 11 22:21:20 RPIEasy RPIEasy: Sending task 5 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:21:21 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:22 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:23 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:21:23 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:25 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:21:25 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:21:25 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:21:25 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:21:25 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:21:26 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:21:30 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:21:31 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:21:31 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:21:31 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:21:31 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:21:54 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:22:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:22
May 11 22:22:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:22
May 11 22:22:12 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:22:15 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:22:15 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:22:15 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:22:15 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:22:16 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:22:24 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:22:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:22:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:22:28 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:22:28 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:22:29 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:22:33 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:22:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:22:34 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:22:34 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:22:34 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:22:34 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:22:44 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:22:49 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:22:49 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=35.0
May 11 22:22:49 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:22:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:22:56 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:22:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:22:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:22:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:22:57 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:22:58 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:23:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:23
May 11 22:23:01 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:23
May 11 22:23:03 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:23:07 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:23:07 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:23:07 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:23:07 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:23:08 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:15 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:16 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:27 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:28 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:29 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:30 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:31 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:32 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:35 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:38 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:40 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:42 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:43 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:45 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:45 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:45 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:23:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:53 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:23:54 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:23:54 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:23:54 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:23:55 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:23:56 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:23:58 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:00 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:01 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:24
May 11 22:24:01 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:24
May 11 22:24:02 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:03 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:05 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:06 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:09 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:11 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:14 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:16 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:17 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:20 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:22 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:23 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:25 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:25 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:24:28 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:24:29 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:24:35 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:24:38 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:24:38 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:24:38 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:24:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:24:40 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:24:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:24:45 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:24:50 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:24:50 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=36.0
May 11 22:24:50 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:24:50 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:24:51 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:24:57 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:24:58 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:24:58 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:24:58 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:24:58 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:24:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:25:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:25
May 11 22:25:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:25
May 11 22:25:07 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:25:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:25:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:00:e8:ec
May 11 22:25:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:25:29 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:25:31 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:25:31 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:25:31 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:25:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:25:38 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:25:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:25:41 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:25:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:25:45 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:25:50 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:25:50 RPIEasy RPIEasy: Event: xiBad#Temperature=23.4
May 11 22:25:50 RPIEasy RPIEasy: Event: xiBad#Humidity=44.0
May 11 22:25:50 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:25:50 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:25:51 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:25:51 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:25:57 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:25:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:25:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=35.0
May 11 22:25:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:25:58 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:25:59 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:26
May 11 22:26:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:26
May 11 22:26:01 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:26:03 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:26:09 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.6
May 11 22:26:09 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:26:09 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:26:09 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:26:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:11 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:12 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:13 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:26:15 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:26:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.8
May 11 22:26:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:26:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:26:17 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:18 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:18 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:26:24 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:26:27 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:26:27 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:26:27 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:26:27 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:26:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:26:33 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.4
May 11 22:26:33 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=35.0
May 11 22:26:33 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:26:33 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:26:33 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:26:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:35 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:37 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:40 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:41 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:42 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:43 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:26:50 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:52 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:26:55 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:26:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:26:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=36.0
May 11 22:26:57 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:26:57 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:26:58 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:26:58 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:26:59 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:27:00 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:27
May 11 22:27:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:27
May 11 22:27:01 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:27:01 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:27:02 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:27:02 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:27:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:03 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:05 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:07 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:09 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:09 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:10 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:27:11 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:14 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:27:14 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:15 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=37.0
May 11 22:27:18 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:27:18 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:27:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:24 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:25 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:27 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:29 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:30 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:27:32 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:39 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:27:41 RPIEasy RPIEasy: Event: xiBad#Temperature=23.2
May 11 22:27:41 RPIEasy RPIEasy: Event: xiBad#Humidity=42.0
May 11 22:27:41 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:27:41 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:27:43 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:27:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:45 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:27:49 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:27:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:27:55 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:27:56 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.3
May 11 22:27:56 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=34.0
May 11 22:27:56 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:27:56 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:27:57 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:27:59 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:28:00 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:28:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:28
May 11 22:28:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:28
May 11 22:28:03 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:28:09 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:28:09 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:28:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:28:11 RPIEasy RPIEasy: BLE connection failed a4:c1:38:00:e8:ec
May 11 22:28:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:28:12 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:28:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:28:20 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:28:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:28:36 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:28:36 piHWRzero dhcpcd[418]: wlan0: carrier lost
May 11 22:28:36 piHWRzero avahi-daemon[253]: Withdrawing address record for 192.168.2.19 on wlan0.
May 11 22:28:36 piHWRzero avahi-daemon[253]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.19.
May 11 22:28:46 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:28:47 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:28:54 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:28:55 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:28:58 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:29:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:29
May 11 22:29:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:29:06 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.3
May 11 22:29:06 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=34.0
May 11 22:29:06 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:29:06 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:29
May 11 22:29:07 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:29:08 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:29:10 RPIEasy RPIEasy: Event: xiBad#Temperature=23.0
May 11 22:29:10 RPIEasy RPIEasy: Event: xiBad#Humidity=43.0
May 11 22:29:10 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:29:10 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:29:11 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:29:12 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:29:13 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:29:14 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:29:15 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:29:16 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:29:16 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:29:18 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:29:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:29:20 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:29:21 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:29:21 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=34.0
May 11 22:29:21 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:29:21 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:29:21 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:29:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:29:23 RPIEasy RPIEasy: BLE connection failed a4:c1:38:18:ba:41
May 11 22:29:23 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:29:23 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:29:27 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:29:27 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=36.0
May 11 22:29:27 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:29:27 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:29:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:29:32 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:29:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:29:34 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:29:34 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:29:34 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=35.0
May 11 22:29:34 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:29:34 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:29:36 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:29:36 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:29:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:29:39 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:29:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:29:42 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:29:43 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 11 22:29:43 RPIEasy RPIEasy: Event: xi_fe#Humidity=37.0
May 11 22:29:43 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 11 22:29:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:29:46 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:29:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:29:51 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:29:55 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:29:55 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=36.0
May 11 22:29:55 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:29:55 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:29:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:29:57 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:30:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:30
May 11 22:30:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:30
May 11 22:30:01 piHWRzero rsyslogd: action 'action-13-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1901.0 try https://www.rsyslog.com/e/2359 ]
May 11 22:30:01 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:30:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:02 RPIEasy RPIEasy: Event: xiBad#Temperature=23.0
May 11 22:30:02 RPIEasy RPIEasy: Event: xiBad#Humidity=43.0
May 11 22:30:02 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:30:02 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:30:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:05 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:06 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:08 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=22.2
May 11 22:30:08 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=34.0
May 11 22:30:08 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 11 22:30:08 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:30:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:10 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:11 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:30:17 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:30:23 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:24 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:26 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:27 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:29 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:30 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:31 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:35 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:36 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:38 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:40 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:40 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:40 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:30:42 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:30:43 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:30:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:30:45 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:30:50 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 11 22:30:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:31:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:31
May 11 22:31:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:31
May 11 22:31:00 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:31:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:31:06 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:31:10 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:31:10 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:31:11 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:31:11 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=35.0
May 11 22:31:11 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:31:11 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:31:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:31:12 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:31:17 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:31:17 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=35.0
May 11 22:31:17 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:31:18 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:31:19 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:31:23 RPIEasy RPIEasy: Event: xiBad#Temperature=23.0
May 11 22:31:23 RPIEasy RPIEasy: Event: xiBad#Humidity=43.0
May 11 22:31:23 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:31:23 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:31:24 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:31:25 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 11 22:31:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:31:36 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:31:36 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:31:37 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 11 22:31:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:31:39 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:31:40 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:31:40 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=36.0
May 11 22:31:40 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:31:40 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:31:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:31:43 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:31:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:31:45 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:31:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:31:55 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:31:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:31:56 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:31:57 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 11 22:32:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:32
May 11 22:32:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:32
May 11 22:32:02 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 11 22:32:07 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.1
May 11 22:32:07 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=36.0
May 11 22:32:07 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 11 22:32:07 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:32:08 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:32:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:32:09 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:32:19 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:32:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:32:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:32:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:32:27 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:32:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:32:32 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:32:33 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:32:34 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:32:34 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:32:39 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:32:39 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 11 22:32:44 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 11 22:32:49 RPIEasy RPIEasy: Event: xiBad#Temperature=23.0
May 11 22:32:49 RPIEasy RPIEasy: Event: xiBad#Humidity=43.0
May 11 22:32:49 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 11 22:32:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:32:57 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:32:58 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:33:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:33
May 11 22:33:00 RPIEasy RPIEasy: Event: Clock#Time=Mon,22:33
May 11 22:33:02 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 11 22:33:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:33:04 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 11 22:33:05 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:33:15 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:33:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:33:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=35.0
May 11 22:33:16 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:33:16 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 11 22:33:17 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 11 22:33:19 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:33:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 11 22:33:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 11 22:33:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 11 22:33:32 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 11 22:33:37 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.7
May 11 22:33:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 11 22:33:37 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=35.0
May 11 22:33:37 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 11 22:33:37 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy

[enesbcs]

Is there a way to see the RSSI once a device is declared? Or can it only be seen on the hardware tab during the initial scan? I'd like to figure out, if the new location is an overall better place than the original position.

There are a BLE scan device which can scan for online BLE devices - with RSSI... but scan mode can only be active when noone else using BLE dongle.

[pitias]

I'll give it a shot, once it's stuck again
Right now it has been running smoothly for last 6 hours.

[pitias]

As RPIEasy has been running smoothly for the last two days, I'm going to change the power supply in order to check the influence.
Something I observed is that there are periods when data is received quite frequently, temperatures are received more often than humidities. On the other hand, tonight there was a period of four hours with no new temperature for a sensor which shows changes pretty often during the day.
Does RPIEasy only show changed values?

[BertrandP]

Hi.
I try to install RPIEasy, but I have those error :

root@RPi0Jardin:/home/pi/rpieasy# ./RPIEasy.py
Init hardware...
Load network settings...
Load GPIO settings...
RPi.GPIO not installed!
I2C smbus not installed!
GPIO init failed
Creating new pinout
Load devices from file
Load controllers from file
Load notifiers from file
17:40:28: Event: System#Boot
17:40:28: Event: Clock#Time=Thu,17:40
17:40:28: Event: Network#Connected
17:40:28: !Webserver can not be started, no available port found!

How install RPI.GPIO ans I2C ?
Do I need to install apach or another things ?

Thanks.

[enesbcs]

How install RPI.GPIO ans I2C ?
Do I need to install apach or another things ?

Every dependency can be installed from inside the RPIEasy plugins&dependencies page.
Webserver is provided by the minimal Perver python web server, using only base python libraries. (threading, asyncio, urllib)

17:40:28: !Webserver can not be started, no available port found!

This error message tells, that either you are running multiple http servers/rpieasy already in the background and there are no more free ports found, or there are network library problem as socket.socket() / socket.gethostname() call failed on you installation.

Can yo try to run the following python code to see if any errors written on the linux console?

nettest.py content:

Code: Select all

import socket
servers = socket.socket(socket.AF_INET,socket.SOCK_STREAM)
servers.bind((socket.gethostname(), 8080))
servers.close()

[BertrandP]

I got this :

root@RPi0Jardin:/home/pi# python nettest.py
Traceback (most recent call last):
File "nettest.py", line 3, in <module>
servers.bind((socket.gethostname(), 8080))
File "/usr/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
socket.gaierror: [Errno -2] Name or service not known

[enesbcs]

socket.gaierror: [Errno -2] Name or service not known

You are somehow using a system that is unable to resolve its own name. I've never seen similar before.
https://github.com/pahaz/sshtunnel/issues/56
https://github.com/alessandromaggio/pyt ... /issues/28

Can you use internet on this machine? Is the DNS server is your local router?

update: i've tried to workaround it in todays commit, please download fresh version from github

[pitias]

I'm having a little trouble with my wifi connection and therefore I'm pinging my router every 15min as a sudo cron-job. If there is no answer, the machine will reboot.
Using the brutal method with a reboot is working, RPIEasy starts up as wanted with all devices and the controller.

Code: Select all

#!/bin/bash
ROUTER=192.168.2.8
if ! ping -c 1 -W 3 -I wlan0 -q $ROUTER;
then
  /sbin/reboot
fi

When I try to keep the machine alive and restart the wifi only, I figured out that I have to restart RPIEasy as well. (Do I have to restart bluetooth as well? If yes, how do I do this?)
But after killing and restarting the machine the devices and the controller are not loaded in RPIEasy. I have to reload them using the tools menu.
Is there a more gracefull way of telling RPIEasy to restart rather than using the system reboot?

Code: Select all

#!/bin/bash
ROUTER=192.168.2.8
if ! ping -c 1 -W 3 -I wlan0 -q $ROUTER;
then
  /etc/init.d/networking restart
  /sbin/mii-tool -F 10baseT-HD
# kill RPIEasy and restart it
  /usr/bin/pkill -f Easy
  /usr/bin/python3 /home/pi/tools/rpieasy/RPIEasy.py
  echo Netzwerk und RPIEasy sollten neu gestartet sein
fi

[enesbcs]

Is there a more gracefull way of telling RPIEasy to restart rather than using the system reboot?

Yes, for example something like that will work (from a bash script), if you are using the default startup run.sh to autostart RPIEasy:

Code: Select all

curl http://localhost/?cmd=exit

If you are using run.sh and killing it, it also autostarts itself, and if you forcing to start another instance than the Tasks and Controllers may be empty, as 2 instance try to use 1 data directory. I have to implement some self-defence against multiple instancing in the future.

Otherwise RPIEasy has its own ping plugin, and simple logic also can be added to Rules.

[BertrandP]

Yes I can acces to internet, update and upgrate the Pi. Yes the DNS is in my box (french Freebox revolution).
I try to delet the forlder and update today from github, but it's the same.

[enesbcs]

Yes I can acces to internet, update and upgrate the Pi. Yes the DNS is in my box (french Freebox revolution).
I try to delet the forlder and update today from github, but it's the same.

Sorry, i think i've found the error, you are using an incompatible old python version:
"/usr/lib/python2.7/socket.py"

I did not interpret this line before, RPIEasy works with Python >v3.4. Try to remove Python 2.7 completely and retry, and install Python3 as instructed by the rpieasy page:
https://github.com/enesbcs/rpieasy

Python 2.7 was ended finally by the Python developers at 2020.01.01 RIP. Say a short goodbye to it.
https://www.python.org/doc/sunset-python-2/

[BertrandP]

I'ts better, but still not work :

root@RPi0Jardin:/home/pi# python --version
Python 3.7.3
root@RPi0Jardin:/home/pi# rpieasy/RPIEasy.py
Init hardware...
Load network settings...
Load GPIO settings...
RPi.GPIO not installed!
I2C smbus not installed!
GPIO init failed
Creating new pinout
Load devices from file
Load controllers from file
Load notifiers from file
10:24:41: Event: System#Boot
10:24:41: Event: Clock#Time=Sun,10:24
10:24:41: Event: Network#Connected
10:24:42: !Webserver can not be started, no available port found!

root@RPi0Jardin:/home/pi# python nettest.py
Traceback (most recent call last):
File "nettest.py", line 3, in <module>
servers.bind((socket.gethostname(), 8080))
socket.gaierror: [Errno -2] Name or service not known

[enesbcs]

root@RPi0Jardin:/home/pi# python nettest.py
Traceback (most recent call last):
File "nettest.py", line 3, in <module>
servers.bind((socket.gethostname(), 8080))
socket.gaierror: [Errno -2] Name or service not known

This nettest.py is not relevant anymore.

The latest RPIEasy.py are using gethostname by exception handling and with failover to localhost:

Code: Select all

 
 try:
  ownaddr = socket.gethostname()
 except:
  ownaddr = '127.0.0.1'

So in theory the error can be if all ports are used by other applications.

Please try to run the following linux command and let me know the results:

Code: Select all

sudo netstat -l -p --numeric-ports --numeric-hosts -n | grep 80

I've added more debug informations to RPIEasy.py output in current commit today.

[BertrandP]

There is nothing else on the RPI0. it's a proper install from 2020-02-13-raspbian-buster-lite.img

for information :

root@RPi0Jardin://etc# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

this is the result for netstat :

root@RPi0Jardin://etc# netstat -l -p --numeric-ports --numeric-hosts -n
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 415/sshd
tcp 0 0 0.0.0.0:55008 0.0.0.0:* LISTEN 527/python3
tcp6 0 0 :::22 :::* LISTEN 415/sshd
udp 0 0 0.0.0.0:40221 0.0.0.0:* 232/avahi-daemon: r
udp 0 0 0.0.0.0:68 0.0.0.0:* 409/dhcpcd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 232/avahi-daemon: r
udp6 0 0 :::38886 :::* 232/avahi-daemon: r
udp6 0 0 :::5353 :::* 232/avahi-daemon: r
raw6 0 0 :::58 :::* 7 409/dhcpcd
Sockets du domaine UNIX actives(seulement serveurs)
Proto RefCnt Flags Type State I-Node PID/Program name Chemin
unix 2 [ ACC ] STREAM LISTENING 11824 409/dhcpcd /var/run/dhcpcd.sock
unix 2 [ ACC ] STREAM LISTENING 11828 409/dhcpcd /var/run/dhcpcd.unpriv.sock
unix 2 [ ACC ] STREAM LISTENING 10545 1/init /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 6708 1/init /run/systemd/fsck.progress
unix 2 [ ACC ] STREAM LISTENING 10563 1/init /run/thd.socket
unix 2 [ ACC ] STREAM LISTENING 13652 474/systemd /run/user/1001/systemd/private
unix 2 [ ACC ] STREAM LISTENING 13659 474/systemd /run/user/1001/gnupg/S.gpg-agent.browser
unix 2 [ ACC ] STREAM LISTENING 13662 474/systemd /run/user/1001/gnupg/S.gpg-agent.ssh
unix 2 [ ACC ] STREAM LISTENING 13664 474/systemd /run/user/1001/gnupg/S.gpg-agent.extra
unix 2 [ ACC ] STREAM LISTENING 13666 474/systemd /run/user/1001/gnupg/S.gpg-agent
unix 2 [ ACC ] STREAM LISTENING 13668 474/systemd /run/user/1001/gnupg/S.dirmngr
unix 2 [ ACC ] STREAM LISTENING 10596 1/init /run/avahi-daemon/socket
unix 2 [ ACC ] STREAM LISTENING 6504 1/init /run/systemd/private
unix 2 [ ACC ] SEQPACKET LISTENING 6513 1/init /run/udev/control
unix 2 [ ACC ] STREAM LISTENING 6517 1/init /run/systemd/journal/stdout
unix 2 [ ACC ] STREAM LISTENING 4056731 1755/systemd /run/user/1000/systemd/private
unix 2 [ ACC ] STREAM LISTENING 4056739 1755/systemd /run/user/1000/gnupg/S.gpg-agent.extra
unix 2 [ ACC ] STREAM LISTENING 4056742 1755/systemd /run/user/1000/gnupg/S.gpg-agent.ssh
unix 2 [ ACC ] STREAM LISTENING 4056744 1755/systemd /run/user/1000/gnupg/S.dirmngr
unix 2 [ ACC ] STREAM LISTENING 4056746 1755/systemd /run/user/1000/gnupg/S.gpg-agent.browser
unix 2 [ ACC ] STREAM LISTENING 4056748 1755/systemd /run/user/1000/gnupg/S.gpg-agent

[enesbcs]

There is nothing else on the RPI0. it's a proper install from 2020-02-13-raspbian-buster-lite.img

I've also tried this Buster edition with an RPI4 and worked well.

this is the result for netstat :

netstat looks fine, nothing using port 8080

Could you try the latest RPIEasy which updated yesterday for more console startup error logs?

[TD-er]

FYI:
Since RPiEasy is such a rapidly growing project (just wow, considering what you managed in such a short time), we thought it would be good to have a separate sub-forum for it.
So I just created it.
Please let me know if I messed up the permissions or something else.

@enesbcs Keep up the good work!

[BertrandP]

I use a RPI 0 W

root@RPi0Jardin:/home/pi# rpieasy/RPIEasy.py
Init hardware...
Load network settings...
Load GPIO settings...
RPi.GPIO not installed!
I2C smbus not installed!
GPIO init failed
Creating new pinout
Load devices from file
Load controllers from file
Load notifiers from file
22:16:27: Event: System#Boot
22:16:27: Event: Clock#Time=Mon,22:16
22:16:27: Event: Network#Connected
22:16:27: !Webserver can not be started, no available port found! [Errno -2] Name or service not known[Errno -2] Name or service not known[Errno -2] Name or service not known[Errno -2] Name or service not known

[enesbcs]

FYI:
Since RPiEasy is such a rapidly growing project (just wow, considering what you managed in such a short time), we thought it would be good to have a separate sub-forum for it.
So I just created it.
Please let me know if I messed up the permissions or something else.

@enesbcs Keep up the good work!

Thank you TD-er subforums will be nice!
Python is for rapid development, and thanks for the Raspberry community there are a lot of premade python examples and libraries for use, so simple sensor integrations is not so complicated. However there were some great challenge on the way, and i am a little scared of linux dependencies as package names and deps tends to change time to time, so maintaining plugin dependencies may require periodic testing against new linux distributions. It is kind of watching and testing new Arduino core versions for ESPEasy.

[enesbcs]

22:16:27: !Webserver can not be started, no available port found! [Errno -2] Name or service not known[Errno -2] Name or service not known[Errno -2] Name or service not known[Errno -2] Name or service not known

It is very interesting "name or service not known" error may refer to DNS resolving error.
when you try "ping www.google.com" on the linux command line, does that work?
I've created a second nettest.py for testing:

Code: Select all

import socket

port = 8080
ownaddr = '0.0.0.0'
try:
   serversocket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) 
   print("socket opened")
except Exception as e:
   print("socket failed "+str(e))
try:
   serversocket.bind((ownaddr, port))
   print("socket bind "+str(ownaddr)+":"+str(port))
except Exception as e:
   print("bind failed for "+str(ownaddr)+":"+str(port)+str(e))
try:
   serversocket.close()
   print("socket closed")
except Exception as e:
   print("close failed "+str(e))

I guess that socket.bind() throws this error, but with 0.0.0.0 address it has to work simply for all interfaces.

[BertrandP]

root@RPi0Jardin:/home/pi# python nettest.py
socket opened
socket bind 0.0.0.0:8080
socket closed
root@RPi0Jardin:/home/pi# ping google.com
PING google.com(par21s17-in-x0e.1e100.net (2a004007:808::200e)) 56 data bytes
64 bytes from par21s17-in-x0e.1e100.net (2a004007:808::200e): icmp_seq=1 ttl=57 time=64.4 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 1 received, 50% packet loss, time 3ms
rtt min/avg/max/mdev = 64.369/64.369/64.369/0.000 ms
root@RPi0Jardin:/home/pi# route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
0.0.0.0 192.168.0.254 0.0.0.0 UG 302 0 0 wlan0
192.168.0.0 0.0.0.0 255.255.255.0 U 302 0 0 wlan0
root@RPi0Jardin:/home/pi#

[enesbcs]

root@RPi0Jardin:/home/pi# python nettest.py
socket opened
socket bind 0.0.0.0:8080
socket closed

It looks fine. I've changed bind in RPIEasy 2.0.161 according to it.

[BertrandP]

It's work ! thank a lot !!!

[2stimpy]

Could someone help me with my rpi setup?
I have everything set up and working for 3 switches to be monitored.
Configured mqtt to receive messages from the pi on switch change.

But now I would like to control a relay which I wired to the gpio15.
I setup gpio15 as an output.
I added Output - Domoticz Output Helper (No feedback) and set up the names for mqtt.

Now if I push the toggle in the web interface I I can see in lens that it sends a message.
If I publish to the set topic, the state also changes in the web interface.

But I cant get the relay to switch on or off, I have the rather standard relay module for the pi.
The relay got power from the 1st pin with the 3rd ground pin. The red light is on.

If I play around with the output High or low for gpio15 than the relay will switch on once but wont go off.
That tells me the relay is working.

I am new to this relay thing, what am I doing wrong.

[TD-er]

Is it GPIO15 on the R'pi or on the ESP?
If it is on the ESP, please note that GPIO15 is a bit special as it has a pull-down resistor instead of the normal pull-up resistors.
If it is on the R'pi, then I really don't know

[enesbcs]

But now I would like to control a relay which I wired to the gpio15.
...
The relay got power from the 1st pin with the 3rd ground pin. The red light is on.

I guess you are trying to use an 5V relay with a 3.3V GPIO, which will not work. If VDD=5V than High level needs to be 0.7 x VDD = 3.5V, check your relay datasheet.
You can check GPIO15 output pin on your RPI with a multimeter, when the relay is disconnected, to see if it works without the relay.
There are methods to use 5V relays with non-5V devices,
http://www.bambusekd.cz/dev/raspberry-control-5V-relay
but i prefer 3V relays generally or MOSFET switches.

[Jabol]

Hello, first I would like to apologize for my English.
Thank you so much for creating the rpieasa!
I wanted to use the software for contact with xiaomi square thermometers. Unfortunately there is a wall on the way between the thermometers and the rpi and the range is terrible.
I wanted to soak rpi zero w and put them in the living room. Thanks to this, I would be able to read parameters and send them to domoticz.
Having rpi zero in the living room, I would also like to control it with an addressable led strip. Can it be done with the use of rpieasa?

[2stimpy]

But now I would like to control a relay which I wired to the gpio15.
...
The relay got power from the 1st pin with the 3rd ground pin. The red light is on.

I guess you are trying to use an 5V relay with a 3.3V GPIO, which will not work. If VDD=5V than High level needs to be 0.7 x VDD = 3.5V, check your relay datasheet.
You can check GPIO15 output pin on your RPI with a multimeter, when the relay is disconnected, to see if it works without the relay.
There are methods to use 5V relays with non-5V devices,
http://www.bambusekd.cz/dev/raspberry-control-5V-relay
but i prefer 3V relays generally or MOSFET switches.

That must be it, I indeed have a 5v relay. I ordered a 3 volt one right away and will try that.
Thanks

[TD-er]

Not sure how much current can be sourced from a GPIO pin on the R'pi, but maybe it is more safe to use a transistor anyway?
Also make sure to place a diode "antiparallel" over the relais coil to protect the electronics driving the coil.
Just the first hit on Google regarding "relais diode": http://www.knutselaar.eu/WP/relais-tips-en-weetjes/

[enesbcs]

Having rpi zero in the living room, I would also like to control it with an addressable led strip. Can it be done with the use of rpieasa?

If the addressable LED strip is a WS2812 than yes the P038 Neopixel plugin is designed to control that. But of course the LED strip will need a separated 5V power supply, the GND has to be common, and a level-shifter is needed in between the RPi GPIO and the LED DigitalInput pin.

[enesbcs]

That must be it, I indeed have a 5v relay. I ordered a 3 volt one right away and will try that.

You can use your 5V relay by adding 4 pieces of passive parts between the RPI and the 5V relay:



However for DC loads i am using these (directly connected to GPIO):


And SSR for AC loads (directly controlled from GPIO):


There are even USB controlled relays on the market! RPIEasy also supports them.

[enesbcs]

Not sure how much current can be sourced from a GPIO pin on the R'pi, but maybe it is more safe to use a transistor anyway?
Also make sure to place a diode "antiparallel" over the relais coil to protect the electronics driving the coil.
Just the first hit on Google regarding "relais diode": http://www.knutselaar.eu/WP/relais-tips-en-weetjes/

You are right a flyback diode is a good idea, if the relay is really a relay, and not a relay module board.
Relay module boards are already contains flyback diodes and some of them also contains opto-isolator.

[Jabol]

Ahh blind i have not seen neopixel.
The only question is how to manage it?
As for the connection, the led strip will be powered by 12v (WS2815) and the signal will be fed through the logic converter.
The only question is how to manage neopixel? And does anyone have an idea how to combine it with domotoicz? (domoticz will be on another raspberry)

[enesbcs]

The only question is how to manage it?

Can be controlled by url commands, as documented in header:
https://github.com/enesbcs/rpieasy/blob ... eoPixel.py

This is the same way as ESPEasy works:
viewtopic.php?t=3919
viewtopic.php?t=3221

[2stimpy]

That must be it, I indeed have a 5v relay. I ordered a 3 volt one right away and will try that.

You can use your 5V relay by adding 4 pieces of passive parts between the RPI and the 5V relay:



However for DC loads i am using these (directly connected to GPIO):


And SSR for AC loads (directly controlled from GPIO):


There are even USB controlled relays on the market! RPIEasy also supports them.

I know I could use the 5v one but the new 3v one was also a cheap relay board.
Had it today and just tested it out. It works great now(only thing is that it is reversed operated) but that's not a real problem)
Now I can start to make the connections to control my gate wired.
I tried different wireless approaches but in the end they all fail once in a while.

[enesbcs]

Now I can start to make the connections to control my gate wired.
I tried different wireless approaches but in the end they all fail once in a while.

I am using ESP8266 with an extra antenna to open the main gate:

https://bitekmindenhol.blog.hu/2020/02/16/wifi-s_kapunyito_diy
A pure 3VDC and passive components used for controlling.

Also using a minimalistic firmware in AP mode to simply open/close remotely. With the external antenna this AP can be seen ~70meter far with clear view of site. It is running since 9 month continously.
https://github.com/enesbcs/ESP_AP_Relay

[2stimpy]

I have chosen to go wired now, and with the pi I will be able to add different options in the future.
I have it all set up but I can't get it to work like it should.

In my home assistant I added the mqtt switches.
I am testing mqtt with mqtt lens.
If I press the toggle button in the web interface, the relay switches like it should, and it reports a state message.
But if I publish to the set topic, the relay switches, but does nor report back a state on the state topic.

I also added sensors like a switch, they report back fine, but off course there I do not use the set topic(because they function as a sensor)

What am I missing here.


I will try to add pictures later, sorry

[enesbcs]

If I press the toggle button in the web interface, the relay switches like it should, and it reports a state message.

Local toggle button is for testing purposes, it is reporting back.

But if I publish to the set topic, the relay switches, but does nor report back a state on the state topic.

If you are using "Output - Domoticz Output Helper (No feedback)" plugin than yes, it is by design. Otherwise the Domoticz will stuck into an endless loop.

[2stimpy]

I am indeed using the domoticz output helper.
Should I use a switch instead?

[2stimpy]

I managed to get it working bij using the set topic as the state topic.
I don't think this is the right way but it works.

What could be the issue when I use it like this?


Now I have to figure out how to automatically switch the relay back of after 1 or 2 seconds.
It needs to act as some kind of push button.

I can make an automation for this in home assistant, but it would be nicer if I could use a rule to do this.
But it needs to report the state.

[enesbcs]

I managed to get it working bij using the set topic as the state topic.
I don't think this is the right way but it works.

Indeed, it is not a very good solution. Maybe i can add a new option to P029 plugin for non-Domoticz systems to report back.

Now I have to figure out how to automatically switch the relay back of after 1 or 2 seconds.
It needs to act as some kind of push button.

I cant help in HA. Domoticz can do this by one simple checkbox: "auto-off by x seconds"

[2stimpy]

I managed to get it working bij using the set topic as the state topic.
I don't think this is the right way but it works.

Indeed, it is not a very good solution. Maybe i can add a new option to P029 plugin for non-Domoticz systems to report back.

That would be nice, the way i have it now is not working after reboot i have to toggle a few times in the webif before the relay responds to the message sent from HA.

To make it act lake a pushbutton/pulse, I can do that in HA but i also managed to get that to work with rules in rpieasy.
Maybe i could also use rules to report to the correct topic?

[enesbcs]

Maybe i could also use rules to report to the correct topic?

Yes rules and publish command is supported in rpieasy.

[2stimpy]

Okay, so i added this.

Code: Select all

On relais#hek do
 if [relais#hek]=1
   gpio,15,1
   publish,RPIEasy/relais/hek/state,1
 else
   gpio,15,0
   publish,RPIEasy/relais/hek/state,0
 endif
endon

It does report to that state topic, but on one switch moment I get over a thousand messages.

[enesbcs]

Code: Select all

On relais#hek do
 if [relais#hek]=1
   gpio,15,1
   publish,RPIEasy/relais/hek/state,1
 else
   gpio,15,0
   publish,RPIEasy/relais/hek/state,0
 endif
endon

It does report to that state topic, but on one switch moment I get over a thousand messages.

Sure, you have just made a recursive endless loop, if relais#hek is controlling gpio15.
As gpio,15,1 command always sync with its parent task, by design. (not in espeasy, but in rpieasy)
Try to use some extra dummy task instead relais#hek. Or simply wait until i upgrade p029 plugin...

[enesbcs]

P029 option added for status reporting for non-Domoticz systems.
https://github.com/enesbcs/rpieasy/issues/176

[2stimpy]

Thanks for updating, great work.
Now if I push the toggle switch, I get a state message.

But if I publish a 1 or 0 to the set topic, the relay switches, state changes in the webif. But I don't get a message at the state topic.

I am sorry, I missed the option box "Response to remote commands for non-Domoticz controllers:".
Now after checking this box, it works like a charm.

Thanks for helping with this and being patient with me.

[2stimpy]

Just one tiny thingy.
If I reboot the system, I first have to use the toggle switch in the webif before the relay starts reacting to the set topic.

[enesbcs]

If I reboot the system, I first have to use the toggle switch in the webif before the relay starts reacting to the set topic.

It is working for me even after reboot. Somehow the state of the value may be out of sync with the real value.. or you are just sending the same state as it can be seen in the Devices page.
Did you try to change "Preserve state at startup" at plugin settings?