can someone maybe tell me if this is still valid for the latest hassio image based on HassOS?
Interface adapter setup
When an interface adapter is used, sensors can be accessed on Linux hosts via owfs 1-Wire file system. When using an interface adapter and the owfs, the mount_dir option must be configured to correspond a directory, where owfs device tree has been mounted.
I want to use a 1Wire USB interface adapter (DS9490R) to read 1wire sensors using owfs.
Iâm too trying this, but with an i2c adapter and only with ResinOS. Iâve succeeded in getting owserver to run as an addon and access my adapter. But I never succeeded in getting any furtherâŚAnyone has a clue on how to proceed? If the onewire component would be able to access i2c and usb bus adapters, or a running owserver, that would be marvellous.
How did you get the OWFS server setup ? Right now i cant even get that far on HassOS. My setup is working as i tested it with windows⌠i could install and read the sensor there.
Thanks! I will try that one as well and see if it works
Update: Does not seem to work⌠it does not even get installed:
18-08-03 13:13:11 INFO (SyncWorker_11) [hassio.docker.interface] Pull image bestlibre/aarch64-owserver tag 0.1.0.
18-08-03 13:13:13 ERROR (SyncWorker_11) [hassio.docker.interface] Canât install bestlibre/aarch64-owserver:0.1.0 â 404 Client Error: Not Found (âpull access denied for bestlibre/aarch64-owserver, repository does not exist or may require âdocker loginââ)
I am thinking of installing an âexternalâ ow server based on a second Raspberry and implement the sensors connected to that Raspberry. Do you happen to know if thats even possible?
This is not clear to me as i these are strings not ip adresses?
And how can i read a temp sensor afterwards for example?
Hm i guess this is only working with 2 instances of HA right? Not with one Raspberry running hassio and a second raspberry running the owfs server based on raspbian stretch?
The mqtt topics are just text strings that prefix the values. The host running the mqtt server is specified in the mqtt configuration. My boxes look like this:
# Master HA (running HassOS, and also running the mqtt server addon)
mqtt:
broker: localhost
mqtt_eventstream:
publish_topic: master/topic
subscribe_topic: slave/#
# Slave HA (running raspbian)
mqtt:
broker: hassio.lan
mqtt_eventstream:
publish_topic: slave/raspbian
This way the master HA will read ALL topics under slave/, but the slaves will only know about the sensors connected to them.
Sounds good but i think i cant use that cause HA is not installed on my second raspberry only OWFS and MQTT is installed on that one.
Additionally i may have found another way to get the sensor data in, i could do it using nodered as well. Nodered installed on hassio was able to read my sensor connected to the owfs server using a node called:`
I have been trying to invent my own method. I have a remote RPi3 with temp sensor. I have installed the mosquitto-client and can make this command work. It sends the w1 data to the mqtt server which is running on the Home Assistant Rpi4 on a remote machine. However, I am unsure what to do with it once it arrives.
Okay I have finally figured this out and wow was I going about it all wrong. Itâs really quite simple.
So I set up a remote Rpi3 with a DS18B20 Temperature sensor on the 1 wire bus and I needed to get this data into HA without running HA on both devices.
Installed the mosquitto-client on the RPi3
Installed the paho.mqtt python3 module #sudo pip3 install paho.mqtt
Found a python script for reading the DS18B20 sensor and modified it to be mqtt friendly.
Removed password setting from the mosquitto server (broker). I have not yet figured out how to send un/pw via the python mqtt client module.
added a few lines to configuration.yaml so it can find the new temperature sensor.
Any news on the DS9490R (USB I2C Master Bus). Iâm trying to get my sensor data into the DS9490R but it doesnât work. It seems like a hardware/wiring issue to me. Someone who has succeeded in this?