OneWire Bug #120
Labels
OneWire
OneWire Module
Comments
|
Looks like I did not remove the note in the docs to install One Wire requirements, there are none anymore. I wrote my own One Wire interface library so no external ones are needed. What else are you hung up on getting your sensors working? |
|
Unfortunately I was not able until now to use it for DS18B20. Maybe it is a problem with user-rights - I am using openhabian as base. Do You have an idea, how to interpret this failure message?: |
|
That is possibly an issue with the One Wire module, I will need some more information to dig into it though. Please run MQTTany with the Please use code fences when posting logs or configs so that they are readable. Here are examples: As for the possible access issues, I don't remember if openhabian has the udev rules or not, but you should follow the instructions on the One Wire page to install the ones included with MQTTany. |
|
Thanks for your response! LogConfig######## Configuration for MQTTany ########
# All optional values are commented out and default values are shown
### Config file version
version: '1.0'
######## MQTT Module ########
mqtt:
### Broker Host
# can be either IPv4 address or hostname
host: 'openHABianRPi4'
### Broker Port
# port to connect to on the host
port: 1883
### Client ID
# Substitutions:
# - {hostname} = the computer's hostname
#client id: '{hostname}'
### Login
#username:
#password:
### Session Options
#qos: 0
#retain: false
### Topics
# Substitutions:
# - {hostname} = the computer's hostname
# - {client_id} = the mqtt 'client id'
# topics are composed as `{root topic}/{node id}/{property id}`
#root topic: '{client_id}' # Root topic
#root topic 'openhabian'
# last will topic becomes `{root topic}/{lwt topic}`
#lwt topic: 'lwt' # Last Will topic
### Heartbeat
# Interval in seconds to publish status messages
heartbeat interval: 300
######## GPIO Module ########
gpio:
### Pin Numbering Mode
mode: 'SOC'
### Polling Interval
polling interval: 60 # interval in seconds to poll all pins
### Interrupt Debounce
debounce: 50 # in milliseconds
### Single Pin Configuration
#pin-id:
#pin05:
### Pin Number
#pin: 5
### Pin Name
# Subsitutions:
# - {pin} = pin number
# - {pin:02d} = pin number padded with 0's to always be 2 numbers
# - {pin_id} = name of this section
#name: '{pin_id}'
### Pin Mode
#pin mode: 'input' # can be 'input' or 'output'
#pin mode: input
### Pin Resistor
#resistor: 'off' # can be 'pullup', 'pulldown', or 'off'
#resistor: pullup
### Pin Type Specifc Options
# Each pin type will have some options specific to it,
# consult the documentation for details.
#digital:
# interrupt: both
# invert: true
pin05:
pin: 5
# name: '{pin_id}'
pin mode: input
resistor: pullup
digital:
interrupt: both
invert: true
pin06:
pin: 6
# name: '{pin_id}'
pin mode: input
resistor: pulldown
digital:
interrupt: both
invert: false
pin13:
pin: 13
# name: '{pin_id}'
pin mode: output
resistor: pullup
digital:
invert: true
initial state: 'ON'
pin19:
pin: 19
# name: '{pin_id}'
pin mode: output
resistor: pullup
digital:
invert: true
initial state: 'ON'
pin26:
pin: 26
# name: '{pin_id}'
pin mode: output
resistor: pullup
digital:
invert: true
initial state: 'ON'
pin16:
pin: 16
# name: '{pin_id}'
pin mode: output
resistor: pullup
digital:
invert: true
initial state: 'ON'
### Multiple Pin Configuration
# alternatively a list of pins can be given.
# actual id's will be '{batch-id}-{index + first index}'
# all options from a single pin configuration apply, except those shown below
#batch-id:
### Pin Name
# a single name may be given, or a list of names the same length as the
# list of pins can be provided. if a single name is given then actual names will
# be '{name} {index + first index}'
# Subsitutions:
# - {pin} = pin number
# - {pin:02d} = pin number padded with 0's to always be 2 numbers
# - {pin_id} = name of this section
# - {index} = the pin's index in the list of pins plus 'first index'
#name: '{pin_id}'
### Pin Numbers
#pin: []
### First Index
# this number will be added to 'index' when substituting '{index}' in id's and names
#first index: 0
######## I2C Module ########
#i2c:
### Polling Interval
#polling interval: 60 # interval in seconds to poll all pins
### Device Configuration
# !! this id is used as the node so it must not match any other node or module name !!
#device-id:
### Device Friendly Name
# Friendly name used in logging etc
# Substitutions:
# - {device_id} = name of device's section in config file
# - {address:02x} = device address in hex (ex. '20')
# - {device} = device identifier
#name: '{device_id}'
### Device Type
# Device identifier, see the wiki for a list of supported devices
#device: ''
### I2C Bus ID
# ID of the I2C bus to use on your SBC
# ex. Raspberry Pi 3 this will probably be 1
# Can also specify full path ex. '/dev/i2c-1'
#bus:
### Device Address
# 7-bit hex address of the device (ex. 0x20)
# this can also be a base-10 integer
#address: 0x
### Device Specific Options
# Each device type will have some options specific to it
# consult the wiki page for the device for details.
######## OneWire Module ########
onewire:
### Bus Interface
bus: 'w1'
### Polling Interval
polling interval: 10 # interval in seconds to poll all devices
### Bus Scan
# Scan bus for any unconfigured devices and add them
bus scan: true
### Device Configuration
device-id:
### Device Name
# Substitutions:
# - {device_id} = will be replaced with the device definition section name
# - {device_type} = will be replaced with the device type (ex. `DS18B20`)
# - {address} = will be replaced with the device's **FULL 8 BYTE ADDRESS**
ds18b20:
unit: 'C'
address: '28-03209779ee7e'
#name: '{device_id}'
name: '{address}'
### Device Address
# The device's address, can be 7 or 8 bytes, can use w1 style `xx-xxxxxxxxxxxx`
# address: '28-030b97942442' # **MUST BE IN SINGLE QUOTES `''`**
### Device Specific Options
# Each device type will have some options specific to it
# consult the wiki page for the device for details.
### Multiple Device Configuration
#batch-id:
### Device Name
# a single name may be given, or a list of names the same length as the
# list of pins can be provided. if a single name is given then actual names will
# be '{name} {index + first index}'
# Substitutions:
# - {device_id} = will be replaced with the device definition section name
# - {device_type} = will be replaced with the device type (ex. `DS18B20`)
# - {address} = will be replaced with the device's **FULL 8 BYTE ADDRESS**
# - {index} = will be replaced with the device's index in the list of addresses
#name: '{device_id}'
### Device Address
# List of device addresses, can be 7 or 8 bytes, can use w1 style `xx-xxxxxxxxxxxx`
#address: ['', ''] # **MUST BE IN SINGLE QUOTES `''`**
### First Index
# this number will be added to 'index' when substituting '{index}' in id's and names
#first index: 0
######## LED Module ########
#led:
### Animation Directory
# A directory or list of directories to look for additional animations in
#anim dir: []
### Startup Animation
# Animation to play when MQTTany loads
#anim startup: 'test.array'
### Array Configuration
#array-id:
### Array Name
# Substitutions:
# - {array_id} = will be replaced with the array definition section name
#name: '{array_id}'
### Output
# The interface to use for outputting data
# Available options are 'rpi' or 'sacn'
#output: ''
### Pixel Count
# The number of pixels in your array (not necessarily LEDs, see next option)
#count:
### LEDs per Pixel
# Allows you to have more than one LED handled as a single pixel.
# Ex. A bulb with 3 LEDs in it can be treated as a single pixel in the array.
# Total number of LEDs in the array should be 'count' times 'leds per pixel'
#leds per pixel: 1
### Initial Brightness
# The initial brightness of the array, can be 0-255
#brightness: 255
### Color Order
# The byte order for the color data sent to the LEDs.
# See the 'test.order' animation for how to determine this
#color order: '{default}'
### Animation Frame Rate
# Frame rate for animations, you may need to decrease this for
# longer arrays or certain interface types.
#anim fps: 60
### Interface Specific Options
# Each interface may have some options specific to it
# consult the wiki page for the interface for details.
######## XSET Module ########
#xset:
### Default Display
# Display option to use when commands do not specify a display.
# Omitting this option will omit the '-display' option from the call to xset
#default display: None
### Startup Commands
# A list of commands to run when the module loads.
# See the documentation on sending commands for formatting.
# If none are desired, use an empty list as shown below.
#startup commands: [] |
|
I edited your comment to use collapsible sections because I'm on my phone. So the udev rules file is here which if you followed the instructions to the letter should be in There is definitely a bug in the One Wire module though, your config is fine. I will look into that later this week when I have time. As for getting One Wire configured and also your GPIO working, because the log is telling me it isn't, let's switch to discussion #121 |
|
@EKNYESE sorry it took so long to get back to this, I have not had much time to work on MQTTany this year. I came to work on this issue but looking through everything here again I found that the problem is actually with your config. This key in the ### Bus Interface
bus: 'w1'It should be 'bus interface' and not 'bus' ### Bus Interface
bus interface: 'w1' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
"pip3 install -r requirements/onewire.txt" not possible since missing!!
Expected behavior
"pip3 install -r requirements/onewire.txt" possible
Environment
Configuration
# n/a because of missing example (although I have invested severals hours it was still not possible for me to get en example how to patch the config for several DS18B20..Logs
The text was updated successfully, but these errors were encountered: