Rules Scheduler Component parameter is empty
Some tips to help you find out what's happening / going wrong (based on revision 2 of your question):


Try to execute your Rules Component "manually" (just to test), to unit-test if it works as desired. To do so, use the "execute" link to the right of the Rules Component (in the Rules UI).
It could be a permission issue, i.e. think about which "user" (authority) the scheduled component executes with.


Some more tips to help you find out what's happening / going wrong (based on revision 3 of your question), and your extra comment which includes "... shows this error: "Recoverable fatal error: Object of class stdClass could not be converted to string in DatabaseStatementBase->execute() (line 2227 of database.in‌​c)." The log has a "page not found" warning from /admin/config/workflow/rules/components/manage/autocomplete/‌​node_to_archive/form‌​-xxx.../ ...":


Try to temporary remove that very last rules action (to execute that PHP code), and see what happens.
If the error still doesn't go away, it seems the time is right to start Rules debugging, as explained in my answer to "Where is the Rules Evaluation Log?".


Last but not least ...

About this part of your question:


  The problem is that the scheduled component gets an empty parameter and so can execute the actions. Drupal log shows an "The variable or parameter node is empty." warning.


Please have a look at what's described in my answer to "Why can my view not access the data of a new node when using Rules event After saving new content?". It explains that "after saving something" actually happens ... "before saving something" (which is not a bug, simply how the Rules module  works ...). I wouldn't be surprised that this is also what explains your problem. Here is why I think so:


Your (main) rule uses the event "after saving something".
Assume that the rules action (to schedule your component) actually happens (also) "before saving something"; In that scenario the part of your message that says "The variable or parameter node is empty." makes sense ... (get it?).


So it would be interesting to see what would happen if (even only to test), you'd replace the (single) Rules Action (to schedule your Rules Component) by the execution of an additional Rules Component (let's call it "Test_tip_from_Pierre") which is scheduled to execute after X secs or mins, and with a single Rules Action (equal to your Rules Action you now have in your main rule). Using that approach, for sure the node will have been saved before you actually schedule your original Rules Component. And that is what might resolve (eliminate / prevent) your warning like "The variable or parameter node is empty."