Topics created by ProfRob

I, too, am a "gray hair" (if I had hair). I despise cloud dependent devices. The reasons are many. ISPs, despite what they say, are not reliable. ISPs are so close to be monopolies, that they act like them. Your ISP can, and will, prevent access to the cloud if they have a competing product. The manufacturers of cloud dependent devices, sell your information and statistics on how you use the devices. This is how they make money. When one of these manufacturers goes out of business, the company that buys up the IP continues to sell that information and ceases the little support that one did get. I might be getting a little paranoid here, but I'm pretty sure there is unrelated-to-function software (spyware) incorporated into many products. (In the late 90's, the company for which I worked resisted the temptation to do so, despite heavy pressure from marketing.) I call it "ET phone home" Maybe the software is innocuous enough, but it can be hijacked by bad actors. There is another problem plaguing home automation and that is poorly designed and poorly documented (which leads to pathetically supported) hardware and software. More so the latter. FAQs and forums are afterthoughts of the slothful, but now it's all we have. I agree with ProfRob and I would add "better documentation". As a note, when I pull on my pants, I sit on my bed, start my pants onto my feet, roll back and pull both legs up at once

Update Meanwhile I made progress with my project. Together with some colleagues I want to install a real-time measurement system with more than 30 channels (i.e. 30 Nano BLE 33 measuring accel. and gyro.) and one evaluation unit (another Nano BLE 33 combined with other computers). The 6 values (2*x,y,z) of 16 Bit each shall be transmitted with 10 measurements per second. Instead of spontaneous sending beacons with new measurement values from the 30 devices (to many collisions, real-time simply not possible) I use a master-slave polling, done by the evaluation unit. And I continue using non-connectable/non-scannable BLE-Beacons, for the request messages and for the response messages. Meanwhile, my beacons can be detected by typical BLE scanner APPs on my smartphone (Android 10). I do not know, why that did not work at the beginning. May be I corrected some mistakes incidentally in the last months. I am working also on a channel hopping (in case of disturbances by other devices with BT and WLAN) and using more channels for higher measurement speed. But the implementation of that will start later. 8 hours later Now I found a reason for the behavior of the Scan-APPs: My request beacons (without data, only user address of 6 bytes) are detected, but not the response beacons with data. I do not need the smartphones now (the speed of about 500 beacons per second is to fast for them), so I am happy with my solution.