How to schedule simple commands?

[akauppi]

I am slightly embarrassed to be asking this.. It's perfectly fine that the project doesn't aim to schedule device actions, but.. here goes.

I've got ZWave-JS-UI running and my devices are recognized. I'd like to schedule simple "power on/off" actions for some smart plugs. Is there any way I could do this without resorting to whole Home Assistant? Having databases and what not it looks way heavier than what I would need for: keep lights on between 10am .. 10pm.

[robertsLando]

Yes, you can: https://zwave-js.github.io/zwave-js-ui/#/usage/setup?id=scheduled-jobs

Basically you can schedule custom driver functions to run,

[akauppi]

Thanks.

That means technically it could be done. But the developer experience wasn't great (I don't see a cursor, and get no logs out though I tried). It would be coding in dark, and without API docs, I guess. Cannot switch the bulb on.

What I do see is a "targetId" (2-37-0, see below). If you have a snippet that switches such on/off, I can give it a try.

On my own, I'll go and make some Rust automation to do this.

[robertsLando]

Here is your driver function to write true on that specific switch:

const zwaveClient = this.zwaveClient

const vId = {
    nodeId: 2,
    commandClass: 37,
    endpoint: 0,
    property: 'targetValue',
}

zwaveClient.writeValue(vId, true)

[robertsLando]

Yeah my question was because if you enable log to file you will not be able to see logs on debug window, also remember there are 2 types of logs, zwave-js logs (the driver that communicate with the stick) and zwave-js-ui logs (the zui application), in order to see both logs there you need to disable log to files for boths, anyway mind to enable them when finished as it is helpful to have logs files when bugs happen, them must be uploaded along with the issues on gh :)

[akauppi]

Ok - solved it.

The MQTT Gateway needs to be enabled - otherwise scheduled jobs don't run.

I now get the logs. :) And I can schedule switches on/off successfully. Mystery fog faded.

[robertsLando]

@akauppi Wait, this reminds me an old bug I solved, what version are you using?

[robertsLando]

Found it: #3409

Has been released more then 2 months ago, I think you should update your instance :)

[akauppi]

True. I was using :latest Docker image, but it was 3 months old.

From my side, this can now be closed (as an issue), but since it's a discussion I don't know what happens next.

Thanks for the help - all good now!