ESP32 - BLE Characteristic - Notify help

40.0 EUR

40.0 EUR peopleperhour Technology & Programming Overseas
120 days ago

Description

I am working on an ESP32 project that involves BLE communication with a Unity application. The ESP32 reads data from sensors and notifies the connected BLE client (Unity app) of the sensor values. Most of the characteristics are working fine, but I am facing an issue with one specific characteristic (Ch_data1) that fails to notify the client.Project Details:Microcontroller: ESP32BLE Client: Unity applicationBLE Server: ESP32Sensors: DHT11, DHT22 for temperature and humidityAdditional Data: Voltage readingProgramming Language: C++ for ESP32, C# for UnityProblem Description:
The Ch_data1 characteristic, which contains voltage, firmware version, and other relevant data, is not notifying the connected BLE client (Unity application). Other characteristics are successfully notifying the client, but Ch_data1 fails to do so despite similar setup and code.What I've Tried:
Ensured MTU is set to 512Verified other characteristics notify correctlyChecked data formatting and lengthAdded delays between notificationsTested with BLE scanner apps to rule out Unity app issuesRequirements:
Identify the root cause of why Ch_data1 is not notifying the BLE client.Provide a solution or workaround to enable successful notification for Ch_data1.Ensure the solution is stable and doesn't interfere with other BLE functionalities.Additional Information:
I'm using the NimBLE library for BLE on the ESP32.Unity logs indicate it subscribes to the characteristic, but no data is received.Other characteristics (e.g., temperature, humidity) notify correctly without issues.Deliverables:
Debugged and fixed code for the ESP32.Detailed explanation of the issue and the steps taken to resolve it.(Optional) Any recommendations for optimizing BLE communication in my setup.

关注公众号,不定期副业成功案例分享
Follow WeChat

Success story sharing

Want to stay one step ahead of the latest teleworks?

Subscribe Now

Similar Teleworks

