Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending matter sensor data to rainmaker (MEGH-6063) #338

Closed
3 tasks done
aadhimellow opened this issue Oct 17, 2024 · 6 comments
Closed
3 tasks done

Sending matter sensor data to rainmaker (MEGH-6063) #338

aadhimellow opened this issue Oct 17, 2024 · 6 comments

Comments

@aadhimellow
Copy link

Answers checklist.

  • I have read the Rainmaker documentation and the issue is not addressed there.
  • I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
  • I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

General issue report

I have flashed the matter controller + rainmaker example with otbr feature to an espressif thread border router and was able to successfully commission a matter door sensor and mattet plug to rainmaker. How can I send the states of those devices to the rainmaker dashboard or aws iot core. Currently one device is not showing any parameters which is the door lock sensor and the matter plug can be turned on and off with rainmaker but those two devices are not shown in rainmaker dashboard.
a846cc26-76e7-4e21-90b3-cc1270961f00
343f9638-caae-4bff-b66a-aa249c44319b

@github-actions github-actions bot changed the title Sending matter sensor data to rainmaker Sending matter sensor data to rainmaker (MEGH-6063) Oct 17, 2024
@aadhimellow
Copy link
Author

@sayondeep Could you please look into this ?

@shahpiyushv
Copy link
Collaborator

The ESP RainMaker dashboard is an admin side device management dashboard meant for devices directly connected to the RainMaker backend, which in this case, is the controller. The devices connected to the controller are pure matter devices, not relevant to admin users. They are accessible only to the end user via the phone app. Moreover, some device types are not yet supported, either by the controller, or the phone app. So, even if they may be controllable by API, they may not show correctly in the app.

@aadhimellow
Copy link
Author

Is there any possible way to send the data of the sensor to aws iot core via the matter controller

@sayondeep
Copy link
Contributor

You can check the supported device type by the controller here

Currently door lock sensor is not supported by the controller and phone app.

Assuming that door lock sensor is supported in the controller. As a proof of concept you can your logic for sending on-off data of light to aws iot core by adding your logic here

.

We report the updated state of light (A supported device type by controller) .
To check and verify the state. You can run the following commands.

$ cd $RMAKER_PATH/
$ esp-rainmaker-cli login --email <rainmaker-account-email>
$ esp-rainmaker-cli  getparams <rainmaker-node-id-of-controller>

On-Off cluster is 0x06.

@aadhimellow
Copy link
Author

Thank you so much. Could you please tell me how to change the startup logo from espressif to a custom logo. I have seen a file in the location matter controller with touchscreen in the file esp_logo.c. But I can see the image is converted into a hex format. How can I convert my custom logo like that. Also what should be the resolution and size of the logo?

@aadhimellow
Copy link
Author

After commissioning the matter controller to rainmaker. I can see the current time in the s3box. How can I fetch that time and print it in the log.
After provisioning i have seen the date time details in the monitor under the esp log tag called esp_rmaker_time but couldnt find the function that does it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants