RPIEasy

[Alan-rpi]

There is a way to send text to your phone via email. See this web page for detail.
https://www.digitaltrends.com/mobile/ho ... l-account/
I've used this before. Seems to work ok.

Thanks for that. I'll add them to my list of potential gateways though I note they are mostly US.

[Alan-rpi]

Hi. I'm now defining a full trial.
I have some output relays and I know my rule can be

Code: Select all

gpio, 13, 1	

but it would be nice to give the output GPIOs names like the inputs.
I was hoping one could then say for example

Code: Select all

if [PanelAlarmSet#state] = 1
           gpio, [DoorLock#state], 1  
or maybe  gpio, [DoorLock], 1  
or maybe  [DoorLock] = 1
endif 

To do this it must be possible to define DoorLock as a Device. Types could be Relay or Switch or LED or an all embracing OnOff Device.

What do you think/suggest.

[enesbcs]

but it would be nice to give the output GPIOs names like the inputs.

There is an existing Output helper plugin, that can be used for a similar manner.
https://github.com/enesbcs/rpieasy/blob ... oOutput.py
If you define one, you can change its state with "taskvalueset,tasknumber,valuenumber,state" and the Value name will hold its actual state. I guess i can enhance "taskvalueset" command to accept [taskname#valuename] for lazy coders who struggle with numbers.

What do you think/suggest.

I think you have never used ESPEasy before.

[Alan-rpi]

Hi. I note that ESP8266 system has System#Wake and System#Boot. Do these work with RPi Easy and is there a System command for closedown/stopping?

On the matter of closedown. If I run RPi Easy as a system task then is RPi Easy happy to be stopped via the Shutdown Now command?

I have written a closedown script where I stop other system tasks such as databases so I could issue stop rpieasy if there was such a command.

Alan

[enesbcs]

Hi. I note that ESP8266 system has System#Wake and System#Boot. Do these work with RPi Easy and is there a System command for closedown/stopping?

On the matter of closedown. If I run RPi Easy as a system task then is RPi Easy happy to be stopped via the Shutdown Now command?

Yes "shutdown now" can be used. But you can also use Tools/Halt command, or "halt" in URL/Rules.
System#Boot called after rules init section in RPIEasy.py and System#Shutdown called at stopping. But this information can be obtained when you look at debug logs.

[Alan-rpi]

for lazy coders who struggle with numbers.

Quite the opposite, I struggle with words! It's about writing code that is descriptive. With numbers one has to either keep commenting what the GPIO x represents or keep looking up what x represents or trying to remember what x represents.

Once my code is written and working it may not be looked at for months, so when I do come back to it then words will get me up to speed quicker.

Yes "shutdown now" can be used. But you can also use Tools/Halt command, or "halt" in URL/Rules.
System#Boot called after rules init section in RPIEasy.py and System#Shutdown called at stopping

Thanks for clarifying the existance of the rules halt command. It is not mentioned on the Commands page https://www.letscontrolit.com/wiki/inde ... O#Commands

There is an existing Output helper plugin, that can be used for a similar manner.

I saw that but couldn't quite figure out how to use it and I was a bit put off using something called Domoticz rather than Relay or Switch. I will look again.

I now see that Domoticz is another HA system. Maybe I should look at that!!! I see it has Zigbee support - useful to control my Hue lights - I don't like the Philips App.

Thanks
Alan

[enesbcs]

Thanks for clarifying the existance of the rules halt command. It is not mentioned on the Commands page https://www.letscontrolit.com/wiki/inde ... O#Commands

Yes, as the ESP8266 has no real shutdown function, but Raspberry Pi has, so i've added it.
https://github.com/enesbcs/rpieasy/wiki ... mmand-list

I saw that but couldn't quite figure out how to use it and I was a bit put off using something called Domoticz rather than Relay or Switch. I will look again.

I am a Domoticz user, and this plugin was evolved from the original ESPEasy Domoticz helper. But P029 Output helper can be used for any other system also. Only restirection is, that it will not trigger outgoing mqtt messages, but only waiting incoming commands.

[enesbcs]

for lazy coders who struggle with numbers.

Quite the opposite, I struggle with words! It's about writing code that is descriptive. With numbers one has to either keep commenting what the GPIO x represents or keep looking up what x represents or trying to remember what x represents.

Once my code is written and working it may not be looked at for months, so when I do come back to it then words will get me up to speed quicker.

All right "taskvalueset" command is enhanced in RPIEasy v2.0.053.
The old form still working:

Code: Select all

taskvalueset,tasknumber,valuenumber,new_value

But also can be used with names:

Code: Select all

taskvalueset,taskname,valuename,new_value

[angelo67]

Hi,
I would like to implement the text of the notices in the "rules"
I would like to make carriage returns as used in espeasy (this is the% CR% command) as written:
https://www.letscontrolit.com/wiki/inde ... ifications
At the bottom of the page.
For example:
notify 1, The% sysday%.% sysmonth%.% sysyear% alle% systime% % CR% The IP Sensor 192.168.1.223 is broken

[laurentm]

Hi,

I try to use Generic - Run OS Command device, to launch a python script. I also tried through the submit command of the tool menu, but the only answer I get is Unknown command.

in the ssh terminal, when using the exact complete path to the script that I use in the "Command" box and it works... (rights are OK, had a +x). I must be doing something wrong, but can't get what. Have you got any idea?

Thanks! Laurent

[enesbcs]

in the ssh terminal, when using the exact complete path to the script that I use in the "Command" box and it works... (rights are OK, had a +x). I must be doing something wrong, but can't get what. Have you got any idea?

You mean you've tried "/usr/bin/python3 complete/path/of/pythonscript.py" ?
This is the complete path with the executable.

[laurentm]

in the ssh terminal, when using the exact complete path to the script that I use in the "Command" box and it works... (rights are OK, had a +x). I must be doing something wrong, but can't get what. Have you got any idea?

You mean you've tried "/usr/bin/python3 complete/path/of/pythonscript.py" ?
This is the complete path with the executable.

Yes... And to be sure, I typed it exactly that way in a terminal window, it worked.

Here is the result of the command output in the tool menu of rpieasy :

False
16:54:00 : Event: Clock#Time=Wed,16:54
16:55:00 : Event: Clock#Time=Wed,16:55
16:56:00 : Event: Clock#Time=Wed,16:56
16:56:29 : CMD: /usr/bin/python3 /home/pi/nukiPyBridge/open.py
16:56:29 : Unknown command: /usr/bin/python3 /home/pi/nukiPyBridge/open.py

Thanks in advance of your help... Laurent

[enesbcs]

in the ssh terminal, when using the exact complete path to the script that I use in the "Command" box and it works... (rights are OK, had a +x). I
...
16:56:29 : CMD: /usr/bin/python3 /home/pi/nukiPyBridge/open.py
16:56:29 : Unknown command: /usr/bin/python3 /home/pi/nukiPyBridge/open.py

There has to be some misunderstanding. Command box in RPIEasy is not for Linux commands, it will never work in that way. It is meant for internal ESPEasy/RPIEasy commands.

Currently the only place that an OS command can be added in RPIEasy is the "Generic - Run OS Command" plugin settings page... and it can be triggered by a virtual switch from Domoticz with this IDX or with taskvalueset command...

rpieasycom.jpg (106.29 KiB) Viewed 105614 times

Otherwise i can add a new command like "eval" to open external python files for internal execution if needed.

[laurentm]

Otherwise i can add a new command like "eval" to open external python files for internal execution if needed.

Thanks for the explanation. No need for that. But if I tried it that way, it's because the Run OS Command doesn't trigger the script either... See my config :

capture.png (141.97 KiB) Viewed 105606 times

When typing TaskValueSet 2,1,1, it triggers the right task (it's task 2):

20:24:00 : Event: Clock#Time=Wed,20:24
20:25:00 : Event: Clock#Time=Wed,20:25
20:26:00 : Event: Clock#Time=Wed,20:26
20:26:49 : CMD: TaskValueSet 2,1,1
20:26:49 : Event: ouvrirPorte#State=1

But the python script isn't launched... I also tried with sudo, but without success. Is there another log I could check to understand what happen "under the hood"?
Thanks! Laurent

[enesbcs]

But the python script isn't launched... I also tried with sudo, but without success. Is there another log I could check to understand what happen "under the hood"?

I've tested it now. When i am trying to execute an invalid command i am seeing this error message on the Linux Console:

Code: Select all

22:03:06: CMD: taskvalueset,rcmd,State,0                                                                                          
/bin/sh: 1: dfsf: not found                                                                                                       
22:03:06: Event: rcmd#State=0   

Beside of that if you change log level (tools->advanced) to "Debug More" than if there are any output from the command execution and there were no error occured, than it will be printed. Try it with simple commands first, such as "ls".

[laurentm]

Try it with simple commands first, such as "ls".

OK, so I changed log level, and then set Command 0 to ls. It works (I don't paste everything, but it's obviously listing the ripeasy directory). I then tried to put a wrong command, as you did, for Command 0, but the output is empty, unlike you... weird. The python script command still doesn't return anything (as if it was wrong, although it works in a Terminal window).

With Command 0 as ls
True
21:31:26 : _C001_DomoHTTP.py
_C002_DomoMQTT.py
_C004_ThingSpeak.py
_C008_GenHTTP.py
_C009_FHEM.py
_C010_GenUDP.py
_C013_ESPEasyP2P.py
_C014_GenMQTT.py
_C015_Blynk.py
_C016_DBStore.py
_C020_LoraDirect.py
_C021_BLEDirect.py
_C022_ESPNow.py
_C023_IFTTT.py
commands.py
...

Here with a wrong command in Command 0 :
True
21:43:00 : Event: Clock#Time=Wed,21:43
21:44:00 : Event: Clock#Time=Wed,21:44
21:44:15 : CMD: TaskValueSet 2,1,0
21:44:15 :
21:44:15 : Event: ouvrirPorte#State=0


The same "nothing" output with the python script :

21:31:26 : Event: ouvrirPorte#State=0
21:31:54 : CMD: TaskValueSet 2,1,1
21:31:54 :
21:31:54 : Event: ouvrirPorte#State=1

Well, I'm stuck... I think I'm gonna reinstall everything to be sure that I didn't make a mistake somewhere. Thanks for your help and above all, thanks for all the work you did to develop rpieasy!
Laurent

[enesbcs]

The same "nothing" output with the python script :

21:31:26 : Event: ouvrirPorte#State=0
21:31:54 : CMD: TaskValueSet 2,1,1
21:31:54 :
21:31:54 : Event: ouvrirPorte#State=1

Well, I'm stuck... I think I'm gonna reinstall everything to be sure that I didn't make a mistake somewhere. Thanks for your help and above all, thanks for all the work you did to develop rpieasy!

Thanks! I will look after deeper at the weekend.
In the meantime perhaps you could try to save command to an .sh script file and add some debug lines, such as create file, write log on startup in the linux script for more testing.

[hvdwolf]

Assuming that your python script has the execute bit set like

Code: Select all

chmod +x /home/pi/nukiPyBridgeOpen.py

.
Please add as first line in your python script

Code: Select all

#!/usr/bin/env python3

and then try with

Code: Select all

/home/pi/nukiPyBridgeOpen.py

, so without the /usr/bin/python3
Or
make the first line in your script

Code: Select all

#!/usr/bin/python3

and then try with

Code: Select all

/home/pi/nukiPyBridgeOpen.py

, so again without the /usr/bin/python3

[hvdwolf]

@enesbcs:
(If you already used/tried this, then sorry for nagging)

You currently use output = os.popen(self.taskdevicepluginconfig[val2])

Isn't it better to use something like:

Code: Select all

output = = subprocess.call(self.taskdevicepluginconfig[val2]))

or if you want to check on the output (returned as a byte string)

Code: Select all

output = subprocess.check_output(self.taskdevicepluginconfig[val2]))

Note also that in case of multiple parameters you need to use someting like a str.split to parse the command, like
subprocess.call(["ls", "-l"])
or
subprocess.call(["/usr/bin/python3", "/home/pi/nukiPyBridgeOpen.py"])

So like

Code: Select all

splitted_val2 = self.taskdevicepluginconfig[val2]).split()

to split on whitespace.
followed by:

Code: Select all

output = = subprocess.call(self.taskdevicepluginconfig[splitted_val2]))

