And of course you should know that the comunication is via "serial protocol", which is defined here:
https://www.mysensors.org/download/serial_api_20
@Guillermo-Schimmel said in 
Selecting a Controller:
@3nibble https://pypi.org/project/pymysensors/ is a nice starting point.
@3nibble https://pypi.org/project/pymysensors/ is a nice starting point.
@3nibble yes, you can talk directly to the ethernet gateway or, more easily, to the MQTT gateway. I tend to unify all my sensors, mysensors or not, over MQTT.
@Klabbe great! perhaps I'll go back to ethernet gateway. Do you think is better option over mqtt gateway?
I think so. I have a lot of battery powered nodes heavily using smartsleep and they work just fine with MQTT.
Well it seems that there isn't and ther won't be a mysensors binding anymore. It was abandoned by the developer.
So as of december 2020, with OpenHAB 3, the way to go is plain MQTT.
I can't say I disagree really. MQTT is simple and works.
I'm going to start from scratch and try to document my experience here.
@rejoe2 said in sending an image without wifi / envoi d'une image hors wifi:
@Guillermo-Schimmel It indeed should not be to difficult, but still there are some questions to be addressed:
- Is there any common standard (e.g. mark start and end of transmissions with keywords like "START" or "END") in stream messages (other than OTA)?
Not that I know of. I'm afraid you are on uncharted territory now.
- How about multi stream options (different ChildIDs).
Afaik the ony sample transfer code ist this one. Using that as a base, I recently built a (not yet tested) version that most likely will be part of the FHEM integration, so I'd really appreciate some common approach to that topic to not propose a somehow "strange" implementation.
This is a nice implementation.
If it were me, I would try to seek compatibility with MQTT, I mean send the images in some form that they could be decoded by any subscriber to my broker.
But regarding header, start/stop and child id I'm afraid you are going to make your own.
Thanks a lot for this effort, I think it would be useful for a lot of us.
But no answer on that question until now.
@Oitzu Great work. Looking forward to use it. I have a use for this (some remote roof drain that gets clogged with leaves). Thanks!
Do you have the image already in some standard form? Like png or jpg? Or do you have the raw data?
In any case you can split the data, send it and reassemble. Shouldn't be difficult.
@badmannen are you sure that your arduino doesn't have a bootloader? why are you trying to modify it?
If it doesn't have a bootloader, or if you want to play with FOTA, then what you are doing it's ok, that is the way I did it.
1st: In order to upload soft using a cable, you don't need to modify the bootloader. Any bootloader will work.
if and only if you want to experiment with FOTA (uploading firmware via wireless), then:
2nd: if you want to use FOTA and you choose MYSBOOTLOADER, then please check the fuses and lock bits, I dont remember them all. But it seems ok, have a try and let us know!
@badmannen 76 is the default. I uploaded different versions for all the channel numbers.
Have in mind that they all have to match (gateway and all the nodes).
If they don't match they aren't going to see each other.
@waspie it's not so much pain. I have it working fine. Setup could be simpler, but it works.
The main advantage, at least for me, is unifying all over mqtt. I have mysensors, but also some server monitoring scripts, a vacuum cleaner control, etc.
It's really nice to have a single layer of abstraction between openhab and everything else.
You have to present a node and it will appear as a thing. The rest can be empty.
I'm talking about mysensors-binding over mqtt, which is what I'm using.
I think you are right. I have misinterpreted +-3 as +-3% of the value. It seems that is +-3 absolute %RH.
Thanks a lot.
Hi Guys
I just assembled two very simple nodes based on the BME280.
Same Standard sketch on both (we should add one in the main site, there is not an example), battery powered.
They both work fine, but look at this:
Pressure looks fine:
But temperature and humidity are out of declared Bosch specs:
Any recommendation? Could it be a case of fake sensors? They weren't exactly cheap.
Thanks
@mahonroy It is a very interesting experiment indeed.
I just connected the batteries to the arduino, no boosting. But I have space for 2 AAs. With coin things surely are harder.
I can't help you now but will keep watching your results. Good luck!
@mahonroy Why so extreme? What is your power budget? I'm using a standard sketch for the same sensor and the power consumption is negligible.
I even added a 2 second (2000ms) powered on delay in order to mycontroller.org to detect the parent EUI.
At least show that you can do that (use Arduino ide OR AVRDUDESS)
Arduino IDE 1.6.x installed
Mysensors lib > 1.5.x installed
You should probably update that to 1.8.8 and 2.3.1. It is not allways related to FOTA but it is allways better to stay updated.
@mfalkvidd said in Arduino pro mini dead after flashing MYSbootloader.:
Great work @jimmy-loyens
Since you now have a working system, would you mind writing down what was needed? I think you are in a good position to describe things so a newbie (like myself, at least when it comes to ota) can understand? Maybe something that can make https://www.mysensors.org/about/fota easier.
I will send you some little things to improve it:
Feel free to post my github project "https://github.com/guillebot/MYSensors-Bootloaders"
I will keep updated the different channel versions and probably will upload my script and some info about compiling them.
@jimmy-loyens Great!
I have to say that the work done with the bootloader and mysensors is really good.
It is very nice when FOTA starts working.
@mfalkvidd Compiling the bootloader in a linux machine is as easy as running make, given than you have devel tools and avr-gcc installed.
@jimmy-loyens https://github.com/guillebot/MYSensors-Bootloaders
The bootloader for all the channels, in 1, 8 and 16MHz flavor.
@timo Via files. It was the old broker I was using with the 1.x mqtt binding.
@timo said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:
@guillermo-schimmel You've mixed up attributes from the MySensors binding and the MQTT binding in the bridge definition. brokerName, topicSubscribe and so on are attributes from the MySensors binding. But this won't do any harm.
Thanks, cleaned up config file:
Bridge mqtt:broker:mosquittotexto [ host="localhost",
port="8884",
secure=false,
startupCheckEnabled=false ]
{
Thing mqtt:topic:miscosas {
Channels:
Type number : ecovacs_1_battery_level "Ecovacs 01 Battery Level" [ stateTopic="ecovacs/E0000693817701104736/battery_level" ]
Type string : ecovacs_1_charge_status "Ecovacs 01 Charge Status" [ stateTopic="ecovacs/E0000693817701104736/charge_status" ]
Type string : ecovacs_1_clean_status "Ecovacs 01 Clean Status" [ stateTopic="ecovacs/E0000693817701104736/clean_status" ]
Type string : ecovacs_1_vacuum_status "Ecovacs 01 Vacuum Status" [ stateTopic="ecovacs/E0000693817701104736/vacuum_status" ]
Type string : ecovacs_1_fan_speed "Ecovacs 01 Fan Speed" [ stateTopic="ecovacs/E0000693817701104736/fan_speed" ]
Type number : ecovacs_1_main_brush "Ecovacs 01 Main Brush" [ stateTopic="ecovacs/E0000693817701104736/components/main_brush" ]
Type number : ecovacs_1_side_brush "Ecovacs 01 Side Brush" [ stateTopic="ecovacs/E0000693817701104736/components/side_brush" ]
Type number : ecovacs_1_filter "Ecovacs 01 Filter" [ stateTopic="ecovacs/E0000693817701104736/components/filter" ]
Type number : server_bluecherry_disk_root "Server Bluecherry Root Partition" [ stateTopic="servers/bluecherry/disk/root" ]
}
}
Restarted all, still all working fine.
@timo Mysensors gateway is defined via Paper UI:
have a look
Bridge mqtt:broker:mosquittotexto [ host="localhost",
port="8884",
secure=false,
brokername="mosquitto",
topicPublish="mysensors1-in",
topicSuscribe="mysensors1-out",
startupCheckEnabled=false ]
{
Thing mqtt:topic:miscosas {
Channels:
Type number : ecovacs_1_battery_level "Ecovacs 01 Battery Level" [ stateTopic="ecovacs/E0000693817701104736/battery_level" ]
Type string : ecovacs_1_charge_status "Ecovacs 01 Charge Status" [ stateTopic="ecovacs/E0000693817701104736/charge_status" ]
Type string : ecovacs_1_clean_status "Ecovacs 01 Clean Status" [ stateTopic="ecovacs/E0000693817701104736/clean_status" ]
Type string : ecovacs_1_vacuum_status "Ecovacs 01 Vacuum Status" [ stateTopic="ecovacs/E0000693817701104736/vacuum_status" ]
Type string : ecovacs_1_fan_speed "Ecovacs 01 Fan Speed" [ stateTopic="ecovacs/E0000693817701104736/fan_speed" ]
Type number : ecovacs_1_main_brush "Ecovacs 01 Main Brush" [ stateTopic="ecovacs/E0000693817701104736/components/main_brush" ]
Type number : ecovacs_1_side_brush "Ecovacs 01 Side Brush" [ stateTopic="ecovacs/E0000693817701104736/components/side_brush" ]
Type number : ecovacs_1_filter "Ecovacs 01 Filter" [ stateTopic="ecovacs/E0000693817701104736/components/filter" ]
Type number : ecovacs_1_ncommand "Ecovacs 01 Number Command" [ commandTopic="ecovacs/E0000693817701104736/command" ]
Type string : porton_a_mano "Garage Porton a Mano" [ stateTopic="mygateway1-out/11/3/1/0/16" ]
Type number : server_nextcloud_disk_root "Server Nextloud Root Partition" [ stateTopic="servers/nextcloud/disk/root" ]
Type number : server_bluecherry_disk_root "Server Bluecherry Root Partition" [ stateTopic="servers/bluecherry/disk/root" ]
}
}
@grumpazoid It is not the same module. Is another with a simpler antenna.
@timo said in OpenHAB Mysensors binding 2.4: cant get mqtt gateway online:
Hey @jimmy-loyens !
I needed some time to investigate the problem and after looking into it, I've no clue why this is working for you @Guillermo-Schimmel .
With version 2.4.0 and the changes to the mqtt binding I'm not able to connect the MySensors binding to the MQTT broker connection configured in OpenHAB. The MySensors binding uses the MQTT implementation and connection of OpenHAB, it does not connect to the broker itself.
And now the funny part: my development system works fine, so I need to find a way to debug this problem.
@Guillermo-Schimmel Did you configure broker and things in PaperUI or in textual files?
Some in files, some in Paper UI.
I think I have a mess, but don't want to touch it because it's working so nicely...
@grumpazoid I did the same but on the tip of the PCB antenna and can confirm that increases the range a lot!
@macieiks Hi!
How are you powering the node?
I had a lot of trouble with heat with mine. The 1117 regulator on the arduino uno wasn't coping with the w5100 power requirements.
It was triggering the thermal cut on it (100+ ºC!!!)
Is your Uno hot?
@guillermo-schimmel Well, solved.
Good brands not means good quality.
Replaced my Cisco switch for a unbranded one:
0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:GW MODE
15 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
w5100 init
w5100.cpp: detect W5200 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5500 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5100 chip
Wiznet soft reset
mr=0
chip is W5100
590 GWT:TPC:IP=192.168.1.200
1598 MCO:BGN:STP
1600 MCO:BGN:INIT OK,TSP=1
1603 GWT:TPC:IP=192.168.1.200
2606 GWT:RMQ:MQTT RECONNECT
2615 GWT:RMQ:MQTT CONNECTED
Connected at the first attempt.
Thank you guys a lot for your time.
@mfalkvidd Thanks for the tips
I did all that
0 MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:GW MODE
15 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
w5100 init
w5100.cpp: detect W5200 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5500 chip
Wiznet soft reset
mr=0
w5100.cpp: detect W5100 chip
Wiznet soft reset
mr=0
chip is W5100
590 GWT:TPC:IP=192.168.1.200
1598 MCO:BGN:STP
1600 MCO:BGN:INIT OK,TSP=1
1603 GWT:TPC:IP=192.168.1.200
2606 GWT:RMQ:MQTT RECONNECT
3610 TSM:READY:NWD REQ
3647 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
3656 GWT:TPC:IP=192.168.1.200
4660 GWT:RMQ:MQTT RECONNECT
5664 TSF:MSG:READ,2-2-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0
5669 TSF:MSG:READ,0-2-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
5675 TSF:MSG:BC
5677 TSF:MSG:READ,11-11-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0
New temp:
29.19
5709 GWT:TPC:IP=192.168.1.200
6713 GWT:RMQ:MQTT RECONNECT
7717 TSF:MSG:READ,10-2-0,s=1,c=1,t=13,pt=2,l=2,sg=0:48
7723 GWT:TPC:IP=192.168.1.200
8726 GWT:RMQ:MQTT RECONNECT
9732 GWT:TPC:IP=192.168.1.200
10735 GWT:RMQ:MQTT RECONNECT
11766 GWT:TPC:IP=192.168.1.200
12769 GWT:RMQ:MQTT RECONNECT
13774 GWT:TPC:IP=192.168.1.200
14777 GWT:RMQ:MQTT RECONNECT
15783 GWT:TPC:IP=192.168.1.200
16786 GWT:RMQ:MQTT RECONNECT
17819 GWT:TPC:IP=192.168.1.200
18822 GWT:RMQ:MQTT RECONNECT
19827 TSF:MSG:READ,10-2-0,s=1,c=1,t=13,pt=2,l=2,sg=0:47
19832 TSF:MSG:READ,10-2-0,s=2,c=1,t=0,pt=7,l=5,sg=0:27.62
19837 GWT:TPC:IP=192.168.1.200
20841 GWT:RMQ:MQTT RECONNECT
21849 GWT:TPC:IP=192.168.1.200
22851 GWT:RMQ:MQTT RECONNECT
23882 GWT:TPC:IP=192.168.1.200
24885 GWT:RMQ:MQTT RECONNECT
25890 GWT:TPC:IP=192.168.1.200
26894 GWT:RMQ:MQTT RECONNECT
27901 GWT:TPC:IP=192.168.1.200
28904 GWT:RMQ:MQTT RECONNECT
29910 TSF:MSG:READ,1-1-0,s=1,c=1,t=1,pt=7,l=5,sg=0:62.6
29941 GWT:TPC:IP=192.168.1.200
30945 GWT:RMQ:MQTT RECONNECT
31160 GWT:RMQ:MQTT CONNECTED
It seems to detect quickly the w5100 and then the delay is elsewhere.
I will try to do the same on some other modules. Perhaps the speed and duplex negotiation.
@mfalkvidd said in Ethernet MQTT Gateway Slow to connect:
@guillermo-schimmel wouldn't it be a bit surprising if there is a delay that is only active on your system?
Sure. I'm not meaning that. Sometimes not being an english speaker is tough.
I mean that some combination of settings that I may have done (wrongly?) perhaps generated that delay.
@yveaux said in Ethernet MQTT Gateway Slow to connect:
@guillermo-schimmel shot in the dark: make sure your Mac ID is unique on your network, or switches will get very confused
Thank you for the suggestion. This is one of the lines I'm investigating.
192.168.1.200 de-ad-be-ef-fe-ed dynamic
At the moment it seems to be some standard arduino joke, but at least is unique in the network.
@electrik said in Ethernet MQTT Gateway Slow to connect:
I'm not using a wired connection, but had many connection issues also. It took long time before the gateway was up, MQTT connections dropped.
Then I replaced my router (the one delivered by the cable supplier) and I have no issues anymore. So that could be worth a try.
Thanks for the help. I'm on a wired connection. And the network element are of great quality. I think there is a delay in ethernet.connect() but can't find it.
@zboblamont Have in mind the repeater capabilities of mysensors. I have 3 wifi routers in my small house, but no problem at all with nRF24.
In my case a lot of mains powered sensors make coverage very easy.
Is this ok in your installation?
openhab> bundle:list|grep My
191 │ Active │ 80 │ 2.4.0.201812040738 │ MySensors Binding
@jimmy-loyens https://forum.mysensors.org/topic/7176/openhab-2-2-binding
he is usually at that thread. very nice guy.
Lots of info on that thread also.
@jimmy-loyens Sorry man. I'm lost. we should try to contact the author of mysensors-binding.
The only advice that I have right now. What I would do: Delete all mysensors-mqtt config. Delete openhab caches (a very big json file).
Start again very simple.
@jimmy-loyens This binding is a little raw. Perhaps you would like to restart the whole OpenHAB.
Also you should enable more debugging in openhab-cli console. Specificaly to mysensors binding and mqtt.
@jimmy-loyens You have some mosquito/mosquitto mismatch. Have you noticed?
@mooshamee Hardware Raspi
software:
https://www.pyimagesearch.com/2018/09/26/install-opencv-4-on-your-raspberry-pi/
Then as I use MQTT for everything, it is very easy to send states, people count, etc.
@steveg Go with the radio that makes you more comfortable in other aspects.
Sending a single value every (5?) minutes its going to last at least a year on a couple of AAAs on any radio.
I have a test node sending values every second with a couple of AAs and it is going on for a month with 90% of battery still.
I'm using nrf24 and will start with nrf5x at some point in the future.
Regards
I'm doing a dedicated OpenCV Raspberry Pi as a sensor, but my case is detecting people and vehicles.
It's going pretty ok. Buy I don't know if the resolution it's good enough for your scenario.
@jimmy-loyens Hi Jimmy. I'm trying to help, but being a complex issue I'm a little lost.
Have you tried the mysensors+mqtt combo without OpenHAB and it's working ok? I would recommend mycontroller.org as a starting point.
I also recommend mqtt.fx client in order to see the mqtt messages. Try to understand them and if possible send some to your sensors.
If and only if the mysensors+mqtt it's ok, then go to openhab.
In PaperUI you should create a thing for the broker. Have you already? Then after the thing for the broker, you have to create a thing for the gateway. And then if both of them are ok, you can discover your sensors.
Please have a look at some of my screens. I have several brokers because I was also very confused. You only need one.
@mfalkvidd thanks. I just did that on a dedicated post. It's driving me crazy.
https://forum.mysensors.org/topic/10109/ethernet-mqtt-gateway-slow-to-connect
Hi guys.
I'm using an Arduino Uno + 5100 based MQTT Gateway.
It's working great with sensors and mqtt but I have a couple if issues that may be related.
It is very slow to connect to the ethernet switch
won't send registration nor info about local sensors.
Power supply is ok, external regulated 5V + 3v3 reg for nrf. All OK's on the radio front.
Take a look at the startup log:
MCO:BGN:INIT GW,CP=RNNGA---,REL=255,VER=2.3.1
4 TSM:INIT
5 TSF:WUR:MS=0
11 TSM:INIT:TSP OK
13 TSM:INIT:GW MODE
15 TSM:READY:ID=0,PAR=0,DIS=0
17 MCO:REG:NOT NEEDED
580 GWT:TPC:IP=192.168.1.200
1583 MCO:BGN:STP
1585 MCO:BGN:INIT OK,TSP=1
1587 GWT:TPC:IP=192.168.1.200
2590 GWT:RMQ:MQTT RECONNECT
3594 TSM:READY:NWD REQ
3631 TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
3638 TSF:MSG:READ,11-11-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0
3645 GWT:TPC:IP=192.168.1.200
4647 GWT:RMQ:MQTT RECONNECT
5652 TSF:MSG:READ,0-11-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
5657 TSF:MSG:BC
5659 TSF:MSG:READ,2-2-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0
5664 TSF:MSG:READ,0-2-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
5669 TSF:MSG:BC
5671 GWT:TPC:IP=192.168.1.200
6674 GWT:RMQ:MQTT RECONNECT
7678 GWT:TPC:IP=192.168.1.200
8681 GWT:RMQ:MQTT RECONNECT
9687 GWT:TPC:IP=192.168.1.200
10690 GWT:RMQ:MQTT RECONNECT
11695 GWT:TPC:IP=192.168.1.200
12697 GWT:RMQ:MQTT RECONNECT
13702 GWT:TPC:IP=192.168.1.200
14704 GWT:RMQ:MQTT RECONNECT
15710 GWT:TPC:IP=192.168.1.200
16713 GWT:RMQ:MQTT RECONNECT
17717 GWT:TPC:IP=192.168.1.200
18720 GWT:RMQ:MQTT RECONNECT
19725 GWT:TPC:IP=192.168.1.200
20727 GWT:RMQ:MQTT RECONNECT
21733 GWT:TPC:IP=192.168.1.200
22736 GWT:RMQ:MQTT RECONNECT
23741 GWT:TPC:IP=192.168.1.200
24743 GWT:RMQ:MQTT RECONNECT
25749 GWT:TPC:IP=192.168.1.200
26752 GWT:RMQ:MQTT RECONNECT
27758 GWT:TPC:IP=192.168.1.200
28762 GWT:RMQ:MQTT RECONNECT
29767 GWT:TPC:IP=192.168.1.200
30770 GWT:RMQ:MQTT RECONNECT
30777 GWT:RMQ:MQTT CONNECTED
Only then, it starts working ok.
When in that MQTT Reconnect, it is not responding any pings. As soon as it gets the ethernet connection running, it connects to the broker at the first attempt.
It is directly connected to a Cisco switch. I tried everything, auto/auto, 10/full, 100/full. Any ethernet combo it's the same.
This is the complete sketch:
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enables and select radio type (if attached)
#define MY_RADIO_RF24
#define MY_RF24_CHANNEL 110
// modulo con amplificador, por ahi recomiendan bajarle la potencia (?)
#define MY_RF24_PA_LEVEL RF24_PA_LOW
#define MY_GATEWAY_MQTT_CLIENT
// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mysensors-1"
// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
// descomentó guille
//#define MY_W5100_SPI_EN 4
// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif
// When W5100 is connected we have to move CE/CSN pins for NRF radio
#ifndef MY_RF24_CE_PIN
#define MY_RF24_CE_PIN 5
#endif
#ifndef MY_RF24_CS_PIN
#define MY_RF24_CS_PIN 6
#endif
// Enable these if your MQTT broker requires username/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"
// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,1,200
// If using static ip you can define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,1,1
#define MY_IP_SUBNET_ADDRESS 255,255,255,0
// MQTT broker ip address or url. Define one or the other.
//#define MY_CONTROLLER_URL_ADDRESS "m20.cloudmqtt.com"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 1,2
// The MQTT broker port to to open
#define MY_PORT 8884
/*
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300
// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 16 // Error led pin
//#define MY_DEFAULT_RX_LED_PIN 16 // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN 16 // the PCB, on board LED
*/
#include <Ethernet.h>
#include <MySensors.h>
// Temperatura
#include <SPI.h>
#include <DallasTemperature.h>
#include <OneWire.h>
#define COMPARE_TEMP 1 // Send temperature only if changed? 1 = Yes 0 = No
#define ONE_WIRE_BUS 2 // Pin where dallase sensor is connected
#define MAX_ATTACHED_DS18B20 16
OneWire oneWire(ONE_WIRE_BUS); // Setup a oneWire instance to communicate with any OneWire devices (not just Maxim/Dallas temperature ICs)
DallasTemperature sensors(&oneWire); // Pass the oneWire reference to Dallas Temperature.
float lastTemperature[MAX_ATTACHED_DS18B20];
int numSensors=0;
// Initialize temperature message
MyMessage msg(0,V_TEMP);
//
void setup()
{
// Setup locally attached sensors
// temperatura
sensors.setWaitForConversion(false);
}
void presentation()
{
// Present locally attached sensors here
sendSketchInfo("Gateway node with temp", "1.0");
// Fetch the number of attached temperature sensors
numSensors = sensors.getDeviceCount();
present(1, S_TEMP);
}
void loop()
{
// Send locally attached sensors data here
// Fetch temperatures from Dallas sensors
sensors.requestTemperatures();
// query conversion time and sleep until conversion completed
int16_t conversionTime = sensors.millisToWaitForConversion(sensors.getResolution());
// sleep() call can be replaced by wait() call if node need to process incoming messages (or if node is repeater)
wait(conversionTime);
// Read temperatures and send them to controller
for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) {
// Fetch and round temperature to one decimal
float temperature = static_cast<float>(static_cast<int>((getControllerConfig().isMetric?sensors.getTempCByIndex(i):sensors.getTempFByIndex(i)) * 10.)) / 10.;
Serial.println(temperature);
// Only send data if temperature has changed and no error
#if COMPARE_TEMP == 1
if (lastTemperature[i] != temperature && temperature != -127.00 && temperature != 85.00) {
#else
if (temperature != -127.00 && temperature != 85.00) {
#endif
// Send in the new temperature
send(msg.setSensor(i).set(temperature,1));
// Save new temperatures for next compare
lastTemperature[i]=temperature;
}
}
// Estudiar un poco esto. Le pongo algo para que no esté midiendo
// permanentemente
wait(1000);
}
I'm on 2.3.1
The main issue here is the failure to use local sensors, but a faster startup time would also be great.
Thanks in advance for any tip.
Guillermo
Hi guys. I'm using an Arduino Uno+5100 based MQTT gateway. It works fine for it's gateway function but I'm not beeing able to send local sensor data. Is that possible?
@guillermo-schimmel It was bothering me that I was using a 16MHz compiled bootloader for 8MHz Arduino Pro Mini.
So I recompiled the bootloader for all the channels and 1MHz, 8MHz and 16MHz.
I don't know yet if it makes a difference but it seems right.
@jimmy-loyens said in openHAB 2.2 binding:
Hello, I just started to use the mysensors binding 2.2 (moving from serial gateway to ethernet gateway to accomadate MYSController) and I have some (maybe stupid) questions I cant find the answers to (I have been poking around the forum though).
First off, I have a whole bunch of the same type nodes: child0=battery/child1=humidity/child2=temperature/child3=lightintensity/child4-9 are digital inputs for doors and windows. Are such nodes supported by the binding, and how to configure them? I can find temperature, humidity and lightlevel nodes in the list (paperUI) but how can i combine these?Second, can the nodes be automaticly discovered by the binding? In my case i have to add them all manually.
Yes they can. Use the openhab-mysensors-2.4.0-snapshot binding and they will appear.
Third, what are the var1-5 channels for? (is this the answer to my first question?)
Good question. I wonder that myself. When you know it please tell me.
Fourth, what is the difference between the two variable1 channels? in the channel name one says "var1" the other one says "custom"?
Fifth, is there a comprehencive tutorial out there on how to configure the nodes? (I have looked but cant seem to find one)
No there isn't. I think it would be a great idea to write something.
Sixed, when i add any sensor manualy i get a status for it of "UNINITIALIZED - HANDLER_INITIALIZING_ERROR ". The node ID/child ID is online sending data though.
I resolved a lot of those messages by restarting the complete OpenHAB. Not cool, but works.
am i using the latest stable version of the binding? I downloaded it a few weeks ago from eclipse market.
Use this:
http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.4.0-SNAPSHOT.jar
Any help would be appreciated
@jimmy-loyens said in MYSController:
@guillermo-schimmel can you tell me where you downloaded the binding? I think im using the 2.2 binding. Is it possible you forgot the link to your setup files? Greets
Please take a look here:
https://www.mysensors.org/controller/openhab
You will find my config and also a link to the 2.4 version of the binding.
@jimmy-loyens I use the openHAB-mysensors 2.3 binding.
But if you are unsure your mysensors setup works, it’s reasonable to start with mqtt binding and then migrate. Lots of moving parts.
I have posted here my own files for your reference.
@jimmy-loyens You have to build an mqtt gateway. On the hardware side it is identical to the ethernet gateway.
There is another sketch for it though:
https://www.mysensors.org/build/mqtt_gateway
It is very easy.
Please let me know it if works. I really like the openhab+mqtt+mysensors combination, I think that eventually there will be a lot of us here.
@sindrome73 here you have bootloaders for all the channels.
https://github.com/guillebot/MYSensors-Bootloaders
They are unchanged from default elsewhere. Only RF CHANNEL.
@jimmy-loyens said in MYSController:
@guillermo-schimmel thanks, seems i have an ethernet shiel + spare uno lying around. I will give it a go.
Same setup here.
Is the mysensors binding compattible with custom nodes i written my own code for? Wich metod is less work to reprogram my openhab? I'm asking because my openhab is quite elaborate. I have a few 100 items and about 80 mylight sensors plugged in to openhab
right now (serial gateway) they all enter openhab via 1 rule with a large hashmap.
Yes, it supports custom nodes.
If i understand correctly i have to create a thing for each sensor and link each item to the channel of this thing. Got a lot of work to do
Yes, but if you do it in text files it's not that bad.
@jimbolaya said in MYSController for RPi?:
@guillermo-schimmel Is the same true for serial gateway?
I don't know, but don't think so. It would be difficult for more than one program to take control of the serial port.
@guillermo-schimmel Here you have some openhab+mqtt+mysensors examples
@jimmy-loyens Yes the mqtt gateway is very simple, just use some arduino+nrf4+ethernet.
There is a simple sketch for that.
In order to connect to openhab you should use openhab 2.4 and the mysensors (unofficial) binding. If you are on an older openhab you can just use the mqtt 1.x binding.
I did a post a few weeks ago. I'll try to find it for you.
@sindrome73 You have to use the Make tool, which is going to call the avr-gcc compiler.
Have you ever compiled something using command line tools?
If you don't know what I'm talking about, just tell me your channel and I can compile a bootloader for you.
@sindrome73 You have to recompile the bootloader.
It's easier than it seems.
https://github.com/mysensors/MySensorsBootloaderRF24
#define RF24_CHANNEL (76) // RF channel for the sensor net, 0-127; default 76
Probably it's going to need all the set of avr devel tools. Install them according to your distribution instructions.
I can confirm that I did this and it's working great.
@jimbolaya if you use mqtt gateway you don't even need to stop one controller. You can use them all (if they support mqtt).
I'm doing OpenHAB+Mycontroller.org+several local scripts.
@jimmy-loyens What I do in order to have multiple controllers is to make a ethernet-mqtt gateway on an Arduino Uno.
That way I can use OpenHAB, try other controllers and also use mycontroller.org to do node management and FOTA.
I think that there is no other way.
@mfalkvidd said in FOTA (Wireless Programming):
- Yes. Isn't that exactly what you did when you did this: "I can confirm that is indeed working by recompiling to my channel" ?
Definitely yes. And it worked. I meant a non-compiling way, like set some eeprom variable.
- I don't know. But I would also guess eeprom.
- The bootloader needs to fit into a very small size, so I am not sure if there is room to read the channel from eeprom.
Maybe @scalz can comment on 2 and 3.
Please @scalz should you have a little room, this would be a very nice feature to have.
Thank you both guys.
Regards
@jimbolaya It can upload firmware. I'm just doing the same as you. I run a very small virtual machine just for administration of nodes and firmware.
@mfalkvidd Thank you as usual.
I can confirm that is indeed working by recompiling to my channel.
I have however a couple of questions.
When you say "by default", do that means that there is a way of modify that default? If so, how?
This specific node that I'm testing with, have a fixed node id (I use OpenHAB). But with the recompiled bootloader it "knows" which firmware download. Where does it gets from? Is the bootloader accessing the main sketch? Or is the node id info fixed in eeprom.
If the node id info is in eeprom, could we also have the channel there? It would be so great not having to compile the bootloader.
Thanks a lot, as allways.
I recompiled MYSBootloader 1.3 with the RF Channel I use and it's now working. I can confirm that FOTA works great over MQTT gateway.
Hi there. For what I'm reading, the MYSBootloader allways uses the default channel 76. Is that correct? It would be a very important addition to this howto.
@guillermo-schimmel Combining mic with temperature would also work. Mic for breath, temp for direction. There are some temperature modules very responsive.
@absolem I would try the audio way.
A microphone near the mouth place could detect very different sounds.
I dunno if the usual mic modules do that or you would need to manually make a circuit with two bandpass filters in order to get the 3 states. (nothing, in, out)
@guillermo-schimmel said in
It looks that I was using 1.a, as this is how I already have items defined from before, f.eks.
Number Temp_03 "Temperatura [%.1f °C]" {mqtt="<[mosquito:mygateway1-out/3/1/1/0/0:state:default]"}but I do agree, this is a bit... time consuming to figure out which value should be sent when.
To migrate from this to 1.b, I would have to define every channel in the things file?
Yes, like this:
Thing mqtt:topic:miscosas {
Channels:
Type number : ecovacs_1_battery_level "Ecovacs 01 Battery Level" [ stateTopic="ecovacs/E0000693817701104736/battery_level" ]
Type string : ecovacs_1_charge_status "Ecovacs 01 Charge Status" [ stateTopic="ecovacs/E0000693817701104736/charge_status" ]
Or via Paper UI, which is slower and painful.
I am not a fan of PaperUi , and would like to have a official bindings when possible. It is always annoying to update openhab, and I would like to keep it as less complicated as possible.
Do you have an example (or give some tips) on how to go with 1.b route, either via PaperUi, or things file? What do I write there for one, f.eks. temperature-humidity sensor?
The "1.b" is just like I said. Define your .things and then is identical to the 2. From things you go to items and then sitemap.
I like having good control over each node, so defining each channel should be fine for me, I am just struggling to get started, then I can copy-paste from there
There you have an example, which I actually use with and old mysensor node which I modifyed (bad)
a. Things:
Thing mqtt:topic:miscosas {
Channels:
Type string : porton_a_mano "Garage Porton a Mano" [ stateTopic="mygateway1-out/11/3/1/0/16" ]
}
b. Items
String item_porton_a_mano "porton a mano" { channel="mqtt:topic:miscosas:porton_a_mano"}
c. Sitemap
Frame label="Garage" {
Default item=item_porton_a_mano icon="garagedoor" valuecolor=[CLOSED="green",OPEN="red" ]
}
Thanks!
@dakipro Well let me try to clarify that, because I have been there.
Once you went the MQTT way (same as I did), you have two methods for connecting OpenHAB to the MySensors network.
MQTT Binding
Here you have sadly two flavors
1.a.) Old mqtt 1.0 binding
1.b.) New mqtt 2.x binding
MySensors Binding
The 1.a. route: MQTT using old MQTT 1.0 binding
If you go the 1.a route. You can manage without using Paper UI. I did that, and it worked pretty good. The downside? You don't have integration with Paper UI, and you have to discover every mqtt topic by hand. You end with things like *mysensors1-out/10/23/0/0/3/17
You should try to avoid that route, but do know that it works.
The 1.b. route: MQTT using new MQTT 2.x binding
The 1.b route. It also works fine, you define the broker via Paper UI and/or files, and you then define every channel by hand, the easier way is via PaperUI.
This is awful.
The 2.x route:
And finally in order to be on the bleeding edge, you can have the new mqtt 2.x binding for other stuff, but for MySensors please install the mysensors-binding. Unfortunately is not official but you can find it here in the forums.
It works great. You define the broker via PaperUI or files, then you define the mqtt gateway thing and then magic, autodiscover of mysensors nodes and sensors.
Once they are discovered you can browse them on the Paper UI and then use them either via Paper UI or files (take a look at my examples).
This is the binding. It doesn't have much documentation but there is some, please look for it, I can't seem to find it now. You have to enter the openhab cli in order to activate it.
http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.4.0-SNAPSHOT.jar
Item files for each mode:
1.a)
Number tanque_distanciaalagua "Distancia [%.0f cm]" <length> {mqtt="<[mosquitto:mygateway1-out/10/1/1/0/13:state:default]", expire="5m"}
1.b)
Number tanque_distanciaalagua "Distancia [%.0f cm]" <length> { channel="mqtt:topic:efe295fe:tanque_distancia", expire="5m"}
Number tanque_distanciaalagua "Distancia [%.0f cm]" <length> { channel="mysensors:distance:gateway2:distance_10_1:distance", expire="5m"}
Hope this makes some sense. Do not hesitate in writing me.
Regards and happy OpenHAB'in.
Guille
Hi @hek, can I send you some images in order to update the very old that are showing here?
@dakipro I have still to write a decent tutorial but if you follow the docs for mysensors binding is pretty straightforward.
What I can do is show you some of my files:
Bridge mysensors:bridge-mqtt:gateway2 [ brokerName="mosquitto", topicPublish="mygateway1-in", topicSubscribe="mygateway1-out", startupCheckEnabled=false ]
Rollershutter Persiana24 "Persiana escritorio [%d %%]" (PERSIANAS) { channel="mysensors:cover:gateway2:cover_12_1:cover" }
cover_12_1 is the channel name, you have to look at that in the Paper UI.
Frame label=Persianas {
Slider item=Persiana24 icon="rollershutter"
Switch item=Persiana24
Switch item=Persiana24 icon="rollershutter" mappings=[0="Abierta", 10="10%", 25="25%", 50="50%", 90="90%", 100="Cerrada"]
}
This is all working.
@timo Thank you very much. I don't now how to use the marketplace, will research right now.
I have followed your instructions, but you link to the 2.3.0-SNAPSHOT. Perhaps you would like to correct that.
Thanks again
@fredswed Yes I'm testing that now. I think it's working. Auto discovery is nice.
@masmat Yes!!!! Thank you man. I found 2.4.0 thanks to your message and now it's working!
Love
@fredswed As far as I know, there isn't a better way. A thing is indeed a phisycal object, and a node groups several of them. 
Can I ask you which kind of connection/gateway are you using? I'm strugling with the mqtt gateway and the binding.
Thanks
@timo Re: openHAB 2.2 binding MQTT support
Hi @TimO. I'm lost. Should I install
http://www.oberfoell.com/openhab2/org.openhab.binding.mysensors-2.2.0-mqtt.jar
or the 2.3.0-SNAPSHOT?
I'm using mqtt gateway.
It doesn't seem to startup with either one.
Thanks!
@guillermo-schimmel Hi there, it's me again. Do you still need to remove the other standard mqtt binding for this to work?
I'm getting HANDLER_INITIALIZING_ERROR.
Thanks
@leitefrog Hi there. Hold on.
I'm testing two variants:
openhab-mysensors binding. This is non-official but will try it today to see what happens. Looks promising.
New mqtt binding. It's working already. You have to use the paper UI. First create the mqtt broker "thing" and then manually one channel for every mysensors variable. And then on the items definitions (files), the format changes:
//Number tanque_temperatura "Temperatura [%.1f °C]" <temperature> {mqtt="<[mosquitto:mygateway1-out/10/2/1/0/0:state:default]", expire="5m"}
Number tanque_temperatura "Temperatura [%.1f °C]" <temperature> { channel="mqtt:topic:efe295fe:tanque_temperatura", expire="5m"}
After my tests today with (1) I will try to write about my experiences.
@mfalkvidd Thanks! Just give me a couple of days and I will try to make a new tutorial for mysensors+openhab.
@davidgraeff Yes David, you are correct. The new binding works. I'm in fact using it and with the corresponding changes on the items files its ok.
I would love some kind of auto discovery though. In order to create each thing you have to manually enter the topic (which on mysensors is very complex)
Anyways, I will try to edit previous message which is in fact wrong.
@timo Hi! Do you plan to continue the development into openhab 2.4?
Hello guys, who can unpin this post?
It is terribly outdated.
The effort for an openhab-mysensors binding is still valid but several things changed on OpenHAB, making this a lot easier.
Hi guys, several updates on the OpenHAB front, being MQTT one of the biggest. Where can I update some of this outdated info?
I highly recommend OpenHAB for mysensors, but for what you read here is not so tempting 
regards
@mfalkvidd that's really great. I'll try. Thank you very much.
Hi @mfalkvidd, and thanks for you time.
I see that there is already a mechanism for altering the node id on runtime.
What I would like to know is if there is something similar to change the RF Channel (and/or) RF Power, also on runtime.
Something in the likes of transportAssignNodeID(), perhaps transportAssignRFChannel().
regards
I would definitely welcome that improvement.
I think that a desired method would be a default via #defines, and some way to overide that programatically.
To what channel we move? I think that some kind of physical input, even taking some pins, would be great. We could "encode" 2^n inputs in order to change the channel from default. Or for more advanced use cases we could change it via a sensor variable for OTA frecuency setting.
Thanks to you all
@grumpazoid I would check on the contacts. 1V drop with the very low current draw of these components can only be
a) depleted battery
b) defective booster
c) poor contact somewhere.
Try to change the pins that you use on the protoboard, or check the solder joints.
Can you attach some schematics?
Just for you to know, I just updated to 2.4 and can confirm that with the new mqtt binding I can connect with mysensors.
You have to create the MQTT Broker think via the web ui and then each thing, finally you have to modify your items, like this:
//Contact GaragePorton "Portón Garage [%s]" <garagedoor> { mqtt="<[mosquitto:mygateway1-out/11/3/1/0/16:state:default]" }
//Contact GaragePuerta "Puerta Garage [%s]" <door> { mqtt="<[mosquitto:mygateway1-out/11/4/1/0/16:state:default]" }
Contact GaragePorton "Portón Garage [%s]" <garagedoor> { channel="mqtt:topic:efe295fe:porton_garage" }
Contact GaragePuerta "Puerta Garage [%s]" <door> { channel="mqtt:topic:efe295fe:puerta_garage" }
@martim I would recommend you to use plain mqtt.
Don't use the binding or the bridge stuff. Once you have the mysensors-mqtt, use plain mqtt items on your openhab config and it will work great.
I already have several sensors this way.
Perhaps after openhab 2.4 I will play a little with the binding and then I could be more useful to you.
@martim Don't use the binding! Use plain MQTT.
I'd love to have a simple working binding but it isn't there yet. Use plain mqtt elements and it'll work great.
The new mqtt binding works. I don't like the mechanism needed to configure the broker, and then each thing, but works, and it is in fact more integrated with openhab than ever.
If you have any questions do not hesitate to contact me.