[gneandr]

The intention for this project is to define a "switch" plan for the different locations/devices. I need to have lamps/devices switched based on such a plan which should randomly vary and can also follow sunrise/sunset time.

The project is in an early state, so any feedback is very welcomed. Also please note the implementation is using python .. and it's my very first python project
(I'm surprise about the broad utility base which should make the project an easy go .. most hopefully).

Head over to
https://github.com/neandr/piScheduler
and let me know ..

Guenter

[curlymo]

Please notice that the next pilight release will contain event rules which already making good progress.

Also, pimatic has already really good support for event rules but you need additional software on top of pilight.

[gneandr]

Please notice that the next pilight release will contain event rules which already making good progress.

Where to find details?

[curlymo]

In the future of pilight and pimatic topic.

[gneandr]

In the future of pilight and pimatic topic.

Sorry to call back on this, but also scanning both pilight and pimatic .. I can't see/find any details you mentioned. Please post --at least -- a link to "the future of pilight".
I would like to cross check with my implementation so far.

Thanks

(Will add an installation intruction for my 'piSchedule' later today)

[curlymo]

http://forum.pilight.org/Forum-Open

http://pimatic.org/

[gneandr]

Updated piScheduler on GitHub

README.md with example and installation details

[curlymo]

Good work!

[gneandr]

Updated on GitHub for schedule plan with text/'INI' format instead of JSON.
This offers easier editing. Also using JSON with direct switching the order of the switch events may not be parsed as the occurrence in the JSON file (off maybe issued before on).

https://github.com/neandr/piScheduler

[gneandr]

After upgrading to pilight 5.0 Have problems with sending control commands like this:

Code:

http://192.168.178.1:5001/send?{%22message%22:%22send%22,%22code%22:{%22location%22:%22Aussen%22,%22device%22:%22Haustuer%22,%22state%22:%22on%22}}

The settings.json changed to:

Code:

{
    "log-level": 5,
    "pid-file": "/var/run/pilight.pid",
    "config-file": "/home/pi/pilight_config/config.json",
    "hardware-file": "/etc/pilight/hardware.json",
    "log-file": "/var/log/pilight.log",
    "send-repeats": 10,
    "receive-repeats": 1,
    "webserver-enable": 1,
    "webserver-root": "/usr/local/share/pilight/",
    "webserver-port": 5001,
    "webserver-authentication": [ "admin", "admin" ],
    "webserver-cache": 1,
    "webserver-user": "root",
    "whitelist": "",
    "update-check": 1,
    "firmware-update": 0
}

Working with "pilight webgui" isn't a problem, so the config.json/hardware.json are OK, all GUI elements do their job, the switches work as expected.

Sending a cmd as shown above opens an 'Authentication Required" dialog asking for uname/pw. Also entering the right values, it repeats asking. /var/log/pilight.log doesn't give any info. Firefoy console also no output.

How is the trick? to work as it was with version 3.0?

Guenter