(or combined in one command)

[enesbcs]

You currently use output = os.popen(self.taskdevicepluginconfig[val2])

Isn't it better to use something like:

Code: Select all

output = = subprocess.call(self.taskdevicepluginconfig[val2]))

or if you want to check on the output (returned as a byte string)

Better? I do not think so.
Different? Absolutely.

popen works just fine, and accepting full command line in one string.
In other scripts, where i needs output, i am using other ways, but in this plugin the output is just for Debugging, no use of it.

[enesbcs]

Cool project!! I still must have an Orange PI zero somewhere in the collection of abandoned projects. Ordered because it was only 14 euro. I thought it was the same as Raspberry pi but it was not.

But could this run RPIEasy? I remember that i ran Armbian firmware on it.

After more than 1 year i can say yes: RPIEasy can finally run on OrangePi with Armbian.
Still not a huge fan of these boards, but OrangePi One looks more stable and tends not overheat without load. But software support is a nightmare. Even integrated pullups are missing and hardware pwm is almost impossible to done, and well, software pwm is a joke. (These are crucial things that i am using with my Raspberries) So do not have high expectations but some gpio related thing may work with them...

[svasiliou]

I just start testing and I see a lot of possibilities.

I have 2 questions.
1) I am using 4-5 ESP8266 with P2P network. When I am enabling P2P to my RPIEasy no device is shown at RPIEasy.
What I am doing wrong?

