Any plan to implement Ethernet GW?

[martinhjelmare]

@drock1985

Did you source ~/.bashrc before running that command? You need to make sure the virtualenvwrapper.sh script is run for the terminal session you are in, before you have the commands on your path. Sourcing it in .bashrc will make sure it runs when you login. The first time, you have to do it manually though, if you don't want to logout/login.

[drock1985]

@martinhjelmare

Hi,

Got it installed and compiled. But when I start Hass, I am getting errors about not being able to isntall Netdisco (or any other addon). Seems to want to start fresh on very boot.

The configuration file I used was in the homeassistant/config folder. There was a configuration.yaml.example file in there so I assumed thats where the config file would go.

[martinhjelmare]

@drock1985

Can you post your error log? Try installing netdisco manually with pip.

[drock1985]

@martinhjelmare

I tried manually installing Netdisco, but it won't compile. I get an error complaining about gcc failing with error status 1.

The config file it looks for is in my normal home folder (which I assume is correct). The only error in the log is that it could not initialize discovery because dependency netdisco 0.5.2 could not be installed.

I think I will try this again tomorrow with Debian or Ubuntu... seems to be a more favorable distro to install Home-Assistant to. I think I even may have an old Pi still kicking around.

[martinhjelmare]

@drock1985

You don't need discovery for mysensors, so you could disable that in the config if you don't have any other component that you want to activate which need discovery.

Do you have gcc installed and general packages for building, usually called build tools, build-essentials etc?

[drock1985]

@martinhjelmare

Haven't tried build-tools (tried build-essential, it couldn't find any packages) and I do have GCC installed.

Will try again when i'm done work for the evening and see what happens.

[martinhjelmare]

@drock1985

I think it's called development tools for Fedora. Google it.

If you can post the build log message, I could advise better. It could be a specific lib package that is missing for the compile. The log will usually give some hint on what's missing.

[martinhjelmare]

I've updated the branch at my fork of pymysensors. If you have installed the ethernet branch of my fork of home-assistant, you should uninstall/reinstall that, or just make a new virtual environment and install again. You should remove the lib directory in your home assistant config directory as well.

Eg:

rm -r ~/.homeassistant/lib
mkvirtualenv -p /usr/bin/python3 hasstest2
cd ~/dev/home-assistant
git branch -D mysensors-tcp-gateway
git fetch origin mysensors-tcp-gateway
git checkout mysensors-tcp-gateway
pip3 install -e .
pip3 install colorlog
pip3 install python-Levenshtein

[drock1985]

@martinhjelmare

Hi,

This is the error I am getting when starting up HASS.

(hasstest) pi@pitest:~/dev/home-assistant $ hass
Config directory: /home/pi/.homeassistant
16-03-05 20:07:56 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=turn_off, domain=homeassistant>
16-03-05 20:07:57 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=turn_on, domain=homeassistant>
16-03-05 20:07:57 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=toggle, domain=homeassistant>
16-03-05 20:07:57 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded introduction from homeassistant.components.introduction
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded updater from homeassistant.components.updater
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded conversation from homeassistant.components.conversation
16-03-05 20:07:57 INFO (MainThread) [homeassistant.loader] Loaded mysensors from homeassistant.components.mysensors
16-03-05 20:07:59 INFO (MainThread) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
16-03-05 20:07:59 INFO (MainThread) [homeassistant.loader] Loaded sun from homeassistant.components.sun
16-03-05 20:07:59 INFO (MainThread) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
16-03-05 20:07:59 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
16-03-05 20:07:59 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
16-03-05 20:07:59 INFO (MainThread) [homeassistant.components.introduction]

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        Hello, and welcome to Home Assistant!

        We'll hope that we can make all your dreams come true.

        Here are some resources to get started:

         - Configuring Home Assistant:
           https://home-assistant.io/getting-started/configuration/

         - Available components:
           https://home-assistant.io/components/

         - Troubleshooting your configuration:
           https://home-assistant.io/getting-started/troubleshooting-configuration/

         - Getting help:
           https://home-assistant.io/help/

        This message is generated by the introduction component. You can
        disable it in configuration.yaml.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

