How can i have access to all the features with a manual install

Installation
13

Very true. I would be considered an HA newbie and I am struggling to learn Python & Docker, among other things. I am an “old” Unix admin and have worked with Linux too.I have worked with all the install possibilities (except straight Docker) as I am searching for the “best supported” method. I am currently using a media player component that uses a custom Python module so that makes Docker inconvenient since that module needs to be reinstalled after every upgrade :frowning:

I am in the process of moving from a manual venv install to a Hassbian one.The venv upgrade to 0.91 series had serious unresolved dependency issues. I did eventually get it working, though.

14

There’s no difference between the manual venv and hassbian aside from possibly the hassbian scripts. But I never used those even when I was running hassbian so I’m pretty sure they aren’t of real importance. And you might be able to get similar functionality using manual venv as well.

So I doubt I would go to the trouble to switch for almost no (or none at all) real gain in functionality.

15

They recently added some z-wave dependencies that needed to be manually added to venv but were supposedly handled by Hassbian. That led me to believe it was better supported.

I do think they are concentrating on Hass.io / Docker mainly though for upgrade stability

16

You should be using custom components then and not installing anything in docker.

17

There is nothing in hass.io that you can’t put in a venv or docker install of HA.
My first try was hass.io. It lasted about 5 minutes as there was too much missing from the underlying OS for me. I then went to what are running now on a Pi 3 for a year or so, before switching to a bunch of docker containers on an old notebook I had sitting around.

If you want to know how to write YAML, check out some of the github repos for ideas.

I use VS code on windows 10 for most of my code, accessed via a samba share. I have GIT installed on the windows computer as well as the Linux notebook and VS code keeps the config files synced with my Github repositories.

If you be specific with your questions, people will try and help you work it all out.

1 Like
18

I would be surprised if that was the case and I’d like to see a link supporting that statement.

After the initial install of either hassbian or manually in a venv (I’ve done both on the same rpi) from then on everything was functionally the same between the two including the update process so I don’t see how there could ever be any differences between the two methods.

19

image
image785×241 11.7 KB

From Z-Wave - Home Assistant

My installation before 0.91 worked without those.

20

I don’t understand what you mean by this. Hassbian is just Raspbian with HA pre-installed in a venv so what exactly are you changing?

1 Like
21

See the post above yours. Somebody else asked for proof of the difference. :wink:

22

Assuming Raspbian is similar enough to Armbian, here’s what I used to set up everything by pasting a few commands into ssh:

First set a static IP and configure whatever else you need in raspbian-config, then follow the initial pi instructions up until they say to prepare the venv.

sudo -i

Paste #1:
add-apt-repository universe
apt update -y && apt install software-properties-common -y && apt install network-manager -y && apt install default-jre -y && apt install node.js -y && apt install python-pip -y && apt install python -y && apt install default-jre -y && apt install python3 -y && apt install python3-venv -y && apt install python3-pip -y && apt install python3-setuptools -y && apt install python3-dev -y && apt install libffi-dev -y && apt install python-dev -y && apt install socat -y && apt install jq -y && apt install apparmor-utils -y && apt install avahi-daemon -y && apt update -y && apt dist-upgrade -y && apt autoremove -y
ln -sf /lib/systemd/resolv.conf /etc/resolv.conf

Paste #2 (replace raspberrypi3 with the options below as needed)

curl -fsSL get.docker.com | sh
pip3 install setuptools wheel virtualenv --upgrade
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s – -m raspberrypi3

Then wait. and wait. and wait. It’ll take a good while to complete.

[options]

  • raspberrypi
  • raspberrypi2
  • raspberrypi3
  • raspberrypi3-64

If for some reason docker gets messed up, you can remove all the containers and just use the last curl command to reinstall hass .io

To remove all docker containers:
docker kill $(docker ps -q)
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q) -f
docker rmi $(docker images -q) -f

23

I don’t think you even understand how ridiculous this sounds.

:rofl:

1 Like
24

In my defence, I posted this last night but it didn’t post till this morning (the forums went down when I submitted it)

In any case, all anyone is doing at this point is defending my assertion a newbie probably doesn’t want to be screwing with a generic linux install of Hassio. It was after a year of using home assistant (tried the all-in-one on raspbian first, then hassio with ResinOS, then hassio with HassOS before I tried a generic linux install).

25

I understand your position but if you go back to the OP, it reads he doesn’t want to format his SD card for whatever reason. That will preclude installing hass.io or hassbian as both will wipe his SD card.
He also posted that he is a JavaScript developer so that means he has an acquaintance with at least one language.
He also states that he has installed the venv homeassistant and knows a bit about Linux.

@muscaiu, from my reading, isn’t interested in “installation wars” but rather how to get the best out of what he has.
Possibly little things like adding aliases to his Pi login to handle the user and path changes and activate the venv.
If he is editing his config on a remote computer, possibly a windows one considering he is a JavaScript developer, how to set up a samba share of the .homeassistant directory and force the correct permissions when saving the files.

At this stage I’ll be waiting until he clarifies what he wants.

26

thanks for the info.

But I still wouldn’t say that means that Hassbian is better supported. It just means that those libraries were added to the image and didn’t need to be installed manually. Once you do that then there isn’t any difference between hassbian in a venv & non-hassbian in a venv.

2 Likes
27

I think that is the best course of action right now.

28

Funny story.

I’m trying to learn how to integrate my 2 Sonoffs and Mijaa Temp sensor into HomeAssistant (remember still missing the Hassio Tab)

So i must be on the 5-th youtube video praying:
…Please don’t go to the Hassio Tab…
…Please don’t go to the Hassio Tab…
…FUCK!!!

:laughing::laughing::laughing:

29

I just did a quick search. Will this help?

30

I don’t have any mijiaa sensor but I’ve got a bunch of Sonoff’s and I don’t use (or need…or want) hassio.

What do you need to know?

Have you flashed them with another firmware yet?

31

Yes they are flashed with Tasmota and used in some of my custom apps, but i wanted to try HomeAssistant to see how easy it really is and what does it do.

Not giving up yet, thanks for all the explinations, i now understand why i don’t need the Hassio tab.

32

here is a configuration that is used for a sonoff basic that i had connected as an extension cord to a boot dryer:

switch:
  - platform: mqtt
    name: "Boot Dryer"
    state_topic: "stat/ext_2/POWER"
    command_topic: "cmnd/ext_2/POWER1"
    availability_topic: "tele/ext_2/LWT"
    qos: 0
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: false

the “ext_2” is the topic defined in tasmota.

put your config into the configuration.yaml and when you restart you will have switch in HA that controls the sonoff. Then you can include that in Lovelace and then you can control it from the frontend.

1 Like