Hello, and thank you for reading. We have an e-commerce affiliate platform. Now this platform is switching from the WP to Next.js + Strapi. To fill in the product information (create/update/delete) products in DB that is used for the e-commerce platform we have a Node.js (Express) application with a simple (2 pages) React app. Application functionality for today: 1. Get the uploaded csv file from front-end with the list of affiliate products 2. Check each product for the next categories: * exist and no changes in price/description/availability from partner * exist and there are changes in price/description/availability, so it has to be updated * not exist in DB - need to be created * product from DB not in the provider list anymore - needs to be hidden on the platform and then deleted 3. Make the logical matching of the fields from the provider according to the settings json that we create for each provider into the fields in DB 4. Send the API call to update the products in the e-commerce 5. For new products, an app is adding them to DB to the temporary table 6. There is a cron job that gathers the new products, sends them to the AI engine API and gets the response with additional data, then marks the products as ready to be sent to the API 7. Send new products already after AI polishing to e-commerce API The app is running locally. What should be done: 1. Clear code and make some refactoring 2. Change the connection from MongoDB to PostgreSQL and organize the repository to be a single DB related module 3. Change the logic from working with csv files to working with API calls and getting data in XML format (data input on step 1) 4. Add 2 providers based on the settings that I will give you (probably already in json files ready to use), but some logical operations need to be coded according to the previous providers logic-matching templates 5. Small changes in AI request logic: change one call to the set of two consistent calls (all prompts are ready) We treat this task as a fixed price. But we want to find a reliable developer who will handle the requests with this application in the future. Please, let me know what do you think.
200.0 USD Technology & Programming peopleperhour Overseas
1 days ago
We are looking for a skilled developer to enhance our API backend by converting existing JavaScript code, currently built with Node.js, Express, and MongoDB, into TypeScript for AWS Lambda. The new implementation should leverage ES6 features and must not include Express. Additionally, the project will require integrating AWS services such as SNS (for SMS) and SES (for email) for authentication, authorization, and verification. Responsibilities: 1. Code Conversion: - Convert the existing JavaScript API code to TypeScript for AWS Lambda, ensuring all functionality is retained while enhancing the code with ES6 features. 2. AWS Integration: - Integrate AWS SNS for sending SMS notifications. - Integrate AWS SES for sending email notifications. 3. Authentication & Authorization: - Implement authentication and authorization processes using AWS services. - Develop verification workflows for email and SMS. 4. MongoDB Integration: - Ensure seamless integration with MongoDB for data storage and retrieval. 5. Error Handling: - Identify and fix any potential errors in the existing codebase. - Implement robust error handling in the new TypeScript code. 6. Serverless Framework: - Develop and deploy the application using Serverless Framework version 4. Requirements: - Strong expertise in TypeScript and Node.js. - Familiarity with AWS services, specifically SNS and SES. - Experience with MongoDB and serverless architectures. - Proficiency in ES6 features and the Serverless Framework. - Ability to write clean, maintainable, and well-documented backend code. Deliverables: - A fully functional TypeScript API codebase deployed on AWS Lambda without Express. - Integrated AWS SNS and SES for SMS and email notifications. - Documentation outlining the setup, usage, and any relevant information for future maintenance. If you are interested in this project, please provide examples of your previous work with TypeScript, AWS, and MongoDB. Include your estimated timeline and budget for completion. Looking forward to your proposals!
157.0 USD Technology & Programming peopleperhour Overseas
19 hour ago
Since the last developer could not manage to do the job this is now added to the list again. PI Work - Fix the default API to ensure it mirrors the discount information from the custom API. - Troubleshoot why the second API does not show discounts for the same products. - Address any API-related issues that affect SEO performance. 2. Internal SEO Cleanup (4-7 hours): - Fix invalid HTML elements in the pages. - Resolve canonical issues, pagination, and meta tag discrepancies. - Correct internal response codes (4xx errors) and missing header tags (H1, etc.). - Update and clean up page titles and duplicate issues. 3. Google SEO Issue Fixes (1 day approx.): - Resolve blocked URLs, canonical tag errors, and noindex tags. - Fix redirects, 403/404 errors, and server-side (5xx) errors. - Address any remaining duplicate canonical issues that Google identified. 4. Post-Cleanup Monitoring (Ongoing): - While the bulk of the work is straightforward and should be completed within 2 days, ongoing monitoring and adjustments will be necessary to help the site rank properly over time. - Track the site in Google Search Console and SEO tools to ensure all issues have been resolved and the site is indexing correctly. DA must grow fast. We have a backlink builder doing his job too. 5. Key Clarifications: - This is a short-term project. Anyone suggesting this will take weeks is overestimating the work. Cleaning up the current list of internal and Google SEO issues should take no more than 2 days for a skilled Magento 2.4 SEO expert. - While long-term ranking improvements will take time, the initial cleanup of these technical issues is simple and should be completed efficiently. 6. Internal Issues List: - Validation: Invalid HTML Elements in – 71 Pages - Canonicals: Non-Indexable Canonical – 1 Page - Pagination: Pagination URL Not in Anchor Tag – 1 Page - Response Codes: Internal Client Error (4xx) – 23 Pages - Pagination: Non-Indexable – 1 Page - Canonicals: Canonicalised – 3 Pages - Canonicals: Outside – 19 Pages - Page Titles: Over 561 Pixels – 9 Pages - Page Titles: Over 60 Characters – 10 Pages - H1: Missing – 13 Pages - Page Titles: Below 200 Pixels – 8 Pages - Canonicals: Missing – 33 Pages - Page Titles: Duplicate – 24 Pages - Images: Over 100 KB – 46 Pages - Page Titles: Below 30 Characters – 15 Pages - H1: Multiple – 1 Page 7. Google Issue List: - Blocked by robots.txt – Failed – 921 Pages (we are removing a lot of idiotic indexing here so it is OK, as usual you must adjust it) - Excluded by ‘noindex’ tag – Failed – 341 Pages - Alternate page with proper canonical tag – Failed – 168 Pages - Duplicate without user-selected canonical – Failed – 38 Pages - Crawled - currently not indexed – Failed – 871 Pages - Duplicate, Google chose different canonical than user – Failed – 2 Pages - Page with redirect – Not Started – 37 Pages - Blocked due to access forbidden (403) – Not Started – 5 Pages - Not found (404) – Started – 2,360 Pages (clarification: I had just added redirects to all; that is why it says started) - Server error (5xx) – Started – 215 Pages - Soft 404 – N/A – 0 Pages - Discovered - currently not indexed – Passed – 3 Pages
28.0 USD Technology & Programming peopleperhour Overseas
1 days ago