Home Assistant

I found this https://github.com/oneyb/rpi-embed-dev/blob/master/install-mysensors-gateway-raspberry.yaml but I don't know how it can be implemented.

OK SOLVED! I reinstalled the last version of mysensors library and i uploaded again the sketch to arduino node and now i can see my light sensor! Thank you very much for your help. Best Regards

solved i just comment below line of my code: //#define MY_CONTROLLER_IP_ADDRESS 192,168,1,6 //#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED and delete mysensors.pickle1 file . thanks @mfalkvidd for your trial to support me.

Ok a bit of an update. I removed my "version" part from config...yaml. I then removed the mysensors.pickle file, restarted HA and then restarted my nodes. And voila, the started showing up. So either there was something wrong with the pickle-file or the version data didn't work. But I can see now that the gw sends it's version to HA all the time, like a heartbeat. I'm not sure if this is correct or not. Now I just need to figure out how to change the names of the sensors in HA to get them more like all my other devices.

Ok so after further reading I found info on the issue, it seems that these are debug messages, we can safaly ignore them. homeassistant forum

@oneyb thanks for your suggestion, and sorry for the late reply. I worry that the install page is large enough as it is. People tend to be afraid of long texts, and just ignore stuff if there is too much text. Therefore, we try to keep the guides as minimal as possible, but still covering the most common cases. The full documentation is still available for those who want to dive deeper. If you have any idea on how to handle it differently, you're very welcome to speak up.

@tdecurtins https://www.home-assistant.io/components/mysensors/#presentation Home assistant only supports ethernet gateways that act as servers. So home assistant will connect as the client, ie we only configure the gateway address in home assistant, not the other way around.

did you figure this out? i keep getting errors trying to declare mhz

@soloam If you changed the optimistic setting, actuators will have assumed state and this will show in the ui as two different buttons for on and off. I recommend to not use optimistic setting, but instead feedback the new state to home assistant.

@martinhjelmare Oh it's true, I've tried it with V_IR_SEND and it worked. Thank you.

@tom-carpenter How did you configure the serial gateway in configuration.yaml? can you please post that section? Also what arduino hardware did you use? Thanks

I am having the exact same issue as kobipes. I am also on hass.io and I have not been able to resolve it. I am using an Arduino Nano with the RF24l01 connected to a Pi using USB (ttyUSB0). No go, configuration errors as stated from your post. However when I use an Arduino Uno on ttyACM i managed to get it working as long as you cold boot the Pi during config changes. Any help will be really appreciated!

HASSIO 0.70 on RPi with serial gateway attached still having configuration check problem with mysensors when executing hassio ha check This is what I did to try to solve: Deleted the configuration.yaml and the mysensors.json Restarted the RPi and hassio installed the default configuration.yaml Added the following mysensors configuration to the default configuration.yaml mysensors: gateways: - device: '/dev/ttyUSB0' persistence_file: 'mysensors.json' persistence: true retain: true version: '2.2' Restarted the Rpi and checked that hassio had installed the mysensors.json in the /config directory All my sensors were added to the mysensors.json The whole system seems to work OK! However when I run "hassio ha check" on the RPi I get the following error: core-ssh:~# hassio ha check ERROR Testing configuration at /config Failed config mysensors: - Invalid config for [mysensors]: /config directory does not exist or is not writeable for dictionary value @ data['mysensors']['gateways'][0]['persistence_ file']. Got 'mysensors.json' not a valid value for dictionary value @ data['mysensors']['gateways'][0]['devic e']. Got '/dev/ttyUSB0'. (See /config/configuration.yaml, line 59). Please check the docs at https://home-assistant.io/components/mysensors/ - config: ? frontend: ? javascript_version: auto group: ? history: ? exclude: ? include: ? use_include_order: False http: ? introduction: ? logbook: ? logger: [source /config/configuration.yaml:52] default: info logs: [source /config/configuration.yaml:54] homeassistant.components.mysensors: debug mysensors: debug mysensors: [source /config/configuration.yaml:59] gateways: [source /config/configuration.yaml:60] - device: /dev/ttyUSB0 persistence_file: mysensors.json persistence: True retain: True version: 2.2 script: ? updater: ? include_used_components: False reporting: True Successful config (partial) mysensors There are no errors in the system log! According to the log the system is reading and writing fine to and from the mysensors.json The secondary annoyance from this problem is the fact that I cannot reload the configuration file after a change. The only way to reload the configuration file is by powering off/on the RPi I added an issue on github: https://github.com/home-assistant/hassio/issues/478 Any help appreciated

Sorry to hear that. I think the .img file is the same but I'm not 100% sure.

@kobipes I think you will get the best help regarding USB exposure in Hass.io in the Hass.io section of the home assistant community forum. I'm using hassbian.

Ehh. I need a little help. I have a problem with change relay to light in HA. And i use in HA optimistic: true. Without it i can't change status of relay. My knowledge about programming is to low.