2) A DB controller is available. This is a HUGE improvement to log data from my ESP8266.
Is there any quick info how can I setup it? I mean I have to create db schema, or create tables etc.

Thanks for your great job.

[TD-er]

1) I am using 4-5 ESP8266 with P2P network. When I am enabling P2P to my RPIEasy no device is shown at RPIEasy.
What I am doing wrong?
[...]

If you change the UDP port in ESPEasy, you must reboot the ESP node to make it work.

[svasiliou]

Yes obviously I have done that.
I think that probably is permissions error but I can't figure out.
At RPIEasy all nodes are shown but devices are not populated.
And yes there is no overlapping on task numbers.

So what am I doing wrong?

[enesbcs]

At RPIEasy all nodes are shown but devices are not populated.

I did not tested ESPEasy P2P controller in RPIEasy since it has developed.
If you describe what devices and how added at ESPEasy side, i will try the same.

[enesbcs]

2) A DB controller is available. This is a HUGE improvement to log data from my ESP8266.
Is there any quick info how can I setup it? I mean I have to create db schema, or create tables etc.

First install prerequisites at Dependency page as usual.
Then drop DB controller in, set it up to SQLite and it works.
For MySQL you have to select MySQL, add SQL server infos, and a user, that has right to create table, and the schema will be created automatically.

[svasiliou]

OK database is up and running!
I see that each line records data from task number values and so on. Further testing for that!

About Easy P2P. For simplicity I will setup a ESP8266 & a RPI zero with RPIEasy.
At esp8266, setup P2P controller and enabled. UPD port 8266 as communication port (defined at advanced)
3 sensors connected (DHT22, BH1750, BMP180) and setup with connection to P2P controller.
Sensor are at task 3,4,5 of esp8266

At RPIEasy only P2P controller required at 8266 UDP Port.
At home of each device are shown all nodes that communicate each other (that works)
After a few seconds (or 1 minute) esp8266 must populate tasks 3,4,5 of RPIEasy (that not works).
Final step is to enable at RPI Easy tasks 3,4,5 and voila data are available from 8266 to RPIEasy.

Yes I can overcome all thing with mqtt broker, but .... you know we must test everything , right?

Thanks for your time.

[enesbcs]

