01-24-2016, 09:10 PM
Hi gneandr, thx for the geo changes, sorry for not responding sooner. I think just one thread for all the posts on piSchedule is a bit confusing. Quite a few different things intersperse. It should be a seperate forum under addons if you ask me.
Anyway, the problem that was first reported on 7/22/2014 about send command not working hits me as well. I cannot be 100% sure but I think it started happening after I upgraded pilight to the development edition for some reason (i cannot remember why right now). Puzzled me for a long time. I saw the commands being fired in the logs but nothing happening. Then started to issue the piSchedule commands directly from the browser
http://192.168.1.251:5001/send?{%22actio...2:%22on%22}}
resulting in {"message":"failed"}.
And as also described, this http://192.168.1.251:5001/config?media=all works just fine.
The response from curlymo around that date is: fixed in 5.0.
If I read well it has something todo with authorizations. Can you enlighten me what auth settings I need to change?
Thanks a bunch!
Anyway, the problem that was first reported on 7/22/2014 about send command not working hits me as well. I cannot be 100% sure but I think it started happening after I upgraded pilight to the development edition for some reason (i cannot remember why right now). Puzzled me for a long time. I saw the commands being fired in the logs but nothing happening. Then started to issue the piSchedule commands directly from the browser
http://192.168.1.251:5001/send?{%22actio...2:%22on%22}}
resulting in {"message":"failed"}.
And as also described, this http://192.168.1.251:5001/config?media=all works just fine.
The response from curlymo around that date is: fixed in 5.0.
If I read well it has something todo with authorizations. Can you enlighten me what auth settings I need to change?
Thanks a bunch!
