Distance 10cm 
BUt the second hint was useful. There seemed to be something "broken"/agile/in development yesterday which was fixed today. As far as I remember this was a fresh merge from development but nevertheless: now it is working again thanks 4 the hint.
Greetings
Dakky
Hello
I used the develop branch quite a while and everthing was fine.
But now i can't get the communication up between controller and node. I didn't change something on the hardware side, so I think there is an error on the software part.
This is what I can see on the node:
Starting sensor (RNNNA-, 2.0.0-beta)
TSM:INIT
RADIO:OK
assign node ID=1
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
node 0 replied, d=0, _nc.distance=255
parent=0, d=1
TSM:ID
node ID=1
pinging node 0
send: 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,st=ok:1
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
!TSM:FAILURE
TSM:PDT
TSM:INIT
RADIO:OK
assign node ID=1
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
node 0 replied, d=0, _nc.distance=255
parent=0, d=1
TSM:ID
node ID=1
pinging node 0
send: 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,st=ok:1
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
read: 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
node 0 replied, d=0, _nc.distance=255
parent=0, d=1
TSM:ID
node ID=1
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
TSM:PARENT
send: 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
!TSM:FAILURE
TSM:PDT
On the gateway side i can see:
0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
IP: 192.168.100.10
0;255;3;0;9;TSM:INIT
0;255;3;0;9;RADIO:OK
0;255;3;0;9;TSM:GW MODE
0;255;3;0;9;TSM:OK
0;255;3;0;9;No registration required
0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-0 s=255,c=3,t=24,pt=1,l=1,sg=0:1
0;255;3;0;9;node pinged by 1, hops=1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=25,pt=1,l=1,sg=0,st=fail:1
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=ok:0
0;255;3;0;9;read: 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
0;255;3;0;9;MSG:BC
0;255;3;0;9;FPREQ from 1
0;255;3;0;9;GWL ok, FPRES to 1
0;255;3;0;9;send: 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
Any idea whats wrong here? is there a place, where I can read about the "new" output format/messages?
EDIT: I don't even come the the setup() part of my sketch. the node is looping around with the log messages above.
@mfalkvidd said:
- Yes you can use analog input as digital input if you like (but not as output). A5, A6 and A7 don't have internal pullups though so you might need to solder external pullups. EDIT: The distance sensor doesn't need pullups so you don't need to add any in this case. However, the TRIG signal to the HC-SR04 needs to be an output pin so you can't move that. You can move the moisture sensors, if you add external pullups (or buy sensors with built-in pullups).
Ok sounds reasonable. Have to read more about that pullup/pulldown thing
- There is no way you can power everything through the voltage regulator on the Pro Mini. The absolute maximum total power rating for the Pro Mini is 150mA when powering through raw. Also note that most Arduino clones do not survive 12V raw input, and that the nrf radio needs approximately 3.3V.
Ok I'll use one LM2596 in order to power all components directly + another 5V=>3V voltage regulator for the radio. This should work 
- The relays are controlled by the output pins on the Arduino. The relays control power (12V in your case) that is coming from elsewhere. Relays often consume quite a lot of power (from the Arduino) when switching so make sure you add capacitors. You could also consider using FETs instead of relays. We've seen many threads on relay problems that were caused by power issues.
Is that a problem too, when powering the relay directly from the LM2596? Otherwise i have to learn something about FETs 
- Probably
So true the problem is the "lost" time when waiting for another china package 
An alternative to getting 8 pumps is to get 1 pump and 8 valves. That will probably be cheaper.
Hmm I did not find any cheap valves. One of the pumps is about $6. And valves cause one problem imho: they need pressure in order to work and this requires to activate the pump some seconds bevor triggering the valve => increased complexity
@dbemowsk said:
Are you aware of this project that is in the build section of the site?
https://www.mysensors.org/build/irrigation
I saw this one, but it's more a "standalone" solution imho. quite complex. I wanted just a stupid "tell me the moisture values and switch a relay"-solution
@rest:
hmm interesting. I will read something about these components, although I'm a little bit afraid of the required code changes 
Hello again
I'm planning to water some of my plants with a quite simple setup.
Basically I want to use a pro mini with a nrf module and a moisture sensor and pump per plant.
This leads me to the following "wiring" (sry for the humble presentation )
The arduino clone has a strange pin layout, but thats not the problem at the moment.
Basically a want to know: will this hardware setup work?
Some hard facts:
There are some "problems" IMHO:
even when i use D2 as output/relay and not as IRQ for the radio i only have 5 pins for switching the pumps/relays. On the opposite side I can have 8 moisture sensors 
Or can i use analog pins as digital INPUT? Then i'd move the distance sensor to A5/A6 which results in 7 relay control pins and 6 moisture sensors => 6 plants instead of 5.I know there are some "ready2use" irrigation setups, but i want to keep it as simple as possible and want all the logic on the controller side (except some "emergency stop mechanisms )
I'm using a ethernet gateway.
the problem is: if the sensors gateway gets restarted/disconnected/updated/whatever the binding does not reconnect. The only way to fix that, is to restart openhab in order to force the binding to connect again.
Detecting an disconnect is really that hard? in the worst case, what about simply reconnecting timebased? not as cute as only reconnect when nessecary but a dirty quickfix.
@TimO do you plan to implement the reconnect thing? I often have to struggle with that and the only solution is the restart the openhab service :S Is there a problem with the reconnect or is it just "another task on the todo list"?
Greetings
Dakky
Ah that explains it for me. Thanks for the dettailed answer. I will @mfalkvidd's and switch the defines. thank you all
Greetings
The title says it all: I have connected a relay to my network and it switches power on (led on the relay lights up), when the input pin goes low and vice versa.
Thats a little bit confusing, when switching off something in the controller UI and the device is switching on and i don't think, that zwitching the state in the arduino code is the way to go
any idea whats wrong here? Wiring is straight forward (vcc & gnd with corresponding pins on relay + D2 to I1 on the relay).
The code is the the one from the examples (as far as I remember ).
I inserted some debug statements to prevent stupid errors on my side
Serial.print("arduino pin: ");
Serial.println(message.sensor + FIRST_DIGITAL_RELAY_OUTPUT);
Serial.print("message.bool: ");
Serial.println(message.getBool());
digitalWrite(message.sensor + FIRST_DIGITAL_RELAY_OUTPUT, message.getBool() ? RELAY_ON : RELAY_OFF);
=>
arduino pin: 2
message.bool: 1
results in switched off relay.
Thanks for helping
EDIT: maybe "hardware" is the wrong section and "Troubleshooting" a better location If thats the case: please move the thread if possible
Dammit ... found the error
created a pull request: https://github.com/tobof/openhab2-addons/pull/18
Greetings
Dakky
@dakky said:
I think i need some help. I am not shure, if my problem lies on the openHab2 side or if there is a problem with the mysensors addon.
No idea anyone? i'm stucked here and I'd really like to continue
EDIT: MAybe this helps debugging: it seem there is no "link" between things and items. The rest endpoints reveals, that the thing has no item:
[
{
"statusInfo": {
"status": "ONLINE",
"statusDetail": "NONE"
},
"link": "http://autohome:8080/rest/things/mysensors:bridge-eth:gateway",
"configuration": {
"tcpPort": 5003,
"ipAddress": "192.168.100.10",
"skipStartupCheck": false,
"imperial": false,
"sendDelay": 200
},
"properties": {},
"UID": "mysensors:bridge-eth:gateway",
"channels": [
{
"linkedItems": [],
"id": "n1c0",
"itemType": "light",
"properties": {}
},
{
"linkedItems": [],
"id": "n1c1",
"itemType": "light",
"properties": {}
},
{
"linkedItems": [],
"id": "n1c2",
"itemType": "humidity",
"properties": {}
},
{
"linkedItems": [],
"id": "n1c3",
"itemType": "humidity",
"properties": {}
},
{
"linkedItems": [],
"id": "n1c4",
"itemType": "humidity",
"properties": {}
}
]
}
]
Greetings
I think i need some help. I am not shure, if my problem lies on the openHab2 side or if there is a problem with the mysensors addon.
This is what i I have:
A working mysensors addon. I receive updates in OpenHab:
2016-06-06 07:12:08.483 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTING - org.openhab.binding.mysensors
2016-06-06 07:12:08.550 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.mysensors.internal.MySensorsHandlerFactory, component.id=7, service.id=102, service.bundleid=11, service.scope=bundle} - org.openhab.binding.mysensors
2016-06-06 07:12:09.070 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTED - org.openhab.binding.mysensors
2016-06-06 07:12:12.062 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2016-06-06 07:12:18.694 [ERROR] [org.openhab.ui.habmin ] - [org.openhab.ui.habmin.designer(3)] bind method [setItemRegistry] not found; Component will fail
2016-06-06 07:12:18.702 [ERROR] [org.openhab.ui.habmin ] - [org.openhab.ui.habmin.designer(3)] bind method [setItemRegistry] not found
2016-06-06 07:12:25.252 [ERROR] [org.eclipse.smarthome.core.transform] - [org.eclipse.smarthome.action.transformation.action(51)] Circular reference detected, getService returning null
2016-06-06 07:12:39.288 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_light_gateway_Light_1_0-mysensors:light:gateway:Light_1_0' has been added.
2016-06-06 07:12:39.315 [INFO ] [smarthome.event.ItemAddedEvent ] - Item 'home_group_88a3d2a1' has been added.
2016-06-06 07:12:42.030 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /ui
2016-06-06 07:12:42.261 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2016-06-06 07:12:42.825 [WARN ] [sql.internal.MysqlPersistenceService] - The SQL user is missing - please configure the sql:user parameter in openhab.cfg
2016-06-06 07:12:43.071 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2016-06-06 07:12:43.114 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2016-06-06 07:12:43.470 [INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been started (v2.0.0, build b2).
2016-06-06 07:12:43.479 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.sitemap'
2016-06-06 07:12:44.159 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.things'
2016-06-06 07:12:44.397 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing 'mysensors:bridge-eth:gateway' has been added.
2016-06-06 07:12:44.468 [INFO ] [nsors.handler.MySensorsBridgeHandler] - Using Metric measure unit
2016-06-06 07:12:44.470 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Set skip check on startup to: false
2016-06-06 07:12:44.489 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=278, service.bundleid=11, service.scope=singleton} - org.openhab.binding.mysensors
2016-06-06 07:12:44.527 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors Bridge
2016-06-06 07:12:44.531 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:gateway' changed from UNINITIALIZED to INITIALIZING
2016-06-06 07:12:44.540 [DEBUG] [rs.protocol.ip.MySensorsIpConnection] - Connecting to bridge ...
2016-06-06 07:12:44.762 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
2016-06-06 07:12:44.770 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete.
2016-06-06 07:12:44.776 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;11;EthernetGateway
2016-06-06 07:12:44.778 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;12;1.0
2016-06-06 07:12:44.849 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;2;2.0.0-beta
2016-06-06 07:12:44.852 [DEBUG] [s.internal.MySensorsBridgeConnection] - Good,Gateway is up and running! (Ver:2.0.0-beta)
2016-06-06 07:12:44.858 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=mysensors:bridge-eth, thing.id=mysensors:bridge-eth:gateway, service.id=279, service.bundleid=11, service.scope=singleton} - org.openhab.binding.mysensors
2016-06-06 07:12:44.859 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-eth:gateway' changed from INITIALIZING to ONLINE
2016-06-06 07:12:44.900 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'logging.persist'
2016-06-06 07:12:44.990 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rrd4j.persist'
2016-06-06 07:12:45.047 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.items'
2016-06-06 07:12:45.168 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c0-mysensors:light:gateway:n1c0:status' has been added.
2016-06-06 07:12:45.171 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c1-mysensors:light:gateway:n1c1:status' has been added.
2016-06-06 07:12:45.174 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c2-mysensors:humidity:gateway:n1c2:hum' has been added.
2016-06-06 07:12:45.178 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c3-mysensors:humidity:gateway:n1c3:hum' has been added.
2016-06-06 07:12:45.182 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c4-mysensors:humidity:gateway:n1c4:hum' has been added.
2016-06-06 07:14:50.818 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1
2016-06-06 07:14:50.820 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
2016-06-06 07:14:55.831 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0
2016-06-06 07:14:55.832 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
2016-06-06 07:28:01.373 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1
2016-06-06 07:28:01.375 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
2016-06-06 07:28:06.385 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0
2016-06-06 07:28:06.387 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
2016-06-06 07:32:21.567 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;1
2016-06-06 07:32:21.568 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
2016-06-06 07:32:26.578 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 1;3;1;1;1;0
2016-06-06 07:32:26.582 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - ACK received!
Seems ok.
But I am not able to see the result in Openhab
my.thing:
mysensors:bridge-eth:gateway [ ipAddress="192.168.100.10", tcpPort=5003, sendDelay=200 ] {
/** define things connected to that bridge here */
light n1c0 [ nodeId="1", childId="0", requestAck=true ]
light n1c1 [ nodeId="1", childId="1", requestAck=true ]
humidity n1c2 [ nodeId="1", childId="2" ]
humidity n1c3 [ nodeId="1", childId="3" ]
humidity n1c4 [ nodeId="1", childId="4" ]
}
my.item:
Switch n1c0 "PFLANZENNAME1 Pumpe" <water> (gGF_irrigation01) { channel="mysensors:light:gateway:n1c0:status" }
Switch n1c1 "PFLANZENNAME1 Pumpe Automatikmodus" <water> (gGF_irrigation01) { channel="mysensors:light:gateway:n1c1:status" }
Number n1c2 "PFLANZENNAME1 Bodenfeuchtigkeit max" <water> (gGF_irrigation01) { channel="mysensors:humidity:gateway:n1c2:hum" }
Number n1c3 "PFLANZENNAME1 Bodenfeuchtigkeit min" <water> (gGF_irrigation01) { channel="mysensors:humidity:gateway:n1c3:hum" }
Number n1c4 "PFLANZENNAME1 Bodenfeuchtigkeit" <water> (gGF_irrigation01,gGF_eating) { channel="mysensors:humidity:gateway:n1c4:hum" }
There are simply no values in openhab although I see the debug messages in the openhab log.
Any idea how to fix it? I did not use the autodicovery of openhab paper UI. what confuses me is the name of the link used by openhab:
2016-06-06 07:12:45.168 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link 'n1c0-mysensors:light:gateway:n1c0:status' has been added.
That does not match the channel. is that ok?
Thank
Dakky
EDIT: updated openhab log to complete startup process and added question
Hello
Ich want to implement a gardening node and found this project:
http://iot-playground.com/blog/2-uncategorised/61-nrf24l01-arduino-balcony-irrigation-controller
I think i am able to adopt this for my setup without the solar power part.
There are still some question on the hardware-side:
Anything i should think about?
thank
Dakky
Hmm simply sleeping for 30secs after sending a bell message is not enough? the other sensors did not seem to be timing critical?#
EDIT: a i see you need the repeating capabilities. so sleeping might be a problem. then u need to calculate a time diff
kewl, thank 4 digging this up. I'm just evaluating openHab2
does the sleeping current come down to an acceptable level when removing the regulator? 1500uA is quite much for a battery powered node.
do u add these photos and comments to openhardware.io ? they are quite helpful
Arghls no DHT11 with this node? Dammit. But a step up converter should do it?
Thanks 4 all the input!
I thought about measuring only, but powering the node is a possibility i nearly ignores. Stupid me 
This intercom has a regulated 18v DC power source. So i should be fine.
Hello
i'm looking for a 18V => 5V (dc/dc) and vice versa converter. Someone can give me a hint, where to look for a suitable solution?
Background: Our intercom (doorbell/opener) is running in 18V, which would kill my arduino input (bell) and output pins
Typing from tablet => short Version
Contact items needs Open or Closed not On vor Off. Make a new map translating 0 to closed etc and it should work. or use the correct item: switch seems a better choice
https://github.com/openhab/openhab/wiki/Explanation-of-items#itemtype
nice idea. this obsoletes about 50% of my mysenors related bookmarks
hmm have some questions too:
there is only one gateway in your network.
you should proceed the following way:
this will probably not work: domoticz is waiting for mqtt messages not matching the mqtt messages delivered by mysensors. When using domotitz ethernet or serial gateway is preferable
signing seems to be fine thanks 4 info
yep i love it, when i can get some inspirations from him. It's one of my greatest problems, howto hide all the stuff i assemble. Here is howto to do it
Thanks!
openhab does not manage the IDs. it's simply not implemented on the openhab side
that's the way i'm using it now. Deftault ethernetGW + additional "datasource" for the mqtt messages. It's a bit tricky to find documentation about the mqtt messages domoticz is expecting. But basically it's working.
of course u're right. was a little brainf*ck
soldering or not does not change anything as long as the parts are fixed.
did you change the caps? I had massive problem with 4,7nF Caps at my gateway: random fails when transmitting. I now use 100nF and 4,7nF at the gateway and it works like a charm
hmm this helped ... i think oO did a lot of stuff and suddenly iw works 
really strange
Thanks
As soon as i hardcode a node ID in my sketch, i can see everthing as usual in die serials (node reporting values, arriving on gateway, signing ok etc)
As soon as i set a AUTO id, nothing works, because i get no node id from domoticz
Hello again
I'm trying to go with the EthernetGateway and a w5100 ethernetshield.
I am not sure, if the ethernet part is working.
why?
the nodes can find the GW, at least in the gw serial monitor i can see them polling for an ID
Log:
0;255;3;0;9;Starting gateway (RNNGAS, 1.6.0-beta)
0;255;3;0;9;Radio init successful.
IP: 192.168.100.10
0;255;3;0;9;Init complete, id=0, parent=0, distance=0
Any Idea?
Contact contact_99 "Contact node 99 sensor 3: [MAP(de.map):%s]" { mqtt="<[mysensors:sensor-gw1-out/99/3/1/0/16:state:MAP(mqttToCloseOpen.map)]" }
this is an item which
reads a message from mqtt broker:
I found it very helpful to subscribe myself to the mqtt broker and read the incoming messages there
hmm i've seen that, but i'd prefer the mqtt way: I have some scripts measuring some stuff besides my mySensors network. And these scripts just send simple mqtt messages to the external broker and are consumed by openHab
EDIT: Hmm ... this mqtt topic causes quite some trouble .. maybe i should rethink this and use the more "conservative" way with the ethernetgateway
I'm still struggling with myself wether to switch from openhab to domoticz.
So i want to use my "old" infrastructure for testing purposes.
setting up domoticz itself was an easy task. But now i don't know how to continue.
The domo documentation concerning mqtt is something near to non existent
So i think the following has to be done:
configuring mqtt broker in domo
i think i did that (settings => hardware => mqtt ethernet)
convert mysensors serial API messages to domo readable json messages
uh .. quite hard imho? node red magic?
example (freestyle, nonvalid :D)
incomging message:
mysensors-gw-out/12/6/1/0/0/36.5 => domoticz/in/{ "idx" : 12, "nvalue" : 0, "svalue" : "36.6"}
quite confusing ...
yep thats what i meant. more or less complex if sensor X then trigger actuator Y and actuator Z.
I will read your links. Thanks!
Hello
simple question:
i'm trying to decide wether to go with openhab or domoticz.
When trying to compare them, i stumbled over the rules:
in opebhab they are configures within openhab. in domoticz I didn't find something like rules. Does this mean, i have to use node red as rule engine?
Greetings @sundberg84
I'm looking for a "non-in-wall" solution to power an pro mini / bare atmega.
At the moment i want to build a simple button-relay. Of course i could by any phone charger, but they cost about +- 10€. And i don't have soo many spare chargers lying around at home
The size is important for me, because my wife would kill me, if i put medium sized packages near everthing i want to switch on/off
i'm already following the thread u mentioned, but i have to admin: my understanding in these topics is not very deep
This one look fine?
Any guess concerning the safety?
Hello
can you recommend a power supply for powering actuator nodes?
Should be
Any hints?
I did not use wlan module (see my signature), but should be the same + wlan settings.
And, of course, setup an external mqtt broker. I used mosquitto, simple apt-get get foo on the openhab host.
@hek posted a howto:
http://forum.mysensors.org/topic/2352/guide-setting-up-and-testing-mqtt-client-gateway
intresting approach any more (maybe more "conventional") ideas? 
http://www.mysensors.org/controller/openhab
OpenHab support only Serial GW or mqtt. So this leaves you to 3 options:
I personally prefer option 3:
uh my fault. The DigitalIO lib is in located in the AVR folder in the development branch only. In the master (1.5 release) its located in the libraries folder: libraries/DigitalIO/DigitalIO.h
seems u don't have extracted the mysensors lib correctly.
DigitalIO.h is included in the bundle. have a look, if u have ./MySensors/drivers/AVR/DigitalIO/DigitalIO.h
Anyone want to share some photos with sensors assembled?
Any experiences how long this node will last? I have one DHT11 and one BH1750 onboard and will wake up the node every 5-15 Minutes.
Greetings
Dakky
Hello
I'm planning to build a sensor with BH1750 light sensor.
I need some inspiration, how to build the housing for this one. Anyone has an idea/example? I can't image where to place the light sensor, without leaving it unprotected outside of the housing.
thanks
Dakky
@sundberg84 said:
I primary use 4,7uF and are tested higher and two caps paralell on my gateway atm.
I can ACK this:
On the Gateway i need 2 caps: 100uF and 4.7uF. without the 100uF cap I had some really strange behavior when starting the gateway until the communication got established same (random) times
At the nodes 4.7uF is sufficent.
yep, i'm afraid that's the way to go. Thanks for ACK
hello
i'm planning the following setup:
SameSame merry xmas and thank you all for the great work
yep, exactly
edit: have a look in the development branch of mysensors. There is a w5100Clientgateway example. I simply changed the pins for the mega and thats it.
and how to you want to transmit any data from the nodes to your network? Wired? cables everywhere? wlan? no low power/battery + expensive in relation to the cheap nrf modules.
my gateway is conencted to the RPI via w5100 ethernet shield. My mqtt broker is mosquitto. simply and functional
ok i think this can be regarded as solved: have tested very many on/of roundtrips and with an 100nf and an additional 4,7nf cap it's rocking stable. Maybe this would be worth a sidenote here: http://www.mysensors.org/build/connect_radio
you mean, no nrf module? whats the sense in using the mysensors lib? thats the "main" task (imho): creating a sensor mesh via the nrf module and channeling everthing via the gateway?
@drock1985 said:
command_topic: "mygateway1-in/2/255/3/0/3"
This does not look korrekt.
The serial API says:
node-id;child-sensor-id;message-type;ack;sub-type;payload\n
so you are trying to send something to node 2, sensor 255. That does not work. Your skeetch is numbering the child from 1 to NUM_RELAYS
so i think something like
command_topic: "mygateway1-in/2/1/3/0/3"
should to... But that's my theoretical knowledge haven't build a relay yet
hurm did i switch them?
Concerning the method: hmm ok. I just thought, that the one recommenced in the build section of mysensors should be the "correct" one.
EDIT: Hrhr @Yveaux vcc lib is cute workd out of the box thx
how do you communicate with openhab? An own mqtt broker? if yes, can u paste the messages? if not, can you paste the openhab log (if you don't see enough in the logfile, set loglevel to debug)
I am not so really skilled in transferring a wiring diagram to "real live". Is this the correct implementation for battery measuring?
retested ... works.
Does the cap size has any "disadvantages"?
hmmm i changed the filter cap to 100nF and powered off the gateway over night: today the node connected at once. I will test again later.
I'll try to answer as much as possible
thx again
recap:
after a longer downtime of the gw the nodes need
in order to reconnect
EDIT. Code attached
/**
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2015 Sensnology AB
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik Ekblad
*
* DESCRIPTION
* The W5100 MQTT gateway sends radio network (or locally attached sensors) data to your MQTT broker.
* The node also listens to MY_MQTT_TOPIC_PREFIX and sends out those messages to the radio network
*
* LED purposes:
* - To use the feature, uncomment WITH_LEDS_BLINKING in MyConfig.h
* - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
* - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
* - ERR (red) - fast blink on error during transmission error or recieve crc error
*
* See http://www.mysensors.org/build/esp8266_gateway for wiring instructions.
* nRF24L01+ ESP8266
* VCC VCC
* CE GPIO4
* CSN/CS GPIO15
* SCK GPIO14
* MISO GPIO12
* MOSI GPIO13
*
* Not all ESP8266 modules have all pins available on their external interface.
* This code has been tested on an ESP-12 module.
* The ESP8266 requires a certain pin configuration to download code, and another one to run code:
* - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
* - Connect GPIO15 via 10K pulldown resistor to GND
* - Connect CH_PD via 10K resistor to VCC
* - Connect GPIO2 via 10K resistor to VCC
* - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
*
* Inclusion mode button:
* - Connect GPIO5 via switch to GND ('inclusion switch')
*
* Hardware SHA204 signing is currently not supported!
*
* Make sure to fill in your ssid and WiFi password below for ssid & pass.
*/
// Custom Settings
#define SKETCH_NAME "mqttClientGateway"
#define SKETCH_MAJOR_VERSION "1"
#define SKETCH_MINOR_VERSION "0"
#include <EEPROM.h>
#include <SPI.h>
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enables and select radio type (if attached)
#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69
#define MY_GATEWAY_MQTT_CLIENT
// Set this nodes subscripe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "sensor-gw1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "sensor-gw1-in"
// Set MQTT client id
#define MY_MQTT_CLIENT_ID "sensor-gw1"
// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#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)
#define MY_SOFTSPI
// Arduino Uno
//#define MY_SOFT_SPI_SCK_PIN 14
//#define MY_SOFT_SPI_MISO_PIN 16
//#define MY_SOFT_SPI_MOSI_PIN 15
// Arduino Mega
#define MY_SOFT_SPI_SCK_PIN A0
#define MY_SOFT_SPI_MISO_PIN A2
#define MY_SOFT_SPI_MOSI_PIN A1
#endif
// When W5100 is connected we have to move CE/CSN pins for NRF radio
#define MY_RF24_CE_PIN 5
#define MY_RF24_CS_PIN 6
// Enable these if your MQTT broker requires usenrame/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,100,10
// If using static ip you need to define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,100,1
#define MY_IP_SUBNET_ADDRESS 255,255,0,0
// MQTT broker ip address.
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 100, 3
// The MQTT broker port to to open
#define MY_PORT 1883
/*
// Flash leds on rx/tx/err
#define MY_LEDS_BLINKING_FEATURE
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300
// 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
#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 <MySensor.h>
void setup() {
}
void presentation() {
// Present locally attached sensors here
sendSketchInfo(SKETCH_NAME, SKETCH_MAJOR_VERSION"."SKETCH_MINOR_VERSION);
}
void loop() {
// Send locally attech sensors data here
}
**EDIT: can someone move thes thread to the troubleshoot section? **
hmm maybe it's more of a problem than i thought: the first connection of the node to the ggateway does still require one or two resets of the node
I turned off and on the gateway and simply waited in order to have the node reconnected to the gw. But this does not happen:
Every 6 "actions/sendings" from the node to the gw i can see:
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
Only resetting the node connects it to the network again.
As long as openhab supports (u did already verify that) 2 mqtt connections, you should be fine.
Topic says it all. I think I have configured signing and encryption, but is there some point, where to verify if messages are really signed/encrypted?
Sketch size did increase, but i don't think thats a proper hint
I use a different kind of setup. I'm not using the mqttGateway example but die mqttClientGateway.
This means the arduino gateway is not the messagebroker (server) itself, but is forwarding the messages to another broker (mosquitto)
This allows me to post non-mysensors messages to the broker and openhab can consume them. A external broker is nessecary, because the mqttClientGateway can handle only one single connection (openhab, so no new messages from external tools, no debugging while openhab is connected etc) and i'm much more experienced in using software on the linux side instead on arduino => external broker
When looking in the examples of mysensors, there are only 2 examples for mqttClientGateways (development branch):
The Mega is nessecary, because the sketch size with optiboot was 108% of the allowed size without debugging (as far as i remember)
And Yes the pins are other ones on the mega, but that requires just changing the sketch.
Hello
EDIT: I posted this thread to General diskussions, because I don't know if there is somethink to troubleshoot or bugreport ...
I have the following behavior:
When starting a node after it's off some time, it fails to connect to the gateway:
Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=fail:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=fail:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=fail:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=fail:0.1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
Erm .. ok: 0/6 messages are ok. Powering it off and on (and mybe pressing the reset buttin once or twice) results in partial st=ok:
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=fail:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=fail:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=fail:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=ok:1
Strange ... 2/6 messages are ok ok lets reset the node again:
Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=ok:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=ok:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
Hmm .. almost ... 4/6 messages are ok ... reset again:
Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=ok:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=ok:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=ok:1
Here we are 6/6 messages are ok ... but i can image, that's not the way it's inted to be, isn't it? I did not change the wiring or something on the code between the power cycles/resets.
** Some time went by trying to get more infos **
Ah i could narrow it down: It's the gateway causing the problem: When the GW was off some time (simple unplug/plug does not cause this problem) it takes some time until the nodes could connect again.
Times:
GW offline: ~7m
Node can reconnect: ~1m20s
Not shure if this is a real world problem or not ... maybe i should think about a mini usv for the gateway
The setup itself is working. The problem is, that you're using the RFM69 module as network device. There is no client gateway example for that device and i think i've read somehere here, that it won't become implemented (to large footprint?).
EDIT:
in case u're still interested, here a small impression how simple this setup works:
mosquitto_sub -v -t '#'
sensor-gw1-out/99/255/3/0/11 Test Sensor
sensor-gw1-out/99/255/3/0/12 0.1
sensor-gw1-out/99/3/1/0/16 1
String sketch_name_99 "Sketch name 99 (Test Item) [%s]" (sketch,all) { mqtt="<[mysensors:sensor-gw1-out/99/255/3/0/11:state:default]" }
Thats it
Another question:
I don't have any experience with the classic setup (broker on gateway). But does
The topic resembles the serial protocol. You must define you preferred subscribe and publish prefix in the sketch. The topic is build like this:
MY_MQTT_PUBLISH_TOPIC_PREFIX/FROM-NODE-ID/SENSOR-ID/CMD-TYPE/ACK-FLAG/SUB-TYPE
mean, that the consuming controllers configuration (openhab in my case) has to be changed?
From
sensor-gw1-out/99/3/V_TRIPPED
To
sensor-gw1-out/99/3/1/0/16
in order to represent what is really pushed to the mqtt broker? Because thats what is posted to the broker?
@Yveaux do u have some code snipplet/example showing this ?
ok thats simple
How to you manage your sketches? I have a git repos with the sketches i use. This means a lot of code duplication, because now i need a sketch per node ID instead per node "type"?
Hello
I need some explanations concerning this setup:
Node => gateway mit mqqt client => mosquitto broker => openhab
Openhab and mosquitto are running fine. Gateway too I think.
At the moment I have 2 items: one static mqqt pub script and one mysensor module.
This can be seen in mosquitto:
infrastructure/sky_state ON
sensor-gw1-out/255/255/3/0/3 (null)
sensor-gw1-out/255/255/3/0/3 (null)
sensor-gw1-out/255/255/3/0/3 (null)
The infrastructure part works and is switched in openhab. The sensor-gw1-out messages are (as far as I've understood this) are the requests from to node to get a NODE_ID
And this is the part, where I'm clueless
are these node id static after initial assignment? Where are they stored in order to survive a node restart? Or are dynamic nodes in my setup the wrong approach and I have to use static node IDs (which would be quite annoying )Thank for input
extending this question:
I have this setup:
node1 => gateway with mqtt Client => mosquitto as mqtt broker => openhab
The result in the gateway is:
0;0;3;0;9;MQTT connected
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
0;0;3;0;9;Sending message on topic: gateway1-out/255/255/3/0/3
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
0;0;3;0;9;Sending message on topic: gateway1-out/255/255/3/0/3
0;0;3;0;9;read: 255-255-0 s=255,c=3,t=3,pt=0,l=0,sg=0:
0;0;3;0;9;Sending message on topic: gateway1-out/255/255/3/0/3
does this mean, that autoassigning a node ID fails?
Found the error:
As soon as in MyConfig.h die following is enabled, compiling fails:
#define MY_GATEWAY_W5100
EDIT:
#define MY_GATEWAY_W5100
is not nessecary at all? even the gatewayClient sketch compiles successful without it.
Hello
I have some trouble compiling the sensor examples from the development branch.
Every example besides the gatewayClients fails:
In file included from /home/dakkar/devzone/Arduino/libraries/MySensors/MySensor.h:139:0,
from /home/dakkar/devzone/Arduino/libraries/MySensors/examples/BinarySwitchSleepSensor/BinarySwitchSleepSensor.ino:41:
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:59:2: error: 'EthernetServer' does not name a type
EthernetServer _ethernetServer(_ethernetGatewayPort);
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:67:9: error: 'EthernetClient' does not name a type
static EthernetClient client = EthernetClient();
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool gatewayTransportInit()':
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:123:4: error: 'Ethernet' was not declared in this scope
Ethernet.begin(_ethernetGatewayMAC);
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:136:3: error: '_ethernetServer' was not declared in this scope
_ethernetServer.begin();
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool gatewayTransportSend(MyMessage&)':
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:179:4: error: '_ethernetServer' was not declared in this scope
_ethernetServer.write(_ethernetMsg);
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool _readFromClient()':
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:219:10: error: 'client' was not declared in this scope
while (client.connected() && client.available()) {
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp: In function 'bool gatewayTransportAvailable()':
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:308:4: error: 'EthernetClient' was not declared in this scope
EthernetClient newclient = _ethernetServer.available();
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:308:19: error: expected ';' before 'newclient'
EthernetClient newclient = _ethernetServer.available();
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:310:8: error: 'newclient' was not declared in this scope
if (newclient) {
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:311:9: error: 'client' was not declared in this scope
if (client != newclient) {
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:319:8: error: 'client' was not declared in this scope
if (client) {
^
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp: In function 'void gatewayTransportRenewIP()':
/home/dakkar/devzone/Arduino/libraries/MySensors/core/MyGatewayTransportEthernet.cpp:359:6: error: 'Ethernet' was not declared in this scope
if (Ethernet.maintain() & ~(0x06)) {
^
exit status 1
Error compiling.
Sketch: MySensors/examples/BinarySwitchSleepSensor/BinarySwitchSleepSensor.ino
Arduino: 1.6.6
OS: Ubuntu 15.10
Any idea?
maybe the solution is to use an alternative setup:
Not using the mqtt gateway from the example, but using the mqtt CLIENT gateway (currently on the development branch)
This allows u to set up an mqtt broker (mosquitto) on your openhap host and the two gateways are sending their messages to this broker instead of being the broker themselves.
Edit:
narf. i see the client gateway examples are only for w5100 and ESP8266
@HarryDutch Hu awesome link. Thanks!
@m26872 hmm you're right. maybe this is a too generic question to be discussed here. pardon me.
Another "noobish" question:
When using this bootloader, one cycle takes 8 seconds? What happens, if for example, a switch is pressed between? does this sensor detect this?
@dakky said:
The gateway tries to open a lot of connections and all of them seem to die after a short while
Any idea?
Narghs!
Seems to be a hardware problem. I changed the w5100 module with an w5100 arduino shield and now it works fine:
0;0;3;0;9;Starting gateway (RNNGA-, 1.6.0-beta)
0;0;3;0;9;Radio init successful.
IP: 192.168.100.10
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;MQTT connected
0;0;3;0;9;Init complete, id=0, parent=0, distance=0
I'm still interested in the reason. Hardware broken or wiring fail?
=> basic networking seems to work, but "delivering content" failed. Any guesses?
Strange fact: with the "broken" hardware:
0;0;3;0;9;Radio init successful.
IP: 0.40.68.10
with the shield:
0;0;3;0;9;Radio init successful.
IP: 192.168.100.10
Same sketch, 192.168.100.10 is the correct Ip (obviously)
Greeting
Dakky
Thx 4 replying
mosquitto version 1.4.5 (build date Sun, 08 Nov 2015 21:43:12 +0000)
unfortunetly this seems not to be the problem
EDIT: i updated the PubSubClient lib to version 2.4 instead of the delivered 1.9. Same behavior
Another EDIT: mosquitto itself seems to work fine: OpenHab successfully connects to the broker and delivers its messages
Hello.
I tried the development branch because I prefer having my gateway not as message broker.
I had some problems resulting in conflicting entries for the gateway in MyConfig.h and the sketch. MyConfig.h always wins for the release it might be more transparent for the user if there is only one location, where the gateway settings are defined: example or MyConfig.h
So much for the feedback, now to the problems:
I use the w5100 version of the sketch with a static IP.
In the serial monitor i see:
0;0;3;0;9;Starting gateway (RNNGA-, 1.6.0-beta)
0;0;3;0;9;Radio init successful.
IP: 0.40.68.10
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Init complete, id=0, parent=0, distance=0
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
0;0;3;0;9;Attempting MQTT connection...
in the log of the moquitto server i see:
1450112394: New connection from 192.168.100.10 on port 1883.
1450112394: New connection from 192.168.100.10 on port 1883.
1450112394: Socket error on client <unknown>, disconnecting.
1450112409: New connection from 192.168.100.10 on port 1883.
1450112409: New connection from 192.168.100.10 on port 1883.
The gateway tries to open a lot of connections and all of them seem to die after a short while
Any idea?
hurm you're right
some facts:
Hello
I sucessfully uploaded the mqtt gateway example. The host is reachable from the network => w5100 seems to work fine.
$> ping 192.168.111.1
PING 192.168.111.1 (192.168.111.1) 56(84) bytes of data.
64 bytes from 192.168.111.1: icmp_seq=1 ttl=128 time=0.092 ms
64 bytes from 192.168.111.1: icmp_seq=2 ttl=128 time=0.091 ms
Serial monitor states:
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
Ok!
so everthing seems fine in my eyes. BUT: the mqtt broker seems not to start. nmap/telnet to 192.168.111.1:1883 fails and a mosquitto_pub/sub does time out after a while.
$> mosquitto_sub -v -t \$SYS/# -h 192.168.111.1
Error: Connection timed out
Any idea how to debug this problem?
EDIT: I used MySigningNone signer; because debug + spi + signing does not fit on an arduino uno
Is this MQTTClientGateway in the dev branch only? I didn't see something like this in the 1.5 release/master.
I would prefer to use my gateway as client, but I am not skilled enough to use the dev branch and work around resulting problems 
greetings
Dakky
edit:
@tomkxy said:
@tomkxy said:
here https://github.com/tomkxy/Arduino.git in the branch MQTTClient.
Did you have a look at my repository above? Functional wise it is the same adapted for version 1.5. I have it in use for quite a while now.
hmm is this repo still functional? with the signing_feature enabled i'm getting compile errors:
mqttClientGateway:175: error: 'signer' was not declared in this scope
, signer
^
Could u show a screen for the lockbits too? I have never set them before and need some guidance thanks
Dakky
Hurm strange things are happening here ...
short timeline:
avrdude: stk500_recv(): programmer is not respondingI don't have to understand that, have I ?
Hello
ich just downloaded the 1.5 release of mysensors to restart the project after some break
I configured MyConfig.h, loaded the example sketch and configured MyMQTT.h and the sketch compiles successfully. But when trying to upload the sketch i receive the folowing error:
Sketch uses 31,688 bytes (98%) of program storage space. Maximum is 32,256 bytes.
Global variables use 1,015 bytes (49%) of dynamic memory, leaving 1,033 bytes for local variables. Maximum is 2,048 bytes.
avrdude: verification error, first mismatch at byte 0x7800
0xff != 0x35
avrdude: verification error; content mismatch
This happens ONLY with this sketch. The sample arduino blink works fine. Any idea whats wrong?
I use the arduino UnO R3 as gateway
nobody ever tried tried to upload the sketch with SOFTSPI and debug enabled to an arduino uno? Even with optiboot the sketch seems to be too large
Mine is about 2 years old. So im not sure about this. If this is the case, i habe another problem. I cant upload the mqqtclientgatway sketch with debug on.
hmm i don't have another arduino to program my gateway
Can't imagine, that it it that hard, to burn a new bootloader with the usbtiny, which is a very common piece of hardware :S
Greeting
another noobish question
i need some more space for my sketch (trying to push the MQTTClientGateway sketch),
So i thought trying optiboot is a good idea.
BUT: after some hours of searching I have the usbtinyisp connected with the uno, finally found the right location where to boot the optiboot files for the arduino IDE and ... a breaker:
I don't have the choise to select a optiboot arduino uno board:
What do I have to do now in order to flash the new bootloader?
Thx
Dakky