How to setup to read DS18B20 temperatures (incl. unit) #134
-
|
Hi to all, Since in the wiki/ manual there is missing an example file with ACTIVATED sensors: THANK You very much! |
Beta Was this translation helpful? Give feedback.
Answered by
EKNYESE
Feb 8, 2022
Replies: 6 comments 5 replies
-
|
Hi @EKNYESE sorry for the slow response, I have not had much time for MQTTany in a while. I believe we were talking about this before and I found that your config file was not correct and I asked that you share the 1-Wire section for me to diagnose. I have examples on my To-Do list, but again time is the issue as it's just me working on this. Here is an example with your address that should work, though I am not able to test it at this time. onewire:
my-sensor:
address: '28-030b97942443' |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Hi Michael, As mqtt-signal I still get only "openHABianRPi4/device-id/address" with message: "28030B97942442E6" (without quotes). Here is my actual mqttany.xml (complete). Do you have an idea, what is wrong in my config regarding onewire? ######## 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
### 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:
my-sensor:
address: '28-030b97942443'
### Bus Interface
#bus: 'w1 interface'
### Polling Interval
#polling interval: 60 # 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:
#address: '28-030b97942442'
### 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**
#name: '{device_id}/temperature'
### 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: [] My actual workaround via shell-script (full functional - but still a workaround until right setup of your mqttany): #! /bin/bash
#Pruefen, ob Suffix angegeben
if [ -z "$1" ] ;then
echo "So geht das nicht"
exit 1;
fi
# Temperatur des Sensors auslesen
INPUT=$(/bin/cat /sys/bus/w1/devices/$1/w1_slave |tail -n1 |cut -d "=" -f 2)
TEMP=$(echo "scale=2; $INPUT / 1000" | bc)
# Wert ausgeben
echo $TEMP |
Beta Was this translation helpful? Give feedback.
-
|
Your config looks ok, though it should be Can you start MQTTany with the <details><summary>Log</summary>
```
PASTE YOUR LOG HERE
```
</details> |
Beta Was this translation helpful? Give feedback.
-
|
Hello, LogFor your infromation: in the last days I had a typo in my config regarding the DS18B20-adress. I have fixed this by inserting '28-030b97942442' instead of wrong '28-030b97942443' in the /etc/mqttany/mqttany.yml. Thanks for your support!! |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Technically the Glad to hear you got your config file sorted! Looks like there is something going on with the data type while decoding the response from the device. I don't think I made any changes there since before v0.12 and I know it was working then so not sure what's going on there. I will dig into it when I have time, hopefully this weekend. |
Beta Was this translation helpful? Give feedback.
-
|
Found and solved. I don't know how that ever worked (it definitely did for at least 1 user). I have opened a new issue for this bug #136. Keep an eye on that, I will push a fix shortly. You will need to switch to the git pull
git checkout masterIf you want to update to the next release version when it comes out use these commands, replacing git pull
git checkout VERSION |
Beta Was this translation helpful? Give feedback.
Answer selected by
CrazyIvan359
-
|
no idea, if it is helpful, but: when I execute following command in shell So I hope, that my cheap DS18B20 meet your specs.. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for the raw data, I can use that to test. Your sensor shouldn't be a problem, they are are supposed to speak the same language. Based on the error I think it is a problem with the way MQTTany handles the data. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Michael,
I am still hoping && waiting for your bugfix-release.
Is it please possible, to release e.g. with only minimal bugfix-updates as
#136?
I have to Setup a New openHAB instance and there have to decide, If I am
possible to use your almost perfekt mqttany (which convept is great!).
Thanks for your reply!
Michael Murton ***@***.***> schrieb am So., 13. Feb. 2022,
14:56:
… Found and solved. I don't know how that ever worked (it definitely did for
at least 1 user). I have opened a new issue for this bug #136
<#136>. Keep an eye on
that, I will push a fix shortly.
You will need to switch to the master branch to use it though, I have a
few other changes I need to get done before I make another release. Run
these commands in the directory you installed MQTTany to (ex /opt/mqttany)
to update to the master branch when you see the issue it closed.
git pull
git checkout master
If you want to update to the next release version when it comes out use
these commands, replacing VERSION with the version you want to update to
(ex v0.14.3):
git pull
git checkout VERSION
—
Reply to this email directly, view it on GitHub
<#134 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM52POOQJT52Z53LMXEYOTDU26Z7ZANCNFSM5LNGKPLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @EKNYESE you can use the fix anytime, it is part of the Where the instructions tell you to use this command: use this command instead: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi Michael, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have stopped first with "sudo systemctl stop mqttany" and executed "python3 mqttany/mqttany.py -vv", right?:
Log