| Crates.io | ring-client |
| lib.rs | ring-client |
| version | 0.1.1 |
| created_at | 2025-05-08 19:48:06.827166+00 |
| updated_at | 2025-06-21 23:42:16.130011+00 |
| description | A Rust client for interfacing with Ring home security devices. |
| homepage | https://ryanmaber.com |
| repository | https://github.com/ryanmab/ring-client |
| max_upload_size | |
| id | 1665768 |
| size | 124,664 |
The Ring Client crate provides a client for interfacing with Ring home security devices.
[dependencies]
ring-client = "0.1.1"
More in-depth examples can be found in documentation comments on the Client methods.
Perhaps one of the most useful features of the crate is the ability to listen and respond to events which occur in a location in real-time.
This is done using the [location::Listener] method.
use ring_client::Client;
use ring_client::authentication::Credentials;
use ring_client::OperatingSystem;
let client = Client::new("Home Automation", "mock-system-id", OperatingSystem::Ios);
// For brevity, a Refresh Token is being used here. However, the client can also
// be authenticated using a username and password.
//
// See `Client::login` for more information.
let refresh_token = Credentials::RefreshToken("".to_string());
client.login(refresh_token)
.await
.expect("Logging in with a valid refresh token should not fail");
let locations = client.get_locations()
.await
.expect("Getting locations should not fail");
let location = locations
.first()
.expect("There should be at least one location");
let mut listener = location.get_listener()
.await
.expect("Creating a listener should not fail");
// Listen for events in the location and react to them using the provided closure.
let result = listener.listen::<_, _, ()>(|event, _, _| async move {
// Connection can be used to send commands to the Ring API.
println!("New event: {:#?}", event);
// The connection argument can be used to send events back to Ring in
// response to the event.
// Return true or false to indicate whether the listener should continue listening, or
// whether the promise should be resolved.
Ok(true)
})
.await;
The [location::Listener] can also be used to send events to the Ring API, such as arming or disarming an alarm
system.
use serde_json::json;
use ring_client::Client;
use ring_client::authentication::Credentials;
use ring_client::location::{Event, Message};
use ring_client::OperatingSystem;
let client = Client::new("Home Automation", "mock-system-id", OperatingSystem::Ios);
// For brevity, a Refresh Token is being used here. However, the client can also
// be authenticated using a username and password.
//
// See `Client::login` for more information.
let refresh_token = Credentials::RefreshToken("".to_string());
client.login(refresh_token)
.await
.expect("Logging in with a valid refresh token should not fail");
let locations = client.get_locations()
.await
.expect("Getting locations should not fail");
let location = locations
.first()
.expect("There should be at least one location");
location.get_listener()
.await
.expect("Creating a listener should not fail")
.send(
Event::new(
Message::DataUpdate(json!({}))
)
)
.await
.expect("Sending an event should not fail");
use ring_client::Client;
use ring_client::authentication::Credentials;
use ring_client::OperatingSystem;
let client = Client::new("Home Automation", "mock-system-id", OperatingSystem::Ios);
// For brevity, a Refresh Token is being used here. However, the client can also
// be authenticated using a username and password.
//
// See `Client::login` for more information.
let refresh_token = Credentials::RefreshToken("".to_string());
client.login(refresh_token)
.await
.expect("Logging in with a valid refresh token should not fail");
let devices = client.get_devices()
.await
.expect("Getting devices not fail");
println!("{:#?}", devices);
There are tons of features which could be added to the crate. If you'd like to contribute, please feel free to open an issue or a pull request.
Examples of features which could be added:
Many of the tests require a valid Ring account before they can be run, which can be provided
via a Refresh Token being set in the .env file.
The .env file can be created by using .env.example as a template:
cp .env.example .env
The tests can be run with:
cargo test