At RPIEasy only P2P controller required at 8266 UDP Port.
At home of each device are shown all nodes that communicate each other (that works)
After a few seconds (or 1 minute) esp8266 must populate tasks 3,4,5 of RPIEasy (that not works).
Final step is to enable at RPI Easy tasks 3,4,5 and voila data are available from 8266 to RPIEasy.

OK. Port 8266 setted both sides. Controllers enabled both sides.
I've added a System Info device to Task 2 at an ESPEasy, checked the "Send to controller" checkbox, and at the RPIEasy side the same task is appeared with Disabled state. I checked it to enabled and the datastream from ESPEasy to RPIEasy is started at the interval setted at the ESPEasy side. It just works. Did you started RPIEasy at root rights? UDP cast messaging is not enabled to simple users.
(At RPIEasy side if it is the receiver on the Device page the Controllers checkbox is off i hope?)
Hint: Device creation only triggered once at RPIEasy side: when you press the submit button on the device page at ESPEasy side.

The green cell means that it is a remote device, not a local one.

[svasiliou]

Did you started RPIEasy at root rights? UDP cast messaging is not enabled to simple users.

OK I think here is the problem
I am starting RPIEasy with sudo ./RPIEasy.py. Also I have check RPIEasy at boot.

Where UDP cast messaging is controlled?
Do I have commit any special command?
Should I fix any permissions?

[enesbcs]

Where UDP cast messaging is controlled?
Do I have commit any special command?
Should I fix any permissions?

There are no special settings as root has rights for everything.

Just make sure to press the submit button again on the ESPEasy side, as this is the only time, when RPIEasy creates new devices...

You have to see something similar on the RPIEasy logs, when data arrives from remote ESPEasy P2P station (of course if you enabled Debug verbose at log level):

Code: Select all

18:10:46: Unit alive: 3
18:11:00: Event: Clock#Time=Thu,18:11
18:11:10: Sensorinfo arrived from unit 3
18:11:11: Sensordata update arrived from unit 3

[svasiliou]

OK I found it!
I have re-submit on esp8266 side my sensor, so I cause sensordata resend

Code: Select all

19:54:56 Sensordata update arrived from unit 2
19:54:56 Event: baro_out#Temperature=23.8
19:54:56 Event: baro_out#Pressure=1020.5

I repeat with other sensors and everything OK.
I can't understand if that is possible bug from espeasy (esp8266) side or anything else.
Anyway!

Thank you for your assistant.

[enesbcs]

OK I found it!
I have re-submit on esp8266 side my sensor, so I cause sensordata resend

Code: Select all

19:54:56 Sensordata update arrived from unit 2
19:54:56 Event: baro_out#Temperature=23.8
19:54:56 Event: baro_out#Pressure=1020.5

I repeat with other sensors and everything OK.
I can't understand if that is possible bug from espeasy (esp8266) side or anything else.
Anyway!

Thank you for your assistant.

No problem.
I do not think it is a bug, it just works in that way. Sensorinfo package has been sent once at submit, sensordata transmitting periodically.

[TD-er]

[...]
I do not think it is a bug, it just works in that way. Sensorinfo package has been sent once at submit, sensordata transmitting periodically.

It is indeed designed like that, but that doesn't mean it shouldn't be improved.
I can imagine a button at the controller page to force a re-send could be useful.

But there are other issues with how intuitive it is (or better how it is not...) so the p2p protocol can really use some TLC.
For example, its current implementation is hardly scale-able, as it will send messages to every node it knows in the network.
So for 255 nodes, that would be a lot of messages being sent every minute.

[enesbcs]

So for 255 nodes, that would be a lot of messages being sent every minute.

Indeed. The "send the data to all known peers" one-by-one is not a network friendly solution. (maybe a simple broadcast to node 0 -every device in one package- will require lesser resources)

But without a central station, the other solution i can imagine to create a setting for every "shared" task at the plugin settings: which Node is the destination.
The periodical lifesign packages can be broadcasted packages, as it requires less network bandwidth and local resource, than sending the same package to every node one-by-one.

For example, its current implementation is hardly scale-able, as it will send messages to every node it knows in the network.

It can be scaled by changing UDP ports on P2P devices that needs to be included in a group. Several paralell groups can be created, this is somewhat similar, but more simpler than VLAN on managable switches.

[TD-er]

[...]
It can be scaled by changing UDP ports on P2P devices that needs to be included in a group. Several paralell groups can be created, this is somewhat similar, but more simpler than VLAN on managable switches.

Sure that's one way of handling it and you don't need to contact a system administrator to narrow the 'broadcast domain', so in that sense it is indeed a bit easier to setup compared to VLANs in switches
But the fact we have such a poor implementation is something that really has to be improved.
I don't think IANA does want to assign more UDP ports for our protocol just because it does not scale.

[enesbcs]

I don't think IANA does want to assign more UDP ports for our protocol just because it does not scale.

IANA has no business in my home network. But yes, you are right it can be better. Maybe something like the KNX protocol? As i saw it has group properties to its nodes. But KNX is a server based protocol, not P2P.

[TD-er]

Well I was thinking more like the p2p protocol should be split into separate parts.
- Discovery of other nodes
- subscribing to updates from a node
- sending updates to subscribers

Discovery can be done a lot more p2p-like.
For example if I find a single node, the chances are this node already knows a few others.
So it could exchange several node numbers + addresses so I could ask them specifically for more information.


Sending updates to all known nodes is useless, as long as no node cares.
So a node that would receive updates should subscribe to those updates.
This can be done periodically, so the list of subscribed nodes also does not grow too long and is purged every now and then.
Still have to think about what to do with nodes waking up from deep sleep.


And there are way more optimizations possible. This is just a tip of the iceberg of ideas I have about it.

[martinus]

But there are other issues with how intuitive it is (or better how it is not...) so the p2p protocol can really use some TLC.
For example, its current implementation is hardly scale-able, as it will send messages to every node it knows in the network.
So for 255 nodes, that would be a lot of messages being sent every minute.

Remember that the original UPD messaging (now called P2P) was designed for standalone use for a limited (<10) number of nodes. So you could save money on not having to buy an RPI with a controller. Its origin even goes back to the Nodo project with a wiznet 5100 controller where Arduino Mega's were doing this P2P communication. To make it more efficient, you could use broadcasting (255.255.255.255) but it's less reliable, especially on ESP devices.

I think it's still very useful for 'standalone' operation for a small number of nodes.

When you're Home Automation is no longer standalone, it's expected to run a full featured controller or at least run an MQTT broker. I once started with UDP unicast, then moved on to UDP broadcast but finally switched over to MQTT.

IMHO MQTT offers all the features you would need for large scale, reliable, efficient, qos and retainable messaging infrastructure between any form of node and controller. And it's supported on many platforms and products.

I would suggest to leave P2P as is, and really try to convince our fellow members to start using MQTT.

Having said that, i think the MQTT implementation of ESPEasy could use some TLC to make it more powerful and flexible. It hasn't been improved much since it's first implementation. Wouldn't it be better to spend time on MQTT improvement?

[Ath]

I would suggest to leave P2P as is, and really try to convince our fellow members to start using MQTT.

@martinus I fully support your statements and suggestions, but this point the most. (y)

[TD-er]

Well I do use the p2p myself mainly for discovery reasons, not really for sharing sensor values.
But I can imagine it could be useful for that too, especially in setups where one node is running as AP (e.g. connected to some other means of communications like LoRa) and the other one collecting data on a mobile device.

But for that it is working just fine as it is right now.

I did change quite a lot in the MQTT implementation in the past 2+ years.
As you can see, even Tasmota is using the patched version of PubSubClient I made.
So under the hood it has improved a lot, but that may not seem like many changes on the user end of the controller.

Still it could use a lot of TLC, for example to run the same pubsubclient for MQTT import and a controller (if they are using the same host to connect to)
And some people do need >1 MQTT controller.

[enesbcs]

Remember that the original UPD messaging (now called P2P) was designed for standalone use for a limited (<10) number of nodes. So you could save money on not having to buy an RPI with a controller. Its origin even goes back to the Nodo project with a wiznet 5100 controller where Arduino Mega's were doing this P2P communication. To make it more efficient, you could use broadcasting (255.255.255.255) but it's less reliable, especially on ESP devices.

True. Even the patched STM32/ArduinoEasy version can join to the same P2P network as ESPEasy or RPIEasy does which is cool.

I think it's still very useful for 'standalone' operation for a small number of nodes.

Agree, i am using it on critical nodes (2-3 pieces) that needs to communicate each other in case mqtt server is lost somehow.

When you're Home Automation is no longer standalone, it's expected to run a full featured controller or at least run an MQTT broker. I once started with UDP unicast, then moved on to UDP broadcast but finally switched over to MQTT.

Agree, i feel MQTT is a must-have for fast and responsive two-way communication.

I would suggest to leave P2P as is, and really try to convince our fellow members to start using MQTT.

For compatibility reasons sure, the current P2P version needed, but an other version can be added someday. Even something that is closer to mesh networking, as wifi range is an increasingly common problem.

[martinus]

Well I do use the p2p myself mainly for discovery reasons, not really for sharing sensor values.

You mean the "nodelist"? You could easily refactor the UDP mechanisme to an MQTT version to periodically send hostname, IP and such.

[happytm]

I think for truly standalone local IOT network uMQTT broker at https://github.com/martin-ger/uMQTTBroker should be implemented as an optional controller. With uMQTT broker there is no need for internet at all for local monitor and control.

Thanks.

[martinus]

I think for truly standalone local IOT network uMQTT broker at https://github.com/martin-ger/uMQTTBroker should be implemented as an optional controller. With uMQTT broker there is no need for internet at all for local monitor and control.

Thanks.

With the memory constrains of the ESP8266, this looks like a better candidate for ESP32. Does it run on ESP32?

btw: think were getting really off-topic here, should we create a new MQTT development discusion topic?

[happytm]

With the memory constrains of the ESP8266, this looks like a better candidate for ESP32. Does it run on ESP32?

No it does not run on ESP32 yet. The problems are discussed here https://github.com/martin-ger/uMQTTBroker/issues/13.

Thanks.

[enesbcs]

Just a quick note: from today FTDI USB GPIO&I2C extender is working with RPIEasy. I've never thought before, that i can use an I2C OLED display with my Ubuntu x86 PC directly. Still no idea what can i use in a real-world scenario, but it is a possibility now.
https://ko-fi.com/rpieasy/gallery#gallerytab

Softpwm, tone and rtttl is not a real joy, because the device is slow, but certain gpio input/output and some i2c devices (not all, as some library was directly made for RaspberryPI only, these will never work, neither OrangePi, nor FTDI GPIO) also works.

[pitias]

Hi enesbcs,
I use RPIEasy 2.0.118 on a Pi Zero W 512MB with Raspbian buster. FHEM is defined as controller for six Xiaomi LYWSD03 Hygrometer. Four of them are definitely within a reachable distance to the pi, two don't have a stable connection.
After a fresh boot of the pi RPIEasy finds most of the devices, receives data and transmits them to FHEM. After some time FHEM reports that the sensors are absent, not sending data anymore. This can happen after a couple of minutes or after a couple of days - I couldn't find a scheme yet.
If it's any help, the pi is located in close proximity to the router - max. 20cm away.

I was able to collect the "debug" messages in syslog, the pi is named "piHWRzero":

Code: Select all

May 10 09:56:41 RPIEasy RPIEasy: Pi Zero W 40 pins
May 10 09:56:44 RPIEasy RPIEasy: Event: System#Boot
May 10 09:56:44 RPIEasy RPIEasy: Webserver starting at port 80
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 09:56:44 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 10 09:56:44 RPIEasy RPIEasy: Event: Clock#Time=Sun,09:56
May 10 09:56:44 RPIEasy RPIEasy: Event: Network#Connected
May 10 09:56:49 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 10 09:56:51 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 10 09:56:52 RPIEasy RPIEasy: Event: xiBad#Temperature=24.2
May 10 09:56:52 RPIEasy RPIEasy: Event: xiBad#Humidity=48.0
May 10 09:56:52 RPIEasy RPIEasy: Event: xiBad#Battery=10.0
May 10 09:56:52 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:56:54 RPIEasy RPIEasy: BLE connected to a4:c1:38:4b:8c:5f
May 10 09:56:56 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 10 09:57:01 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.6
May 10 09:57:01 RPIEasy RPIEasy: Event: xi_fe#Humidity=50.0
May 10 09:57:01 RPIEasy RPIEasy: Event: xi_fe#Battery=-1.0
May 10 09:57:01 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:02 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 09:56:47 piHWRzero systemd[1]: systemd-hostnamed.service: Succeeded.
May 10 09:56:47 piHWRzero rsyslogd: action 'action-13-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1901.0 try https://www.rsyslog.com/e/2359 ]
May 10 09:56:47 piHWRzero rsyslogd: rsyslogd[internal_messages]: 431 messages lost due to rate-limiting
May 10 09:57:05 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 10 09:57:08 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 09:57:13 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 09:57:13 RPIEasy RPIEasy: Event: xiDach#Humidity=43.0
May 10 09:57:13 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 09:57:13 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:14 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.5
May 10 09:57:14 RPIEasy RPIEasy: Event: xi_fe#Humidity=50.0
May 10 09:57:14 RPIEasy RPIEasy: Event: xi_fe#Battery=-1.0
May 10 09:57:14 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:15 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 10 09:57:15 RPIEasy RPIEasy: Event: Clock#Time=Sun,09:57
May 10 09:57:15 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 09:57:19 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 09:57:19 RPIEasy RPIEasy: Event: xiDach#Humidity=43.0
May 10 09:57:19 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 09:57:19 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:d8:e8:7c
May 10 09:57:22 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 09:57:23 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 09:57:23 RPIEasy RPIEasy: Event: xiDach#Humidity=43.0
May 10 09:57:23 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 09:57:23 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:28 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.6
May 10 09:57:28 RPIEasy RPIEasy: Event: xi_fe#Humidity=50.0
May 10 09:57:28 RPIEasy RPIEasy: Event: xi_fe#Battery=-1.0
May 10 09:57:28 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:57:28 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 09:57:29 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 10 09:57:36 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 09:57:36 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 10 09:57:41 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 10 09:58:14 RPIEasy RPIEasy: Event: Clock#Time=Sun,09:58
May 10 09:59:15 RPIEasy RPIEasy: Event: Clock#Time=Sun,09:59
May 10 09:59:16 RPIEasy RPIEasy: Event: xiWohnzimmer#Temperature=22.3
May 10 09:59:16 RPIEasy RPIEasy: Event: xiWohnzimmer#Humidity=50.0
May 10 09:59:16 RPIEasy RPIEasy: Event: xiWohnzimmer#Battery=100.0
May 10 09:59:16 RPIEasy RPIEasy: Sending task 2 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:59:20 RPIEasy RPIEasy: Event: xiArbeitszimmer#Temperature=23.9
May 10 09:59:20 RPIEasy RPIEasy: Event: xiArbeitszimmer#Humidity=46.0
May 10 09:59:20 RPIEasy RPIEasy: Event: xiArbeitszimmer#Battery=100.0
May 10 09:59:20 RPIEasy RPIEasy: Sending task 3 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:59:24 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=23.9
May 10 09:59:24 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=47.0
May 10 09:59:24 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 10 09:59:24 RPIEasy RPIEasy: Sending task 5 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 09:59:28 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.6
May 10 09:59:28 RPIEasy RPIEasy: Event: xi_fe#Humidity=50.0
May 10 09:59:28 RPIEasy RPIEasy: Event: xi_fe#Battery=100.0
May 10 09:59:28 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 10:01:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:01
May 10 10:02:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:02
May 10 10:03:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:03
May 10 10:04:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:04
May 10 10:05:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:05
May 10 10:06:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:06
May 10 10:07:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:07
May 10 10:08:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:08
May 10 10:09:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:09
May 10 10:09:07 t610 systemd[1]: Starting Clean php session files...
May 10 10:09:07 t610 systemd[1]: Started Clean php session files.
May 10 10:10:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:10
May 10 10:11:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:11
May 10 10:11:48 piHWRzero systemd[1]: Starting Cleanup of Temporary Directories...
May 10 10:11:48 piHWRzero systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
May 10 10:11:48 piHWRzero systemd[1]: Started Cleanup of Temporary Directories.
May 10 10:12:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:12
May 10 10:13:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:13
May 10 10:14:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:14
May 10 10:15:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:15
May 10 10:16:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:16
May 10 10:17:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:17
May 10 10:18:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:18
May 10 10:19:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:19
May 10 10:20:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:20
May 10 10:21:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:21
May 10 10:22:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:22
May 10 10:23:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:23
May 10 10:24:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:24
May 10 10:25:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:25
May 10 10:26:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:26
May 10 10:27:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:27
May 10 10:28:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:28
May 10 10:29:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:29
May 10 10:30:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:30
May 10 10:31:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:31
May 10 10:32:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:32
May 10 10:33:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:33
May 10 10:34:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:34
May 10 10:35:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:35
May 10 10:36:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:36
May 10 10:37:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:37
May 10 10:38:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,10:38

