You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @dgreif , thanks for your continued support of this API and thank you for your consideration of these two minor requests below.
I've recently had a few request to support wifi status with chimes in ring-mqtt but currently this isn't available via the API. I'd like to see a "getHealth" function for chimes similar to the one for cameras.
Also, as a super minor enhancement, adding support for chime_v2 and chime_pro_v2 for more correct model numbers might be nice as well.
Describe the solution you'd like
I think you should be able to just copy the getHealth() function from cameras as the behavior is basically identical.
Describe alternatives you've considered
I actually implemented my own function to get the health status via a call to restClient directly and it works great, but a getHealth() function would be nice for consistency between cameras and chimes I think. This is the code I'm currently using:
Feature Request
Description
Hi @dgreif , thanks for your continued support of this API and thank you for your consideration of these two minor requests below.
I've recently had a few request to support wifi status with chimes in ring-mqtt but currently this isn't available via the API. I'd like to see a "getHealth" function for chimes similar to the one for cameras.
Also, as a super minor enhancement, adding support for chime_v2 and chime_pro_v2 for more correct model numbers might be nice as well.
Describe the solution you'd like
I think you should be able to just copy the getHealth() function from cameras as the behavior is basically identical.
Describe alternatives you've considered
I actually implemented my own function to get the health status via a call to restClient directly and it works great, but a getHealth() function would be nice for consistency between cameras and chimes I think. This is the code I'm currently using:
I've also manually addressed the model name in my code as well, it's a really minor issue of course.
The text was updated successfully, but these errors were encountered: