Evothings

Belated thanks for the reply. I got by with just having up/down buttons, but I will still try your suggestion to be ready for the next time.

This seems like it should be simple, but I can't figure it out after much trial and error (my HTML/JS skills are sketchy at best). I want to have a number input box in an Evothings app that, upon clicking a SUBMIT button, would write that value to a BLE characteristic on my device. I've got a jQuery...

Glad you got it figured out.

Don

I tried it here and, according to both the Evothings terminal and an LED on the Microduino-BT, the Evothings client app is connecting to the HM10. But the Evothings terminal then says "ERROR: RX/TX services not found!" I also tried to connect to the HM10 with a generic Nordic app I have ( ...

You are right, there is one other thing I forgot that is keeping you from connecting to the HM10. I had changed the device name of my HM10 to "HMSoft531" to indicate I had upgraded the firmware to v5.31 on my device, but I believe the default device name is simply "HMSoft". You c...

Sharing with the group a private response I had prepared for avip... I looked at the HM10 using a pretty powerful BLE tool from Cypress called CySmart . Here is what I found... UUID UUID Description Value 0xFFE1 has 'Write w/o Response' and 'Read' uint8 array of read/write chars 0x2902 Client Charac...

Thank you for the information. As it turns out, I was able to speed up the firmware enough to where this was no longer an issue, but this is all still good to know.

Don

I've got a peripheral I'm working on that is admittedly slow in reporting its characteristics due to a pretty heavy processor load. I am working on optimizing the embedded code to speed it up, but I'm wondering if there is any thing I can do on the Evothings side since there is a time crunch to get ...

I'm not completely sure I understand it myself, but I've generally found that you can pad 16 and 32 bit UUIDs with the same digits to make them into 32 bit or 128 bit UUIDs. For example... The RFduino read characteristic UUID is 2221, but I've found this 128 bit UUID to work 0000 2221 -0000-1000-800...

Thank you. I've now got some reference material to help develop better long-term solutions as well as a quick fix for my immediate problem. I was thinking of having a button to re-run app.startScan() function from app.js, but I wasn't sure that would clean out all remnants of any prior connections. ...