@NeverDie Thx for appreciating the work done. There will also be an open source part in the future. When and how extensive the open source part will be, remains to be seen. The release of certain information (block diagram, ..., in this post) is related to those open source parts. There are some OBD solutions, however most of them (in my experience) give back low frequency data put by the car manufacturer on the OBD-bus (CAN, ...). Therefore transients evolving directly from the battery could only be recorded if the manufacturer sends those data accordingly on the bus. Due to the small bandwidth(also because of other car data that have to be sent, ...), such battery data are sent more often once per second or less. Fast battery events (i.e. cranking events, ...) are therefore imperceptible. Unless the manufacturer processes the fast events and then sends them (once per second or less), which is very unlikely if the manufacturer does not market this feature itself. Third parties devices for high frequency sensing costs several hundreds dollars. In my experience, important battery states (especially the fast ones) are recorded by measuring and processing corresponding data directly on the battery. I agree with you about the limits related to the communication over Bluetooth. But i think Bluetooth 5.0 will improve a lot. However, WiFi will always remain an important option due to the high data throughput. The combination of both (BLE & WiFi), especially with regard to energy consumption, will gain in importance.

Interesting, please note that you need to be a licensed ham radio operator, in order to use the APRS network.

@terxw okey, thanks for reporting back !! Let me know if there is something else. This is a 0.5v so I'm open for improvements.

@scalz said in HALO : ESP32 multi transport GW/Bridge for Mysensors: the webapp was great, but I converted it to native crossplatform app for better versatility&perf, so I can use one app for my devices, like Ethernet for HALO etc, or Serial for my other Janus gw dongle, bluetooth.. To be honest, I've not updated anything yet for a few reasons, like very little spare time for a public release + support for such "big" project. (easier to handle local projects). Sorry, still no eta for the moment.. It is clear that there is not enough time. But this project can become popular. That's what's missing MySensors. ...This void must be filled.

Finally solved a lot of problems and checked a lot of mistakes. But now the first version of this device works almost properly :trollface: I will make a small report in the description asap

Qu3Uk, I did get a chance to test with a Fitbit recently. It technically worked, but not all that well. The thing is, the Fitbit only advertises every 2 seconds so latency is a bit high. But worse, its apps really want to be connected to it often to sync; and whenever it's connected, it stops advertising and the detector then can't pick it up. TommySharp, At this point I don't plan to modify the board much but having it read environmental sensors would be a cool feature! For that, would be nice to make little beacons that read sensors and advertise/broadcast the readings every few seconds. Then they could be very low-power, run on coin-cells for months, and could be placed anywhere instead of needing it to be hooked up to USB power like the main board is. Like these: https://sen.se/peanuts/ I'm curious if it could read them. As for enclosures, I know. I would love to have some nice ones but at this point I'm making too many boards to 3D print enclosures, but too few to afford injection-molding tooling to make a custom case.

@victus Im not familiar with this components you mention, you need to test yourself, cant help you with the technical stuff. It does not seem to be a fully functional ECG but a heart rate monitor. As epierre said above, you need to define if you want to monitor or have a fully functional ECG, its a big difference. With a monitor all you get is pretty much your heartrate and you can detect arytmias. A fully working ECG is normally made with 12 leads and is used to in detail know how the electrical depolarisation from different time and direction/place within the heart muscle works. Holter is a example of a heart rate monitor over time.

@doctor64 said: PIR sensors Not anyone, a sensor that generates a signal when I come close to the car, I rather it not be IR since, AFAIK, they need to be in specific positions to work, unlike NFC or Bluetooth that cover areas around the sensor. Basically I'm trying to create a smart switch that goes on or of based on whether I'm close (in the range of 10-20 feet) to it or not.

Sorry, no. Realised modern phones BT goes into sleep mode which means they don't announce themselves for longer periods. Kind of made it meaningless for the application.