Quickly hacked in is_on function on devices in lua
All checks were successful
Build and deploy automation_rs / Build automation_rs (push) Successful in 5m48s
Build and deploy automation_rs / Build Docker image (push) Successful in 47s
Build and deploy automation_rs / Deploy Docker container (push) Successful in 30s

In order to get feature parity with pre-lua the is_on function is
manually implemented on all wrapped devices in lua
This implementation will need to be improved in the future.
This commit is contained in:
2024-05-07 00:02:02 +02:00
parent c7fc25d239
commit 794b8eef19
2 changed files with 20 additions and 5 deletions

View File

@@ -5,6 +5,7 @@ use std::sync::Arc;
use futures::future::join_all;
use futures::Future;
use google_home::traits::OnOff;
use mlua::FromLua;
use tokio::sync::{RwLock, RwLockReadGuard};
use tokio_cron_scheduler::{Job, JobScheduler};
@@ -42,6 +43,17 @@ impl mlua::UserData for WrappedDevice {
methods.add_async_method("get_id", |_lua, this, _: ()| async {
Ok(crate::devices::Device::get_id(this.0.read().await.as_ref()))
});
methods.add_async_method("set_on", |_lua, this, on: bool| async move {
let mut device = this.0.write().await;
let device = device.as_mut();
if let Some(device) = device.cast_mut() as Option<&mut dyn OnOff> {
device.set_on(on).await.unwrap()
};
Ok(())
});
}
}