11-23-2015, 10:08 PM
This is what I found after quite too long experimenting and re-installing:
In a fresh install on NOOBS (that's for me) 'pilight-send bla bla' works fine.
After I configure config.json with all sorts of info, including '"standalone": 1' (don't mind the rest of the world) in the settings section, and having it play ball, my commandline 'pilight-send' throws me the ssdp message. Changing '"standalone": 0' or removing it, makes no difference. ('service pilight stop' - alter config.json - 'service pilight start')
But if I replace config.json with the bare OOTB version 'pilight-send' works fine again.
So apparantly I cann't have the command line and the server working at the same time. I do not actually need them both, so I made a shell script to backup config.json and copy config.json-default and vice versa for when I do need to switch.
I hope it saves at least one person a lot of time...
In a fresh install on NOOBS (that's for me) 'pilight-send bla bla' works fine.
After I configure config.json with all sorts of info, including '"standalone": 1' (don't mind the rest of the world) in the settings section, and having it play ball, my commandline 'pilight-send' throws me the ssdp message. Changing '"standalone": 0' or removing it, makes no difference. ('service pilight stop' - alter config.json - 'service pilight start')
But if I replace config.json with the bare OOTB version 'pilight-send' works fine again.
So apparantly I cann't have the command line and the server working at the same time. I do not actually need them both, so I made a shell script to backup config.json and copy config.json-default and vice versa for when I do need to switch.
I hope it saves at least one person a lot of time...