It's a very simply rule to execute every day at fixed time:
45 06 * * Mon-Fri
public void Run()
DriverHelper.ProcessCommad(Domains.MYSENSORS, "N21S0", "ControlUp", "");
DriverHelper.ProcessCommad(Domains.MYSENSORS, "N21S0", "ControlStop", "");
I am checking and some times works, normally after a Raspberry reboot, and radomly sometimes.
Checking log doesn't appear nothing so I suppose commands are not sent.
No i have not debug enabled, i don't know what implies in uSD life.
I thought i might have a RF problem, but log are writen in Raspberry so in this case commands should appear in log even if it can not reach the node and I have no problem using EasyIoT, commands are executed with no lacks. This is no 100% sure but we have not signal radio level indicator.
Commands: Sensor.Down, Sensor.Stop and Sensor.Up are the last incorporated in EsyIot so it can be a bug?. I don't know because when i use it in web ui works well. What the difference of using in Automation? CRON?.
This commands have only one direction: from controller to Node, there is no a feedback, so it must be sent with no matter of success.
So if CRON itself is working fine then maybe it is something with DriverHelper, maybe try using ModuleHelper(like ModuleHelper.SetProperty(Domains.ESP8266, "N3S0", "Sensor.Humidity", "52.2"))? And maybe add EventHelper.SetEvent?
There shouldn't be any difference but it is worth trying. Hard to say without source code.
Html is using Ha.Data.ServiceCall('Control/Module/' + module1.Domain + '/' + module1.Address + '/ControlUp/', null, "POST", null);
which is calling ajax var url = '/Api/EasyIoT/' + 'Control/Module/' + module1.Domain + '/' + module1.Address + '/ControlUp/'
So another way is to call api directly from automation.