16-03-05 20:07:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=introduction>
16-03-05 20:07:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=recorder>
16-03-05 20:07:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=http>
16-03-05 20:07:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=history>
16-03-05 20:07:59 INFO (MainThread) [requests.packages.urllib3.connectionpool] Starting new HTTPS connection (1): pypi.python.org
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=None, new_state=<state updater.updater=0.14.2; friendly_name=Update Available @ 20:08:00 05-03-2016>, entity_id=updater.updater>
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=updater>
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=process, domain=conversation>
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=conversation>
16-03-05 20:08:00 ERROR (MainThread) [homeassistant.components.mysensors] Missing required configuration items in mysensors: port
16-03-05 20:08:00 ERROR (MainThread) [homeassistant.bootstrap] component mysensors failed to initialize
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=log, domain=logbook>
16-03-05 20:08:00 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=logbook>
16-03-05 20:08:00 INFO (MainThread) [requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): maps.googleapis.com
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=None, new_state=<state sun.sun=below_horizon; next_setting=22:12:29 06-03-2016, elevation=-21.55, next_rising=10:44:01 06-03-2016, friendly_name=Sun @ 20:08:01 05-03-2016>, entity_id=sun.sun>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=sun>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=discovery>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=api>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=frontend>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Starting Home Assistant (13 threads)
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homeassistant_start[L]>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=stop, domain=homeassistant>
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=restart, domain=homeassistant>
16-03-05 20:08:01 INFO (Thread-17) [homeassistant.components.http] Starting web interface at http://0.0.0.0:8123
16-03-05 20:08:01 INFO (Thread-15) [homeassistant.core] Timer:starting
16-03-05 20:08:01 INFO (Thread-18) [homeassistant.components.http] "GET /api/stream?api_password=no_password_set&restrict=state_changed,component_loaded,service_registered HTTP/1.1" 200 -
16-03-05 20:08:01 INFO (Thread-19) [homeassistant.components.http] "GET /api/bootstrap HTTP/1.1" 200 -^C16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Stopping
16-03-05 20:08:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homeassistant_stop[L]>
16-03-05 20:08:02 INFO (Thread-16) [netdisco.service] Scanning
^CProcess Process-1:
Traceback (most recent call last):
Traceback (most recent call last):
  File "/home/pi/.virtualenvs/hasstest/bin/hass", line 9, in <module>
    load_entry_point('homeassistant', 'console_scripts', 'hass')()
  File "/home/pi/dev/home-assistant/homeassistant/__main__.py", line 330, in main
    keep_running, exit_code = run_hass_process(hass_proc)
  File "/usr/lib/python3.4/multiprocessing/process.py", line 254, in _bootstrap
    self.run()
  File "/usr/lib/python3.4/multiprocessing/process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "/home/pi/dev/home-assistant/homeassistant/__main__.py", line 248, in setup_and_run_hass
    exit_code = int(hass.block_till_stopped())
TypeError: 'bool' object is not iterable
  File "/home/pi/dev/home-assistant/homeassistant/core.py", line 100, in block_till_stopped
    self.stop()
  File "/home/pi/dev/home-assistant/homeassistant/core.py", line 107, in stop
    self.pool.stop()
  File "/home/pi/dev/home-assistant/homeassistant/util/__init__.py", line 364, in stop
    self.block_till_done()
  File "/home/pi/dev/home-assistant/homeassistant/util/__init__.py", line 358, in block_till_done
    self._work_queue.join()
  File "/usr/lib/python3.4/queue.py", line 86, in join
    self.all_tasks_done.wait()
  File "/usr/lib/python3.4/threading.py", line 290, in wait
    waiter.acquire()
KeyboardInterrupt

 mysensors:
   gateways:
     - device: '192.168.1.10'
       persistence_file: '~/.homeassistant/mysensors3.json'
       tcp_port: 5003
   debug: true
   persistence: true
   version: '1.5'

[martinhjelmare]

@drock1985

Did you checkout correct branch?

git fetch origin mysensors-tcp-gateway
git checkout mysensors-tcp-gateway

You should remove the lib directory in ~/.homeassistant/ before you start hass again after the git checkout also.

rm -r ~/.homeassistant/lib

[drock1985]

