@berkseo Do you have a what goes where description? like this but with a number instead of x
And the code, could you upload the code for this and for the SHT20 version?
@berkseo I'm trying to reverse engineer the BOM of this board, but I am quite unsuccessful. Could you please upload a BOM with (R1 = xxx k) or something similar, or Upload high-res closeups of the board so one can read the resistor values? Capacitors are a little harder, maybe you could share those values?
I have started on a BOM list, if you could help me fill it out, that would be much appreciated. I want to start soldering!!
Front
Back
@jrbenito I did jump the gun a little early. Sure, the gateway works, if you have externally connected devices, like an external MySensors gateway, but it does not work if you have the radio wired directly onto the RPi. It cannot fint the SPI.
Basically I did this:
A DockerFile (the .configure section needs to be modified to personal preferences)
FROM balenalib/raspberrypi3-debian
RUN apt-get update && apt-get install -y --no-install-recommends git bash make g++ \
&& cd /root \
&& git clone https://github.com/mysensors/MySensors.git --branch development \
&& cd /root/MySensors \
&& mkdir -p /data \
&& LDFLAGS="-static" ./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-gateway=ethernet --my-port=5003 --my-leds-err-pin=29 --my-leds-rx-pin=31 --my-leds-tx-pin=33 --my-rfm69-encryption-enabled --my-signing-request-signatures --my-signing=software --my-config-file="/data/mysensors.conf" \
&& make \
&& cd /root \
&& apt-get remove -y git make g++ && apt-get autoremove -y
EXPOSE 5003
ENTRYPOINT ["/root/MySensors/bin/mysgw"]
And a Docker-compose.yml file (ports needs to be configured. I think 5003 is not needed, since 5003 would be used if the gateway was handling the radio wired to the pins of the pi. Run with serial instead)
version: '3'
services:
portainer:
container_name: portainer
image: portainer/portainer:arm
restart: always
volumes:
- '/var/run/docker.sock:/var/run/docker.sock'
expose:
- 9000
ports:
- 9000:9000
mysensors:
build:
context: .
dockerfile: Dockerfile
container_name: mysensor_eth
restart: unless-stopped
privileged: true
devices:
- /dev/ttyACM0:/dev/ttyACM0
ports:
- 5003:5003
volumes:
- /mnt/usb1/mysensorsd/data:/data:rw
- /sys:/sys:rw
- /tmp:/tmp
The config file needs to be on a exposed volume and have the eeprom file pointed to the same volume
File mysensors.conf and it needs to be modified for signing keys and path to log aqnd eeprom
i had everything on /mnt/usb1/mysensors and folders data created within that path. I set access to full RW for everyone
# Logging
# Verbosity: debug,info,notice,warn,err
verbose=debug
# Enable logging to a file.
log_file=1
# Log file path.
log_filepath=/mnt/usb1/mysensors/data/mysgw.log
# Enable logging to a named pipe.
# Use this option to view your gateway's log messages
# from the log_pipe_file defined bellow.
# To do so, run the following command on another terminal:
# cat "log_pipe_file"
log_pipe=1
log_pipe_file=/tmp/mysgw.pipe
# Enable logging to syslog.
syslog=0
# EEPROM settings
eeprom_file=/mnt/usb1/mysensors/data/mysensors.eeprom
eeprom_size=1024
# Software signing settings
# Note: The gateway must have been built with signing
# support to use the options below.
#
# To generate a HMAC key run mysgw with: --gen-soft-hmac-key
# copy the new key in the line below and uncomment it.
soft_hmac_key=****************
# To generate a serial key run mysgw with: --gen-soft-serial-key
# copy the new key in the line below and uncomment it.
soft_serial_key=*******************
# Encryption settings
# Note: The gateway must have been built with encryption
# support to use the options below.
#
# To generate a AES key run mysgw with: --gen-aes-key
# copy the new key in the line below and uncomment it.
aes_key=**************
I do not use the MySensors on a docker. I had som many problems with it, SPI beeing one, and the LEDs an other.
It literally takes 3 minutes to set it up and run nativelly on a Pi, and this gives you full access to everything.
I run everything else in a docker.
@gahlawathome said in Help! openHAB 2.4 binding MQTT:
I have exactly same problem. Does it work for anyone not using the system broker?
Both binding and openhab are 2.4.
Googleing this problem at it is quite reoccurring that the questions are about "How to get mysensors mqtt gateway online". Something must be wrong with it, otherwise so many cannot report the same thing.
@TimO as the developer, do you have any leads?
@waspie said in Help! openHAB 2.4 binding MQTT:
yeah, mysensors in 2.4+ is very touchy.
Have you restarted the openhab service lately?
Try deleting your mysensors gateway then restart openhab and re-add the mysensors mqtt gateway. Just for grins...
I did that now... same thing...
So, The "Mysensors Binding" creates a Thing, "Mysensors MQTT Gateway".
The "Mysensors MQTT Gateway" needs a "MQTT Broker" Thing. This thing is called "mosquitto". The mosquitto thing is configured to connect to 127.0.0.1:1883
In "Mysensors MQTT Gateway" I say "Broker Name" is "mosquitto".
In log "Mysensors MQTT Gateway" says "No connection to broker: mosquitto"
Maybe I should just revert back to Ethernet. I have spent 3 days with this, and somthing that "mysterious" can just not be right.
@waspie said in Help! openHAB 2.4 binding MQTT:
i dont know what folder path your stuff would be in exactly but can you list openhab???/userdata/config/org/openhab/
Looks like this:
I tried some experiments. I made a simple flow in node-red. Listen to "mysensors-out/#" then print it to debug. And yes, it works.
I also tried to add a channel to the "MQTT Broker" thing, also "mysensors-out/#"
It showed up without any problems... not very usable, but can see the connection...
But the "Mysensors MQTT Gateway"... just dead in the water...
@waspie said in Help! openHAB 2.4 binding MQTT:
this is 2.4.0 and not a 2.5.x build, right?
Yes it is the 2.4 build. Both OH is 2.4 and mysensors is 2.4 (any newer is not available to my knowledge)
OH is an installation from a docker image (openhab/openhab:2.4.0)
Trace file does not look very healthy...
@waspie said in Help! openHAB 2.4 binding MQTT:
fd3193ea
OK, thanks. I changed the "Broker name" in Mysensors MQTT Gateway in OH to fd3193ea.
The Mysensors thing is still "Offline" though... I rebooted every thing... but still offline...
@waspie said in Help! openHAB 2.4 binding MQTT:
I dont see a broker in your things view. Please re-snip and post
@waspie said in Help! openHAB 2.4 binding MQTT:
what is the name of that broker?
I don't know how to answer that.... You vitually see my screen (all the screen shots).. What you see is what I have. Where do I see the name of the broker?