Another log is

Code: Select all

May 10 19:19:03 RPIEasy RPIEasy: Pi Zero W 40 pins
May 10 19:19:04 RPIEasy RPIEasy: Event: System#Boot
May 10 19:19:04 RPIEasy RPIEasy: Webserver starting at port 80
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:d8:e8:7c
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:18:ba:41
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 10 19:19:04 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:19
May 10 19:19:04 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 10 19:19:04 RPIEasy RPIEasy: Event: Network#Connected
May 10 19:19:11 RPIEasy RPIEasy: Event: xiBad#Temperature=24.0
May 10 19:19:11 RPIEasy RPIEasy: Event: xiBad#Humidity=50.0
May 10 19:19:11 RPIEasy RPIEasy: Event: xiBad#Battery=-1.0
May 10 19:19:11 RPIEasy RPIEasy: Sending task 6 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:19:12 RPIEasy RPIEasy: BLE connection failed a4:c1:38:00:e8:ec
May 10 19:19:13 RPIEasy RPIEasy: BLE connected to a4:c1:38:d8:e8:7c
May 10 19:19:16 RPIEasy RPIEasy: BLE connected to a4:c1:38:18:ba:41
May 10 19:19:18 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:00:e8:ec
May 10 19:19:19 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 10 19:19:25 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 10 19:19:35 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 10 19:19:39 RPIEasy RPIEasy: BLE connected to a4:c1:38:00:e8:ec
May 10 19:19:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:74:a3:28
May 10 19:19:47 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:19:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:74:a3:28
May 10 19:19:56 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:19:56 RPIEasy RPIEasy: BLE connected to a4:c1:38:74:a3:28
May 10 19:19:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Temperature=24.0
May 10 19:19:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Humidity=51.0
May 10 19:19:58 RPIEasy RPIEasy: Event: xiSchlafzimmer#Battery=100.0
May 10 19:19:58 RPIEasy RPIEasy: Sending task 5 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:20:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:20
May 10 19:20:03 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:20:12 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:20:41 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:20:51 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:21:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:21
May 10 19:21:00 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:21:28 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:21:34 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:21:42 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:22:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:22
May 10 19:22:18 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:22:28 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:22:33 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:22:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:22:51 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:23:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:23
May 10 19:23:01 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:23:10 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:23:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:23:27 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:23:35 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:24:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:24
May 10 19:24:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:24:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:24:51 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 19:24:51 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:24:51 RPIEasy RPIEasy: Event: xiDach#Battery=-1.0
May 10 19:24:51 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:24:51 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:24:58 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:25:08 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:25:17 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:25:27 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:25:36 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:25:41 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:25:52 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:25:55 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:26:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:26
May 10 19:26:03 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:26:38 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:26:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:27:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:27
May 10 19:27:13 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:27:21 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:27:27 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:27:37 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:27:46 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:28:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:28
May 10 19:28:53 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:29:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:29
May 10 19:29:00 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:29:13 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:29:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:29:33 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:29:41 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:29:56 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:30:01 piHWRzero rsyslogd: action 'action-13-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1901.0 try https://www.rsyslog.com/e/2359 ]
May 10 19:31:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:31
May 10 19:32:01 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:01 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:01 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:07 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 19:32:07 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:07 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:07 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:13 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 19:32:13 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:13 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:13 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:20 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:20 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:20 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:27 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:27 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:27 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:27 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:31 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:31 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:31 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:31 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:38 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:38 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:38 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:38 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:44 RPIEasy RPIEasy: Event: xiDach#Temperature=25.6
May 10 19:32:44 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:44 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:44 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:49 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:49 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:49 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:50 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:32:57 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:32:57 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:32:57 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:32:57 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:33
May 10 19:33:02 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:02 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:02 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:03 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:08 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:08 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:08 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:08 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:12 piHWRzero dhcpcd[418]: wlan0: carrier lost
May 10 19:33:12 piHWRzero avahi-daemon[253]: Withdrawing address record for 192.168.2.19 on wlan0.
May 10 19:33:12 piHWRzero avahi-daemon[253]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.19.
May 10 19:33:20 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:20 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:20 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:20 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:26 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:26 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:26 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:26 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:32 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:32 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:32 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:38 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:38 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:38 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:38 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:44 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:44 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:44 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:44 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:50 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:50 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:50 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:50 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:33:56 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:33:56 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:33:56 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:33:56 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:34:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:34
May 10 19:34:02 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:34:02 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:34:02 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:34:02 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:34:09 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:34:09 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:34:09 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:34:09 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:34:14 RPIEasy RPIEasy: Event: xiDach#Temperature=25.7
May 10 19:34:14 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:34:14 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:34:14 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:34:20 RPIEasy RPIEasy: Event: xiDach#Humidity=48.0
May 10 19:34:20 RPIEasy RPIEasy: Event: xiDach#Battery=100.0
May 10 19:34:20 RPIEasy RPIEasy: Sending task 4 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:34:26 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:34:32 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:34:45 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:34:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:35:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:35
May 10 19:35:12 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:35:20 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:35:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:35:50 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:36:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:36
May 10 19:36:13 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:36:19 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:36:30 RPIEasy RPIEasy: BLE connection failed a4:c1:38:4b:8c:5f
May 10 19:36:37 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:4b:8c:5f
May 10 19:36:49 RPIEasy RPIEasy: BLE connected to a4:c1:38:4b:8c:5f
May 10 19:37:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:37
May 10 19:38:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:38
May 10 19:39:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:39
May 10 19:39:03 t610 systemd[1]: Starting Clean php session files...
May 10 19:39:04 t610 systemd[1]: Started Clean php session files.
May 10 19:40:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:40
May 10 19:41:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:41
May 10 19:42:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:42
May 10 19:43:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:43
May 10 19:44:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:44
May 10 19:45:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:45
May 10 19:45:01 piHWRzero rsyslogd: action 'action-13-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1901.0 try https://www.rsyslog.com/e/2359 ]
May 10 19:46:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:46
May 10 19:47:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:47
May 10 19:48:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:48
May 10 19:49:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:49
May 10 19:49:55 t610 kernel: [698930.342921] perf: interrupt took too long (3933 > 3927), lowering kernel.perf_event_max_sample_rate to 50750
May 10 19:50:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:50
May 10 19:51:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:51
May 10 19:52:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:52
May 10 19:52:13 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 19:52:14 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 19:52:25 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 19:52:32 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 19:52:38 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 19:52:43 RPIEasy RPIEasy: Event: xi_fe#Temperature=22.6
May 10 19:52:43 RPIEasy RPIEasy: Event: xi_fe#Humidity=56.0
May 10 19:52:43 RPIEasy RPIEasy: Event: xi_fe#Battery=-1.0
May 10 19:52:43 RPIEasy RPIEasy: Sending task 1 data to FHEM at http://192.168.2.43:8383/ESPEasy
May 10 19:52:44 RPIEasy RPIEasy: BLE connection failed a4:c1:38:fd:9b:fe
May 10 19:52:49 RPIEasy RPIEasy: BLE connection initiated to a4:c1:38:fd:9b:fe
May 10 19:52:56 RPIEasy RPIEasy: BLE connected to a4:c1:38:fd:9b:fe
May 10 19:53:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:53
May 10 19:54:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:54
May 10 19:55:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:55
May 10 19:56:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:56
May 10 19:56:24 piHWRzero rngd[282]: stats: bits received from HRNG source: 360064
May 10 19:56:24 piHWRzero rngd[282]: stats: bits sent to kernel pool: 304096
May 10 19:56:24 piHWRzero rngd[282]: stats: entropy added to kernel pool: 304096
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2 successes: 18
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2 failures: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2(2001-10-10) Monobit: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2(2001-10-10) Poker: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2(2001-10-10) Runs: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2(2001-10-10) Long run: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: HRNG source speed: (min=97.655; avg=367.381; max=897.906)Kibits/s
May 10 19:56:24 piHWRzero rngd[282]: stats: FIPS tests speed: (min=392.147; avg=2383.038; max=9071.644)Kibits/s
May 10 19:56:24 piHWRzero rngd[282]: stats: Lowest ready-buffers level: 2
May 10 19:56:24 piHWRzero rngd[282]: stats: Entropy starvations: 0
May 10 19:56:24 piHWRzero rngd[282]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
May 10 19:57:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:57
May 10 19:58:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:58
May 10 19:59:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,19:59
May 10 20:00:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:00
May 10 20:01:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:01
May 10 20:02:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:02
May 10 20:03:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:03
May 10 20:04:01 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:04
May 10 20:05:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:05
May 10 20:06:00 RPIEasy RPIEasy: Event: Clock#Time=Sun,20:06

Sometimes it's able to reestablish the connection but after a while it not possible anymore and the system is stuck.

Do you have any idea how I can make the connection more reliable? Or did I misconfigure anything?
Rebooting the system after detecting the frozen state is only my the last option.

Best regards
Matthias

[enesbcs]

After a fresh boot of the pi RPIEasy finds most of the devices, receives data and transmits them to FHEM. After some time FHEM reports that the sensors are absent, not sending data anymore. This can happen after a couple of minutes or after a couple of days - I couldn't find a scheme yet.

Neither I.
BLE connection is very fragile and in fact there can only be one active BLE connection at a time. I've tested with three devices and occasionally they block each other, with six devices the probability of collision is double.
How do you add intervals? Its wise to choose distant numbers (and never choose the same interval) for each, such as: 91-101-111-121-131-141 seconds at least, or more.
If you are using BLE scanner plugin, disable it.

[enesbcs]

Try to upgrade to neweset RPIEasy. A new option "Connect only if BLE local device free" is available, check for all LYWSD03 devices.

[pitias]

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.