Ugh, forgot to run the checkout command. palm smacks head

Booting now, will report back in a minute if it is working or not.

[martinhjelmare]

@drock1985

Don't forget to use the correct ip address of your gateway in your network.

[drock1985]

@martinhjelmare

It works! Found my motion sensor with ease. Will start adding lights now shortly

Thanks again, loving this.

EDIT: Quick question: To autostart this, would I just use the normal Home-Assistant instructions in the virtualenv, or is there another method to do it?

[martinhjelmare]

@drock1985

:thumbsup:

When you have time, can you run git log and tell me the top commit message, so I know which version you are using.

Regarding autostart, no I don't think you can use the normal instructions together with the virtualenv. You could write a script, that changes to the virtualenv and starts hass, and run that script at login or similar.

If you don't have another production install of home assistant on the computer, you can skip the virtualenv alltogether and just do:

pip3 install --user "https://github.com/MartinHjelmare/home-assistant/archive/mysensors-tcp-gateway.zip"

or if you want to install as root:

sudo pip3 install "https://github.com/MartinHjelmare/home-assistant/archive/mysensors-tcp-gateway.zip"

This way you should be able to autostart the usual way, per instructions on the web.

But then if you want to test an update from me, you have to make sure you uninstall everything correctly and manually remove ~/.homeassistant/lib before you install again.

[drock1985]

@martinhjelmare

Here is the info you requested:

commit d07f8097a6186611371b8bc918fcb0d436bb39ba
Author: MartinHjelmare <marhje52@kth.se>
Date:   Sat Feb 27 04:55:38 2016 +0100

    Add mysensors tcp ethernet gateway

    * Replace CONF_PORT with CONF_DEVICE and ATTR_PORT with ATTR_DEVICE.
    * Add tcp_port in config.
    * Use fork pymysensors repo, temporarily.
    * Try to guess if tcp or serial gateway is configured, by validating
        device name as an ip address. If successful setup tcp gateway, if it
        fails, setup serial gateway.
    * Update device_state_attributes to show correct device, ethernet or
        serial.

commit 278fdc0983a8528945e13cf912da82f3bc5fe14c
Merge: 6dc49df 8ffa368
Author: Daniel Høyer Iversen <daniel.h.iversen@ntnu.no>
Date:   Fri Feb 26 10:49:10 2016 +0100

    Merge pull request #1385 from balloob/rfxtrx

    improve rfxtrx sensor
:

[martinhjelmare]

@drock1985

Sorry, I forgot I've only updated the pymysensors project, so you checking the home-assistant git log is no use. Well, I think your're running the lastest version anyway, since you got it working just now. Everything should be ok.

Let me know if you experience any problems.

If everything seems ok for you after some time of testing, I don't see why we can't release this very soon. My limited testing after the lastest update, show no problems.

[Dave Dan]

Hey @martinhjelmare,

I finally got this working.

I'm doing tests with a couple of multi-sensors (Temp, Hum, Light & motion). The discovery worked very well, no issue at all after following all the above steps.

What I'm not seeing wotking are the updates. I always see the same values. I'm checking messages with MYSController and I see the GW is receiving the events and updates but I can't see new values showing in the portal.

Still testing ...

[martinhjelmare]

@Dave-Dan

Do you mean that the sensors are not showing the latest values in the gui?

If the last value from a sensor is the same as the previous value, a state change won't happen. So the value will be reported as being as old as the previous value. Could this explain what you see?

[Dave Dan]

actually, I just got it working ...

yes, I was referrring to that. The way I have built the sensor is that everytime a movement is detected is sending all sensors statuses to the GW. This sensors are designed to be plugged (no battery powered) so no concern on power consumption.

I restarted the server and now updates are working.

What I'm seeing in the log is constantly this message:
16-03-14 10:39:53 INFO (Thread-9) [mysensors.mysensors] Permission denied when writing to /home/pi/dev/home-assistant/path/mysensors3.json

If I'm not wrong this is the persistence.

Apart of this I now see updates coming in ...

[martinhjelmare]

Good!

The path to the persistence file must exist, not the file itself, but the directory tree above, and hass should have write permission to it.

I usually put the file in the same directory as configuration.yml.