March 1st update bug. **solved**

All about the standard Meteobridge devices based on mobile routers from TP-Link, D-Link, ASUS

Moderator: Mattk

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

March 1st update bug. **solved**

Post by _John C »

Just updated today :(
Attachments
Screenshot_20210301-153308_Samsung Internet.jpg
Screenshot_20210301-153308_Samsung Internet.jpg (52.04 KiB) Viewed 619 times
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

Platform:TL-WR902ACV3
Meteobridge 5.1 (Mar 1 2021, build 3785), FW 1.3
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

What firmware version is your GW1000 running? Did you upgrade to version 1.6.5 that was recently removed by Ecowitt for bugs?...or are you still on version 1.6.3? If you are stuck with version 1.6.5, then you'll have to wait until the next version comes out. I'm not saying that your issue is necessarily related to the GW1000 firmware but it is a possibility.

The Meteobridge March 1st update add support for the new WH35 sensor (Leaf wetness). This sensor is not yet released for sale. It is possible that the changes required for the WH35 caused some inadvertent bug in the overall GW1000 driver. But maybe only for those on the latest GW1000 firmware 1.6.5 (that is now recalled).

I'm running my GW1000 still with firmware 1.6.3 and I just upgraded my Meteobridge TP-Link to March 1st update and I'm getting live data. I have not updated my Meteobridge RPI as I don't like to upgrade my production system until it has been well tested.

Ecowitt will soon come out with an updated firmware to fix the issues with version 1.6.5. They are aware of the problem.

Also did you check the obvious and make sure that your GW1000 didn't get a new IP address? I recommend setting a DHCP IP address lease reservation for the GW1000...and for the Meteobridge too so that you can always find it.
Meteobridge RPI | GW1000

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

GW1000 is running firmware 1.6.5. After the 1.6.5 update; Meteobridge was working fine. It was only today after updating Meteobridge the problem appeared. :?: :?: :(

I have both devices set with static ip addresses and both are correct.
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

Code: Select all

wnetd  (01.03.2021 19:28:40): process started.
system (01.03.2021 19:28:40): start of logging process initiated.
wnetd  (01.03.2021 19:28:41): send data thread started (pid:1889 tid:1891)
logger (01.03.2021 19:28:41): historical data loaded (84 records).
logger (01.03.2021 19:28:41): data logger (version 5.1e, build 3785) started.
logger (01.03.2021 19:28:42): connect station 0 (GW1000 via TCP/IP).
logger (01.03.2021 19:28:45): sensors are now providing data.
logger (01.03.2021 19:28:45): services started.
logger (01.03.2021 19:28:52): child process received termination signal (11) in functions: termination_handler < forward < chars_avail < process_data < handle_data < set_basic_timeout < send_wnet_nosensor < test_inetupload < send_wnet_nosensor < forward < chars_avail < process_data < handle_data < set_basic_timeout < send_wnet_nosensor < test_inetupload < send_wnet_nosensor < forward < c...
logger (01.03.2021 19:28:52): disconnect station 0 (GW1000): exit
logger (01.03.2021 19:28:53): data logger stopped.
logger (01.03.2021 19:28:53): parent process to be terminated.
logger (01.03.2021 19:29:11): historical data loaded (84 records).
logger (01.03.2021 19:29:11): data logger (version 5.1e, build 3785) started.
logger (01.03.2021 19:29:12): connect station 0 (GW1000 via TCP/IP).
logger (01.03.2021 19:29:15): sensors are now providing data.
logger (01.03.2021 19:29:15): services started.
logger (01.03.2021 19:29:22): child process received termination signal (11) in functions: termination_handler < forward < chars_avail < process_data < handle_data < set_basic_timeout < send_wnet_nosensor < test_inetupload < send_wnet_nosensor < forward < chars_avail < process_data < handle_data < set_basic_timeout < send_wnet_nosensor < test_inetupload < send_wnet_nosensor < forward < c...
logger (01.03.2021 19:29:22): disconnect station 0 (GW1000): exit
logger (01.03.2021 19:29:22): data logger stopped.
logger (01.03.2021 19:29:22): parent process to be terminated.
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

You can't have static address set on GW1000 as it only supports DHCP. You can have a DHCP reservation though...not the same thing. Maybe that is what you mean...but semantics matter. Let's use the proper terms. Static IP is what you set on a device. A DHCP reservation is what you set on the DHCP server (router or other network device acting as DHCP server).

Regarding the Meteobridge....I think setting a DHCP reservation is better than static IP address configuration. If you ever have to reconfigure your network you'll have a much easier time if everything is using DHCP leases (with and without reservations).

Sorry about your trouble with not getting live data from the GW1000. At this point I think you can wait for the next GW1000 firmware or you can see if Boris can look at the latest update to see if any changes regarding adding support for the WH35 is causing trouble with firmware 1.6.5. See it is firmware 1.6.5 that is the first to support the WH35. Being that there is a known issue with the GW1000 firmware 1.6.5 (hence why it was pulled off distribution) I would be hesitant for Meteobridge to make any changes until the next firmware comes out. I'm sure it won't be but another day until the next GW1000 firmware comes out. And unfortunately there is no way to revert back to a prior firmware on the GW1000. Next time don't be so quick to jump on a new firmware release.

As a test or in the mean time you could try to run Meteobridge 5.0 version and see if that gets you live data from the GW1000.
Meteobridge RPI | GW1000

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

Thank you galfert so much. 😁
Running Meteobridge 5.0 ; it's working again.👍😁
Attachments
Screenshot_20210301-194555_Samsung Internet.jpg
Screenshot_20210301-194555_Samsung Internet.jpg (201.47 KiB) Viewed 586 times
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

GW1000 new firmware V1.6.6 has been released. I upgraded and Meteobridge 5.1 (1st March update) will still not work. Reverted Meteobridge to v 5.0 and it's working again.

Looks like Meteobridge 5.1 (1st March update) does not work with GW1000 V1.6.5 or V1.6.6 😩
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

Seems strange that there are not more people reporting this issue. I also asked over at the wxforum.net and nobody has reported issues. It could be that there aren't very many that have upgraded their both the GW1000 firmware and the Meteobridge.
Meteobridge RPI | GW1000

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

alexdelprete wrote:
Wed Mar 03, 2021 3:02 pm
I checked with Ecowitt, and they said that the recent fw updates are not related to the APIs or the UDP broadcasting
Seems as though Ecowitt misunderstood your question. Because starting with GW1000 firmware 1.6.5 some big changes were made. With this new firmware, API changes were made to support the new WH35 leaf moisture sensors. There was also considerable change in the battery status reporting method. Even though the Meteobridge does not make use of battery status, the data for all this is still there in the payload of the API query for sensor data. The length of the API data payload changed starting with firmware 1.6.5....you now get less bits because there was an older battery status that was removed because it was redundant and less detailed than the newer method for battery status that was introduced some months prior.

Boris had refrained from reporting GW1000 sensor battery status before with the Meteobridge, because it was complicated and the documentation is difficult to understand (much of it written in Chinese). But it isn't as simple as just using Google Translate because what is documented is spars and much of it requires discovery work.

The new battery status reporting method is much better and simpler. Now each sensor reports on its own battery right after the sensor data is passed on each broadcast. Previously there was a bunch of zeros as place holders for all sensors' battery status even if you didn't have that sensor. It would have been complicated to get the status for all sensors even if you didn't have the sensor but then only report on those that were present. That was nuts before.

So this got to be a bit off topic on battery talk but it was a big change in the API.
Meteobridge RPI | GW1000

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

alexdelprete wrote:
Wed Mar 03, 2021 7:15 pm
Lucy understood my question, and adding new sensors does not imply a major API change, it's just adding a new device to the API. Adding a device doesn't mean that the rest is changed,
What I'm saying is that the adding of a new sensor type is not the major change in the API. Rather the major change is in the battery status reporting method that was removed. Even though the Meteobridge does not make use of battery status it still has to contend with this data as it parses the data payload for sensor data. None of us are privy to the method and logic used by the Meteobridge to parse sensor data.

There are other changes in this newest firmware that I have not mentioned. There was also change in the way barometric data is sent which is still a bug in 1.6.6 for WH2650 devices, it is missing. There is also code in there for a future Ambient device not yet released.

For Lucy to say that the API didn't change is just not true, therefore she did not understand you. She is a wonderful helpful person but sometimes people make mistakes or they simply misunderstand or they may not grasp the context of the situation. Because I have the official API documentation (half written in Chinese) and I can tell after having studied it that there are considerable changes. The API without a doubt has changed. I'm the person that is the liaison for all the software developers in regards to the GW1000. The API has not changed in reference to how older sensor data is presented, but because the data payload is sent in one continuous stream it is up to each software to determine how it deals with the entire data payload. But the amount of bits sent has changed (it has diminished) because there was some code clean-up.

In the past previous API changes have affected different applications differently. Some break, some don't. For example I remember a firmware update that affected Weather-Display but didn't affect Meteobridge. This is because it is up to each application to decide how they parse the ingested data from the API. The API is a simple query command sent to the GW1000 that simply says to the GW1000, "hey send me all the data", and the GW1000 responds with an entire payload of hexadecimal data that needs to be parsed and converted to decimal. Some changes in the API are ignored by the parsing and in other software it may see something unexpected and hence nothing works.

I don't know why firmware 1.6.6 works with Meteobridge 5.0 and not with the latest 5.1. It could be that because there have been a few versions of 5.1. It is possible that a prior change in the 5.1 development is the key difference. Meteobridge 5.0 may be ignoring some extra stuff that firmware 1.6.6 is sending. If you look at the Meteobridge changelog you'll see that there were changes in earlier 5.1 for temperature sensors that only send temperature and not humidity (like the WH31P), and there was also a change for a bug in recording of soil sensor data.
Like I said, the only guy who can tell us what's happening is Boris, I'm just guessing that probably a bug was introduced in latest MB version, let's wait and see. MB is a great piece of software, bugs can happen. :)
I agree there. I think you should message info < at ] smartbedded and ask Boris to remote into your Meteobridge to see what he can do now that firmware 1.6.6 is out.
Meteobridge RPI | GW1000

User avatar
galfert
Platinum Boarder
Platinum Boarder
Posts: 326
Joined: Sun Jun 24, 2018 10:31 pm
Location: Orlando, FL

Re: March 1st update bug

Post by galfert »

I have no interest in going further with this conversation. I can't discuss this further at your level (whether higher or lower than me is irrelevant). Our understanding of APIs is not something we are going to agree on. I'm sorry but some conversations are just off putting.

Further testing by other individuals shows that there is no problem with GW1000 firmware 1.6.6 and MB 5.1 March 1st release. Your issue is likely caused by something else....or you have a particular situation that is unique that Boris will need to look into.

https://www.wxforum.net/index.php?topic=41612.0
Meteobridge RPI | GW1000

_John C
Junior Boarder
Junior Boarder
Posts: 38
Joined: Thu Jun 11, 2020 5:31 pm

Re: March 1st update bug

Post by _John C »

galfert wrote:
Thu Mar 04, 2021 2:44 am
Further testing by other individuals shows that there is no problem with GW1000 firmware 1.6.6 and MB 5.1 March 1st release.
Not working for me :?
Attachments
Screenshot_20210301-153308_Samsung Internet.jpg
Screenshot_20210301-153308_Samsung Internet.jpg (52.04 KiB) Viewed 472 times
Meteobridge TL-WR902AC V3, Ecowitt GW1000CA, HP2551CA, WH65 Outdoor 7in1 2 arm array, WH32B Indoor Temp/Hum/Baro, WH45 Co2/PM2.5/PM10, WH41 PM2.5, WH57 Lightning Detector, WH31 Temp/Hum x8, WH51 Soil Moisture x8, WH55 Water Leak x4, Da9L PWT x2

meteolive57290
Senior Boarder
Senior Boarder
Posts: 42
Joined: Sat Dec 10, 2016 11:26 am

Re: March 1st update bug

Post by meteolive57290 »

hello
for my part no problem with my GW1000 and the last fw 5.1 release on the other hand I find myself with an unknown "device" (Air)
Regards
Attachments
Capture_mb-horz.jpg
Capture_mb-horz.jpg (99.65 KiB) Viewed 468 times

marioferrari22
Fresh Boarder
Fresh Boarder
Posts: 8
Joined: Tue Nov 24, 2020 10:03 pm

Re: March 1st update bug

Post by marioferrari22 »

I have the same problem, but since the March 1st release, it doesn't work anymore, I updated the GW1000 to version 1.6.6, but nothing changes.
I can only go back to version 5.0 and wait for more news.
I tried again today with the version (Mar 4 2021, build 3790),
Same problem
Bye
----------
Lod


wnetd (04.03.2021 10:52:28): process started.
system (04.03.2021 10:52:28): start of logging process initiated.
wnetd (04.03.2021 10:52:28): send data thread started (pid:1942 tid:1943)
logger (04.03.2021 10:52:29): historical data loaded (60 records).
logger (04.03.2021 10:52:29): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:52:30): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:52:30): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:52:30): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:52:33): sensors are now providing data.
logger (04.03.2021 10:52:33): services started.
logger (04.03.2021 10:52:40): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:52:40): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:52:41): data logger stopped.
logger (04.03.2021 10:52:41): parent process to be terminated.
logger (04.03.2021 10:52:59): historical data loaded (60 records).
logger (04.03.2021 10:52:59): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:52:59): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:52:59): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:52:59): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:53:03): sensors are now providing data.
logger (04.03.2021 10:53:03): services started.
logger (04.03.2021 10:53:10): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:53:10): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:53:11): data logger stopped.
logger (04.03.2021 10:53:11): parent process to be terminated.
logger (04.03.2021 10:53:29): historical data loaded (60 records).
logger (04.03.2021 10:53:29): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:53:29): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:53:29): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:53:29): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:53:33): sensors are now providing data.
logger (04.03.2021 10:53:33): services started.
logger (04.03.2021 10:53:40): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:53:40): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:53:41): data logger stopped.
logger (04.03.2021 10:53:41): parent process to be terminated.
logger (04.03.2021 10:53:59): historical data loaded (60 records).
logger (04.03.2021 10:53:59): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:53:59): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:53:59): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:53:59): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:54:03): sensors are now providing data.
logger (04.03.2021 10:54:03): services started.
logger (04.03.2021 10:54:10): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:54:10): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:54:11): data logger stopped.
logger (04.03.2021 10:54:11): parent process to be terminated.
logger (04.03.2021 10:54:29): historical data loaded (60 records).
logger (04.03.2021 10:54:29): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:54:29): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:54:29): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:54:29): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:54:33): sensors are now providing data.
logger (04.03.2021 10:54:33): services started.
logger (04.03.2021 10:54:40): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:54:40): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:54:41): data logger stopped.
logger (04.03.2021 10:54:41): parent process to be terminated.
logger (04.03.2021 10:54:59): historical data loaded (60 records).
logger (04.03.2021 10:54:59): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:54:59): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:54:59): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:54:59): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:55:03): sensors are now providing data.
logger (04.03.2021 10:55:03): services started.
logger (04.03.2021 10:55:10): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:55:10): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:55:11): data logger stopped.
logger (04.03.2021 10:55:11): parent process to be terminated.
logger (04.03.2021 10:55:29): historical data loaded (60 records).
logger (04.03.2021 10:55:29): data logger (version 5.1e, build 3790) started.
logger (04.03.2021 10:55:29): station 0 (Vantage), can't open device /dev/ttyMH: Invalid argument
logger (04.03.2021 10:55:29): station 0 (Vantage), connect to station failed.
logger (04.03.2021 10:55:29): connect station 1 (GW1000 via TCP/IP).
logger (04.03.2021 10:55:33): sensors are now providing data.
logger (04.03.2021 10:55:33): services started.
logger (04.03.2021 10:55:40): child process received termination signal (11) in functions: termination_handler < send_wnet_nosensor < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < get_set < get_set_text < send_a...
logger (04.03.2021 10:55:40): disconnect station 1 (GW1000): exit
logger (04.03.2021 10:55:41): data logger stopped.
logger (04.03.2021 10:55:41): parent process to be terminated.

Post Reply