# General advice/questions using ansible with RasPi's around the house **URL:** \ **Category:** Ansible Project\ **Created:** [December 29, 2022, 6:22pm UTC](https://forum.ansible.com/t/general-advice-questions-using-ansible-with-raspis-around-the-house/37508 "2022-12-29T18:22:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Tom\_Stewart](https://avatars.discourse-cdn.com/v4/letter/t/ec9cab/32.png) [@Tom\_Stewart](https://forum.ansible.com/u/Tom_Stewart)\ **Post date:** [December 29, 2022, 6:22pm UTC](https://forum.ansible.com/t/general-advice-questions-using-ansible-with-raspis-around-the-house/37508/1 "2022-12-29T18:22:41Z")
So, I’ve been hearing good things about ansible for years, and finally decided to take the plunge, figuring it might help me manage the collection of Raspberry Pi’s I’ve accumulated around the house doing various things. After a bit of struggle, I got to the point where I could log into all the Pi’s via SSH without explicit user credentials being passed on the command line. So then I put together an inventory file, and figured it was time to try out a “ping.” Of my 10 pi’s, I was successful on half of them. The other 5 run pre-packaged OS’s that apparently don’t fulfill all the requirements. 4 of these make up my home music system, and those run PiCorePlayer, which seemingly lacks a python installation. The 5th runs EyePi, an abandoned packaging of MotionEye that creates a streaming webcam (in my case, for weather). Ansible complains about not being able to create a tmp directory. On the EyePi, I doubt I am going to get very far, but I was hoping to find a way to specify where the tmp directory should go in my inventory file. But reading through the doc, I haven’t found such a setting. Q1: is there such a setting that can be stored in the inventory, so it’s always used when communicating with that host? On the PiCorePlayers, I was able to install a python3.8 extension, and that seems to have gotten me past that particular roadblock. So I guess for the most part, I am really just left with Q1… Thanks for any help! ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [January 5, 2023, 4:40pm UTC](https://forum.ansible.com/t/general-advice-questions-using-ansible-with-raspis-around-the-house/37508/2 "2023-01-05T16:40:37Z")
> Q1: is there such a setting that can be stored in the inventory, so it's always used when communicating with that host? This is part of the shell plugin [https://docs.ansible.com/ansible/latest/collections/ansible/builtin/sh\_shell.html#parameter-remote\_tmp](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/sh_shell.html#parameter-remote_tmp) Also note that while most modules shipped with Ansible are written in Python, Ansible can still execute modules written in other languages as long as the interpreter (Perl, Ruby, shell, etc) is present on the target OR you use a compiled language in which case the requirement is that the binary can be executed on the remote (I've see golang and haskell modules for example). ---
**Author:** ![Tom\_Stewart](https://avatars.discourse-cdn.com/v4/letter/t/ec9cab/32.png) [@Tom\_Stewart](https://forum.ansible.com/u/Tom_Stewart)\ **Post date:** [January 5, 2023, 4:56pm UTC](https://forum.ansible.com/t/general-advice-questions-using-ansible-with-raspis-around-the-house/37508/3 "2023-01-05T16:56:29Z")
Thanks, Brian. It’s probably just me, and because I’m new to Ansible, but I guess it surprises me that these appear to be “global” type variables that apply to all managed systems, instead of being able to apply to a single system. ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [January 5, 2023, 4:58pm UTC](https://forum.ansible.com/t/general-advice-questions-using-ansible-with-raspis-around-the-house/37508/4 "2023-01-05T16:58:13Z")
it's BOTH, the setting allows for setting an env var (global to run) or config item (same) or a variable (which can be global go play, assinged to a group or to a specific host).