Posts made by Francois

HI @user2684 thanks for that is is working now

Hi @user2684 I try to used Nodemanage with a motion sensor. But I only see the on event and not the off event. What do I have to do to see both the events.

Thanks

Francois

Hi don't understand why I am not seeing the values for my BH1750 sensor and the battery voltage. If I look at the logs it is send from the sensor to Home Assistant. Below is the logs. What is wrong here? I am running version 2.3.0 on all the nodes

ESP gateway logs

100589130 TSF:MSG:READ,31-31-0,s=255,c=0,t=17,pt=0,l=11,sg=0:2.3.0-alpha
100589137 GWT:TPS:TOPIC=mygateway1-out/31/255/0/0/17,MSG SENT
100589697 TSF:MSG:READ,31-31-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
100589702 GWT:TPS:TOPIC=mygateway1-out/31/255/3/0/6,MSG SENT
100589773 GWT:IMQ:TOPIC=mygateway1-in/31/255/3/0/6, MSG RECEIVED
100589788 TSF:MSG:SEND,0-0-31-31,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=OK:M
100589855 TSF:MSG:READ,31-31-0,s=255,c=3,t=11,pt=0,l=16,sg=0:Light Lux Sensor
100589862 GWT:TPS:TOPIC=mygateway1-out/31/255/3/0/11,MSG SENT
100590422 TSF:MSG:READ,31-31-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
100590428 GWT:TPS:TOPIC=mygateway1-out/31/255/3/0/12,MSG SENT
100590987 TSF:MSG:READ,31-31-0,s=0,c=0,t=16,pt=0,l=0,sg=0:
100590992 GWT:TPS:TOPIC=mygateway1-out/31/0/0/0/16,MSG SENT
100591554 TSF:MSG:READ,31-31-0,s=5,c=0,t=30,pt=0,l=0,sg=0:
100591559 GWT:TPS:TOPIC=mygateway1-out/31/5/0/0/30,MSG SENT
100592121 TSF:MSG:READ,31-31-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
100592342 TSF:MSG:SEND,0-0-31-31,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
100592425 TSF:MSG:READ,31-31-0,s=5,c=1,t=38,pt=7,l=5,sg=0:3.28
100592431 GWT:TPS:TOPIC=mygateway1-out/31/5/1/0/38,MSG SENT
100592992 TSF:MSG:READ,31-31-0,s=255,c=3,t=0,pt=1,l=1,sg=0:100
100592997 GWT:TPS:TOPIC=mygateway1-out/31/255/3/0/0,MSG SENT
100623883 TSF:MSG:READ,31-31-0,s=0,c=1,t=37,pt=3,l=2,sg=0:11

Log from HA

2018-07-20 21:04:05 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 31;255;3;0;11;Light Lux Sensor
2018-07-20 21:04:05 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 31 child 255
2018-07-20 21:04:05 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Not a child update for node 31
2018-07-20 21:04:05 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 31;255;3;0;12;1.0
2018-07-20 21:04:05 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 31 child 255
2018-07-20 21:04:05 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Not a child update for node 31
2018-07-20 21:04:06 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 31;0;0;0;16;
2018-07-20 21:04:06 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 31 child 0
2018-07-20 21:04:06 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] No child values for node 31 child 0
2018-07-20 21:04:06 DEBUG (MainThread) [mysensors.gateway_mqtt] Subscribing to: mygateway1-out/31/0/1/+/+, qos: 0
2018-07-20 21:04:06 DEBUG (MainThread) [mysensors.gateway_mqtt] Subscribing to: mygateway1-out/31/0/2/+/+, qos: 0
2018-07-20 21:04:06 DEBUG (MainThread) [mysensors.gateway_mqtt] Subscribing to: mygateway1-out/31/+/4/+/+, qos: 0
2018-07-20 21:04:07 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 31;5;0;0;30;
2018-07-20 21:04:07 WARNING (MainThread) [mysensors] Not a valid message: Not valid message sub-type: 30 for dictionary value @ data['sub_type']
2018-07-20 21:04:07 DEBUG (MainThread) [mysensors.gateway_mqtt] Receiving 31;0;1;0;37;214
2018-07-20 21:04:07 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Node update: node 31 child 0
2018-07-20 21:04:07 DEBUG (MainThread) [homeassistant.components.mysensors.gateway] Invalid values: {37: '214'}: sensor platform: node 31 child 0: S_LIGHT_LEVEL requires value_type V_LIGHT_LEVEL @ data[23]```

I also just order my gateway

Thank @hek this fix my problem as I was using 8Mhz Arduino mini pro as a gateway.

Hi @hek I start testing the OH2 with the new binding over the last few days and I couldn't get any of my relay nodes to work with the lasts version of the serial gateway software Beta2 . I had a setup running Domoticz with and older version of the of the Serial Gateway beta software on it and once loaded OH2 software and configure it work fine. All sensor that send data to the serial gateway work with the new version of the gateway software it is only when the serial gateway have to send data to relay nodes and dimmer that it is nothing work. Is there something in the MyConfig.h file that I missed or is there any other place that I need to changes anything?

Thanks

Francois

@TimO mysensor is now working The only problem I have and I also had the same problem with OpenHab 1.8.2 as well in that I don't get my relay sensor to switch on or off. If if look at the log openhab it is sending the commands to the RelayActuator what am I doing wrong with this sensor? All my other sensor are reporting back to the dashboard.

11:59:32.760 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'teststudy' received command ON
11:59:32.769 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 101;1;1;1;2;1
11:59:32.782 [INFO ] [marthome.event.ItemStateChangedEvent] - teststudy changed from NULL to ON
11:59:32.789 [DEBUG] [g.mysensors.handler.MySensorsHandler] - handleUpdate called
11:59:32.873 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 101;1;1;1;2;1
11:59:32.977 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 101;1;1;1;2;1
11:59:33.478 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 101;1;1;1;2;1
11:59:34.479 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 101;1;1;1;2;1
11:59:35.209 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;1;1;0;16;0
11:59:35.221 [INFO ] [marthome.event.ItemStateChangedEvent] - studymotion changed from OPEN to CLOSED
11:59:35.243 [INFO ] [marthome.event.ItemStateChangedEvent] - studymotionlastup changed from 2016-04-23T11:59:31.084+0200 to 2016-04-23T11:59:35.229+0200
11:59:35.269 [INFO ] [marthome.event.ItemStateChangedEvent] - studymotionlastup changed from 2016-04-23T11:59:35.229+0200 to 2016-04-23T11:59:35.248+0200
11:59:36.480 [WARN ] [g.mysensors.protocol.MySensorsWriter] - NO ACK from nodeId: 101
11:59:36.483 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - No old status know to revert to!

@TimO I just download the last version of the beta version and recompile my gateway and I still am getting the same error code. There is not something that I missed in the MyConfig.h file or any other file that I need to change in openHAB2?

@TimO I have this gateway working on Domoticz without any problem. Put on OH2 I am getting this error and i don't know why it is happing

@andreacioni Here is is the info:

0;255;3;0;9;Starting gateway (RRNGA-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
0;255;3;0;14;Gateway startup complete.
0;255;3;0;9;Init complete, id=0, parent=0, distance=0
0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
40;1;1;0;16;1
0;255;3;0;9;read: 40-40-0 s=255,c=3,t=0,pt=1,l=1,sg=0:100
40;255;3;0;0;100
0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
40;1;1;0;16;1
0;255;3;0;9;read: 2-2-0 s=0,c=1,t=1,pt=7,l=5,sg=0:34.0
2;0;1;0;1;34.0
0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
40;1;1;0;16;0
0;255;3;0;9;read: 40-40-0 s=0,c=1,t=23,pt=2,l=2,sg=0:80
40;0;1;0;23;80
0;255;3;0;9;read: 40-40-0 s=255,c=3,t=0,pt=1,l=1,sg=0:100
40;255;3;0;0;100
0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
40;1;1;0;16;1
0;255;3;0;9;read: 101-101-0 s=255,c=3,t=15,pt=0,l=2,sg=0:

0;255;3;0;9;send: 0-0-101-101 s=255,c=3,t=15,pt=0,l=2,sg=0,st=fail:

0;255;3;0;9;read: 101-101-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
101;255;3;0;6;0
0;255;3;0;9;read: 101-101-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
101;255;3;0;6;0
0;255;3;0;9;read: 101-101-0 s=255,c=3,t=12,pt=0,l=3,sg=0:2.0
101;255;3;0;12;2.0

@andreacioni sorry how do I do this I_VERSION command to the gateway?

@TimO I still get the same error after I disable debugging in the gateway

@andreacioni Thanks for this all my sensor are running on version 2 so I don't know it my nodes will run on an 1.5 serial GW

@TimO I try openHab 2.0 binding today and I am getting this where the serial changes from Initializing to Offline. Even if I reboot I get the same error. Why is this happing?

12:49:05.469 [DEBUG] [nsors.handler.MySensorsBridgeHandler] - Initialization of the MySensors Bridge
12:49:05.543 [DEBUG] [col.serial.MySensorsSerialConnection] - Connecting to /dev/ttyUSB0 [baudRate:115200]
12:49:06.140 [INFO ] [smarthome.event.ItemAddedEvent      ] - Item 'mysensors_bridge_ser_bb7302f6' has been added.
12:49:06.390 [DEBUG] [col.serial.MySensorsSerialConnection] - Successfully connected to serial port.
12:49:06.446 [INFO ] [rthome.event.ItemThingLinkAddedEvent] - Link 'mysensors_bridge_ser_bb7302f6-mysensors:bridge-ser:bb7302f6' has been added.
12:49:09.409 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Starting gateway (RRNGA-, 2.0.0-beta)
12:49:09.426 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Radio init successful.
12:49:09.434 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;14;Gateway startup complete.
12:49:09.441 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Init complete, id=0, parent=0, distance=0
12:49:09.506 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Sending to MySensors: 0;0;3;0;2;
12:49:10.488 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing 'mysensors:bridge-ser:bb7302f6' takes more than 5000ms.
12:49:10.763 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
12:49:10.767 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;1;1;0;16;1
12:49:11.676 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
12:49:11.680 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;1;1;0;16;1
12:49:11.778 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=0,c=1,t=23,pt=2,l=2,sg=0:72
12:49:11.783 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;0;1;0;23;72
12:49:11.792 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=5,c=1,t=38,pt=7,l=5,sg=0:3.07
12:49:11.796 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;5;1;0;38;3.07
12:49:11.838 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=5,c=1,t=38,pt=7,l=5,sg=0:3.07
12:49:11.843 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;5;1;0;38;3.07
12:49:11.861 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 40-40-0 s=255,c=3,t=0,pt=1,l=1,sg=0:100
12:49:11.866 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 40;255;3;0;0;100
12:49:12.079 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 66-66-0 s=1,c=1,t=24,pt=5,l=4,sg=0:3579898
12:49:12.083 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 66;1;1;0;24;3579898
12:49:14.409 [ERROR] [s.internal.MySensorsBridgeConnection] - Cannot start reading/writing thread, probably sync message (I_VERSION) not received
12:49:14.410 [DEBUG] [col.serial.MySensorsSerialConnection] - Shutting down serial connection!
12:49:14.412 [DEBUG] [g.mysensors.protocol.MySensorsWriter] - Stopping Writer thread
12:49:14.418 [WARN ] [g.mysensors.protocol.MySensorsWriter] - Writer thread interrupted
12:49:14.428 [DEBUG] [g.mysensors.protocol.MySensorsReader] - Stopping Reader thread
12:49:14.528 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:bb7302f6' changed from INITIALIZING to OFFLINE
Insert Code Here

@scalz how is atc working on the rfm69?

All my temp motion and humidity sensor work but my relay and dimmer sensor don't work, why will this be the case? Here is the log:

2016-04-03 09:25:07.928 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:07.930 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:08.186 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:08.406 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:08.527 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:08.539 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:08.584 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:08.588 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:08.625 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:08.802 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:09.247 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:09.588 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:10.421 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:10.899 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:11.410 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:11.431 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:11.594 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:11.829 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:12.513 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:12.840 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:12.841 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 0
2016-04-03 09:25:13.145 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,0) is called!
2016-04-03 09:25:13.394 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:13.422 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:17.880 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:17.882 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:18.025 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:18.536 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:18.538 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:18.541 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:22.736 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:22.737 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 0
2016-04-03 09:25:23.021 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 95-95-0 s=1,c=1,t=16,pt=1,l=1,sg=0:1
2016-04-03 09:25:23.022 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Kitchen = ON
2016-04-03 09:25:23.033 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,0) is called!
2016-04-03 09:25:23.431 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Kitchen,ON) is called!
2016-04-03 09:25:23.765 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=5,c=1,t=38,pt=7,l=5,sg=0:2.90
2016-04-03 09:25:23.766 [DEBUG] [.b.m.internal.MySensorsBinding] - MotionBatVcc_GF_Study = 2.90
2016-04-03 09:25:23.937 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(MotionBatVcc_GF_Study,2.90) is called!
2016-04-03 09:25:26.984 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:26.985 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:27.203 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:27.648 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:27.650 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:27.650 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 66-66-0 s=1,c=1,t=17,pt=5,l=4,sg=0:315
2016-04-03 09:25:27.651 [INFO ] [.b.m.internal.MySensorsBinding] - No item configured for "66;1;V_WATT"
2016-04-03 09:25:27.653 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:29.284 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 66-66-0 s=1,c=1,t=24,pt=5,l=4,sg=0:2718269
2016-04-03 09:25:29.286 [INFO ] [.b.m.internal.MySensorsBinding] - No item configured for "66;1;V_VAR1"
2016-04-03 09:25:31.838 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:31.840 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 0
2016-04-03 09:25:32.184 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,0) is called!
2016-04-03 09:25:33.022 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 95-95-0 s=1,c=1,t=16,pt=1,l=1,sg=0:0
2016-04-03 09:25:33.024 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Kitchen = OFF
2016-04-03 09:25:33.326 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Kitchen,OFF) is called!
2016-04-03 09:25:35.140 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:35.141 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:35.447 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:35.556 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
2016-04-03 09:25:35.557 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 1
2016-04-03 09:25:35.561 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,1) is called!
2016-04-03 09:25:36.738 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:36.851 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:37.297 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:37.324 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:37.758 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:37.962 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:38.434 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:38.454 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
2016-04-03 09:25:38.877 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
2016-04-03 09:25:39.995 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:40.045 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Study = 0
2016-04-03 09:25:40.341 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Study,0) is called!
2016-04-03 09:25:40.590 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 82-82-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:40.591 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Kitchen01 = OFF
2016-04-03 09:25:40.595 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Kitchen01,OFF) is called!
2016-04-03 09:25:41.596 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 2-2-0 s=0,c=1,t=1,pt=7,l=5,sg=0:43.4
2016-04-03 09:25:41.597 [DEBUG] [.b.m.internal.MySensorsBinding] - Hum_GF_Study = 43.4
2016-04-03 09:25:41.852 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Hum_GF_Study,43.4) is called!
2016-04-03 09:25:43.390 [DEBUG] [.b.m.internal.MySensorsBinding] - I_LOG_MESSAGE: read: 82-82-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
2016-04-03 09:25:43.392 [DEBUG] [.b.m.internal.MySensorsBinding] - Motion_GF_Kitchen01 = OFF
2016-04-03 09:25:43.395 [DEBUG] [.b.m.internal.MySensorsBinding] - internalReceiveUpdate(Motion_GF_Kitchen01,OFF) is called!

Hi @bkl

Are you using the standard relay sketch with this binding or did you change anything in the sketch as I just don't get my relay to work.

Here is my log with the above string in my logback.xml.

17:28:48.825 [INFO ] [.b.m.internal.MySensorsBinding:257  ] - New MySensor node found: node-id=15
 * Example item: 15;255;I_BATTERY_LEVEL      - Use this to report the battery level 0-100 (%)
 * Example item: 15;255;I_SKETCH_NAME        - Sketch name that can be used to identify sensor
 * Example item: 15;255;I_SKETCH_VERSION     - Sketch version that can be reported to keep track of the version of sensor
17:28:48.827 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 15-15-0 s=255,c=3,t=6,pt=1,l=1,sg=0:0
17:28:50.856 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 15-15-0 s=255,c=3,t=11,pt=0,l=25,sg=0:Main Bedroom Relay & Butt
17:28:50.858 [INFO ] [.b.m.internal.MySensorsBinding:318  ] - No item configured for "15;255;I_SKETCH_NAME"
17:28:50.860 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 15-15-0 s=255,c=3,t=12,pt=0,l=3,sg=0:2.0
17:28:50.862 [INFO ] [.b.m.internal.MySensorsBinding:318  ] - No item configured for "15;255;I_SKETCH_VERSION"
17:28:50.864 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 15-15-0 s=1,c=0,t=3,pt=0,l=0,sg=0:
17:28:50.867 [INFO ] [.b.m.internal.MySensorsBinding:257  ] - New MySensor sensor found (Binary device (on/off)): node-id=15, sensor-id=1 with type S_BINARY
 * Example item: 15;1;V_STATUS             - Binary status. (on/off)
 * Example item: 15;1;V_WATT               - Watt value for power meters
17:28:51.457 [DEBUG] [.p.rrd4j.internal.RRD4jService:113  ] - Stored 'LightSwitch_GF_Study' with state 'ON' in rrd4j database (again)
17:28:51.460 [DEBUG] [.p.rrd4j.internal.RRD4jService:132  ] - Stored 'LightSwitch_GF_Study' with state '0' in rrd4j database
17:28:51.500 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command OFF
17:28:51.503 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
17:28:51.719 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 2-2-0 s=0,c=1,t=1,pt=7,l=5,sg=0:29.1
17:28:51.722 [DEBUG] [.b.m.internal.MySensorsBinding:307  ] - Hum_GF_Study = 29.1
17:28:51.729 [DEBUG] [.p.rrd4j.internal.RRD4jService:132  ] - Stored 'Hum_GF_Study' with state '29.1' in rrd4j database
17:28:51.760 [INFO ] [runtime.busevents             :26   ] - Hum_GF_Study state updated to 29.1
17:28:51.762 [DEBUG] [.b.m.internal.MySensorsBinding:248  ] - internalReceiveUpdate(Hum_GF_Study,29.1) is called!
17:28:51.862 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command ON
17:28:51.864 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
17:28:52.045 [DEBUG] [.p.rrd4j.internal.RRD4jService:132  ] - Stored 'LightSwitch_GF_Study' with state '0' in rrd4j database
17:28:52.075 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command OFF
17:28:52.077 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
17:28:52.252 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command ON
17:28:52.255 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
17:28:52.448 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command OFF
17:28:52.451 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,OFF) is called!
17:28:52.648 [DEBUG] [.b.m.internal.MySensorsBinding:263  ] - I_LOG_MESSAGE: read: 40-40-0 s=1,c=1,t=16,pt=0,l=1,sg=0:1
17:28:52.650 [INFO ] [runtime.busevents             :22   ] - LightSwitch_GF_Study received command ON
17:28:52.654 [DEBUG] [.b.m.internal.MySensorsBinding:230  ] - internalReceiveCommand(LightSwitch_GF_Study,ON) is called!
17:28:52.659 [DEBUG] [.b.m.internal.MySensorsBinding:307  ] - Motion_GF_Study = ON
17:28:52.662 [DEBUG] [.p.rrd4j.internal.RRD4jService:113  ] - Stored 'Motion_GF_Study' with state 'OFF' in rrd4j database (again)

Hi what is the syntax for a relay in openhab using this binding?

This in what I get in the log but the light do not switch on or off.

2016-03-27 20:37:00.068 [INFO ] [runtime.busevents             ] - LightSwitch_GF_Study received command ON
2016-03-27 20:37:00.889 [INFO ] [runtime.busevents             ] - LightSwitch_GF_Study received command OFF
2016-03-27 20:37:01.622 [INFO ] [runtime.busevents             ] - LightSwitch_GF_Study received command ON
2016-03-27 20:37:02.407 [INFO ] [runtime.busevents             ] - LightSwitch_GF_Study received command OFF
2016-03-27 20:37:03.247 [INFO ] [runtime.busevents             ] - LightSwitch_GF_Study received command ON

This is the syntax that I am use and it is not working. Also try V_LIGHT without any luck.

Switch LightSwitch_GF_Study	"Study Light  [%s]"				<light> 	(GF_Study)			{mysensors="41;1;V_BINARY"}

Hi I am new to openHAB how do you configure a relay node? I do see the node in the logs but the relay don't what to switch on or off. I have my temp and humidity sensors working already.

18:38:50.450 [INFO ] [.b.m.internal.MySensorsBinding:257  ] - New MySensor sensor found (Dimmable device of some kind): node-id=95, sensor-id=0 with type S_DIMMER
 * Example item: 95;0;V_STATUS             - Binary status. (on/off)
 * Example item: 95;0;V_PERCENTAGE         - Percentage value. 0-100 (%)
 * Example item: 95;0;V_WATT               - Watt value for power meters

Regards

Francois

@fets yes i did.

@Yveaux I must say that I like your library it is easy to use and it is on all my battery driven sensors. Thank for this great library.

HI @drock1985

I had the same problem with stable version that is why I change over to the 1.6 dev version. I use the serial gateway. I thought it the power supply that I used so I upgrade to better 5v power supply and still I am getting the same issue. The relay actuator will freeze after a day and the only way I can get it to work is power it off. What I don't understand is that I also run a NFR24L01 radio as relay Actuator also on dev 1.6 without any issues. The rest of my RFM69 sensor I don't have a problem with only with the relay sensors.

@riteshpatel I upgrade to version 1.6 beta as this have an must better integration with the RFM69 radios. Now you only have to configure your device in the MyConfig.h file. Also if you look at the sketch you will see you only have to #define MY_REPEATER_FEATURE to have the repeater.

// Enable debug prints to serial monitor
#define MY_DEBUG 

// Enable and select radio type attached
/m#define MY_RADIO_NRF24
#define MY_RADIO_RFM69

// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE

Hi my rfm69 RelayActuator keep on freezing. I am using version 1.6. This is the only node in my system that keep on freezing and the only way that I can get it to work is by removing the power from the sensor. The nodes will run for a day without any issues before it freeze. I also have have 2 Nrf24l01 RelayActuator with button running version 1.4 with in my system and this 2 node's don't freezes. I use Domoticz as my controller

@AWI what is the range and sensitive of this PIR?

@Cliff-Karlsson I had the same issue and didn't know what was the problem was so today i move over to Mysensor 1.6 Beta change relevant setting in MyConfig.h and recompile my serial gateway and some of my sensor and the problem when away. On what version of Domoticz are you?

I am also use the RFM69W with an mini pro

Just compile the DallasTemp sketch and it is working.
Starting sensor (1.6.0-beta)
Radio init successful.
send: 101-101-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 101-101-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
read: 0-0-101 s=255,c=3,t=6,pt=0,l=1,sg=0:M
send: 101-101-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=ok:Temperature Sensor
send: 101-101-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.1
Init complete, id=101, parent=0, distance=1
Starting sensor (1.6.0-beta)
Radio init successful.
send: 101-101-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 101-101-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
read: 0-0-101 s=255,c=3,t=6,pt=0,l=1,sg=0:M
send: 101-101-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,st=ok:Temperature Sensor
send: 101-101-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.1
Init complete, id=101, parent=0, distance=1

@Cliff-Karlsson You have to change the following setting in Myconfig.h for you radio

/**********************************
*  RFM69 Driver Defaults
***********************************/
// Default network id. Use the same for all nodes that will talk to each other
#define RFM69_NETWORKID     100

// Default frequency to use. This must match the hardware version of the RFM69 radio (uncomment one):
 #define RFM69_FREQUENCY   RF69_433MHZ
//#define RFM69_FREQUENCY   RF69_868MHZ
//#define FREQUENCY     RF69_915MHZ

// Enable this for encryption of packets
//#define RFM69_ENABLE_ENCRYPTION
#define RFM69_ENCRYPTKEY  "sampleEncryptKey"

Then in MySensor.h you change the following:

ifndef MySensor_h
#define MySensor_h
#include "Version.h"   // Auto generated by bot
#include "MyConfig.h"
#include "MyHw.h"
#include "MyTransport.h"
//#include "MyTransportNRF24.h"
#include "MyTransportRFM69.h" 
#include "MyParser.h"
#ifdef MY_SIGNING_FEATURE
#include "MySigning.h"
#include "MySigningNone.h"
#endif
#include "MyMessage.h"
#ifdef MY_OTA_FIRMWARE_FEATURE
#include "utility/SPIFlash.h"
#endif
#include <stddef.h>
#include <stdarg.h>```


// look for this lines and changes this

class MySensor
{
  public:
	/**
	* Constructor
	*
	* Creates a new instance of Sensor class.
	*
	*/
	//MySensor(MyTransport &radio =*new MyTransportNRF24(), MyHw &hw=*new MyHwDriver()
	MySensor(MyTransport &radio =*new MyTransportRFM69(), MyHw &hw=*new MyHwDriver()

@rene_2k2 I don't have any issue with any of my nodes that is using the rfm69 radios. I also upgrade all my nodes to ver 1.5. I am using a series gateway and my controller is Domoticz

@rvendrame have a look at this low power board that is using the rfm69 https://hallard.me/bp-ulpnode/

@neverdie I just using jumper wire to connect the radio to the Arduino mini pro see picture. This is working for me now as it is fast to get a sensor up and running.Also, it have a small footprint as well.

What about support for the rfm69 radio?

@NeverDie it is just bare copper wire.

@fets yes ons DIY. I am using 433mhz radio and I just wound the wire around screwdriver the thickness of the wire is 5.8mm and it is working for me.

For now I am using the serial gateway.

@tekka do MYSBootloader also work with the RFM69 radios?

@Cliff-Karlsson I currently are using both the RFM69 and the NRF2401+. And from my experience I get better coverage from the RFM69. You can purchase complete units from Lowpowerlab (http://lowpowerlab.com/) or http://www.anarduino.com/miniwireless/. You can also just purchase the radio from Anarduino and his cost for the radio is $4.09. The RFM69HW is a high power radio +20 dBm Power Output Capability (longer range). I will not run this radio of batteries. How every if you look at RFM69W this is the one I am using the cost for this one is $3.80 and the out power is +13 dBm Capability and I get coverage inside and outside my house without any issue. The current I get on this radio with a door sensor (BinarySwitchSleepSensor) is 1uA in sleep mode. I also have a motion sensor and the current for this sensor in sleep mode is 30uA.

I have a power meter outside my house and could not get coverage with the normal NRF2401 even with the PA LNA radio I battle to get my pulse power sensor to work reliably. I change my pulse sensor over to the RFM69W and to date I did not have any issue with it not working

@hek Hi I got a new shipment of Arduino mini pro and after I did the low power hack on this Arduino I now are getting 30uA current usage. Thank again for all you support and for this great MySensor community that you started :). Now I can go full steam ahead in building more sensor for my house.

@rvendrame I will only go for the RFM69. When I start playing with the Mysensor project Hek only had only support for the NRF24l01+. Once they port the library over to support the RFM69 I stop using the NRF24L01+. Luckly I don't have big installation on the NRF24 radio.

@rvendrame I give all my nodes static ID's and this is working for me in Domoticz

@rvendrame yes I running 2 serial gateways on my Domoticz controller.

Hi I am using both at this stage and is busy change all my nodes over to the RFM69 and I don't have issue with range like I do with the NRS24L01+. I order my radio from Anadruino (http://www.anarduino.com/) to date I did not had any problems with the deliveries I get it relative fast. Also, it is easy to fit the radio on an Arduino mini pro see picture 1. Your footprint with the RFM69 is must smaller than it is if you fit the Arduino and NRF24l01 like I did with this LED dimmer and PIR Sensor see picture 2. The only problem I have at this stage is my power consumption is still high and I don't know why it is this high 3mA.

Picture 1:

Picture 2:

Great work thanks for all the hard work you putting in to this Hek and team

@kolaf sorry no I didn't play with clamp power probes yet

@kolaf yes I am running domoticz as it is easy to add sensor. I never had any luck with getting openhab to run. I am wait for the release of openhab2. BTW I am running my rf69 via a serial gateway. Do you the have 3 phase power to your farm?

@kolaf I run the same setup now for more than a 2 month and don't have this issue. For now I am running the power sensor of battery as my meter is outside my house as there is no 220 plug to run it off power supply. I still have a very small RF69 sensor network. I have 10 NRF24 sensor that I am now converting to RF69. Can this issue that you experience be to the size of your sensor network?

Here is some data from my power sensor for this week:

You put a work into this board and it looks great. Cannot wait for it to come available.

@kolaf Do you run any of your node off batteries if you do what is you current consumption?

@hek I see that you have powerDown in the MyHwATMega328.cpp how do I use that function?

void powerDown(period_t period) {

	ADCSRA &= ~(1 << ADEN);

	if (period != SLEEP_FOREVER)
	{
		wdt_enable(period);
		WDTCSR |= (1 << WDIE);
	}
	#if defined __AVR_ATmega328P__
		do {
			set_sleep_mode(SLEEP_MODE_PWR_DOWN);
			cli();
			sleep_enable();
			sleep_bod_disable();
			sei();
			sleep_cpu();
			sleep_disable();
			sei();
		} while (0);
	#else
		do {
			set_sleep_mode(SLEEP_MODE_PWR_DOWN);
			cli();
			sleep_enable();
			sei();
			sleep_cpu();
			sleep_disable();
			sei();
		} while (0);
	#endif

	ADCSRA |= (1 << ADEN);
}

@hek yes the radio is solder on

@hek sorry how will I disconnect the radio?

@hek with sleep(8000) I still get 3.75mA.

@hek to get down to 3uA I have to use the following line.

LowPower.powerDown(SLEEP_8S, ADC_OFF, BOD_OFF);

How do I do this in the current library. If I use the LowPower library I get an error when compile

@hek as per this Web site I should get about 16uA http://forum.anarduino.com/posts/list/39.page

Hi how do I put the RFM69 in sleep mode? I currently getting 4mA current draw for BinarySwitchSleepSensor. On the NRF24 for the same sketch, I get 3uA.

@tekka See below it reboot the first time when I try it the seconde time it did
not it just say reboot

Here is my routing Tabel:

@tekka log file send

@tekka will it be a problem if I don't have all my node on the MYSbootloader? Currently I only have 2 of my nodes with MYSBootloader. I am still testing before I change all the nodes

@tekka I doing this and still the node ID is not changing. I change this node to 4 and it still come up as Node 3. The reboot command also don't reboot the device. I have to do a manual reset on the device is this normal?

@tekka the reason I asked I has a problem where I had 2 node with the same node ID and a could not do a OTA via MYSController. As i keep the same ID. I clear the EEPROM and still l it did not work. So the only why I could get the node working was to reflash the boot loader.

@tekka once you flash the Arduino with the MYSBootloader is the only why that now you can programme the Arduino is though the MYSController software?

Hi All I am just getting the following message in the serial monitor and I don't know why. All the other sensor that I connect to Domoticz work it just happen from yesterday when I try to add a new sensors.

find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
sensor started, id=10, parent=255, distance=255
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
find parent```

@BulldogLowell this looks great once you complete it I will print it. Only problem our raining session is over till Dec. But I can start the build so long :).

@petewill I add a light sensor to your sketch and this now slow everything down what will the reason for this be? The motion sensor will not always pickup motion. I have another node with light and motion sensor and that is working right.

Here is the code:

/***
 * 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.
 * 
 * DESCRIPTION
 * This sketch provides a Dimmable LED Light using PWM and based Henrik Ekblad 
 * <henrik.ekblad@gmail.com> Vera Arduino Sensor project.  
 * Developed by Bruce Lacey, inspired by Hek's MySensor's example sketches.
 * 
 * The circuit uses a MOSFET for Pulse-Wave-Modulation to dim the attached LED or LED strip.  
 * The MOSFET Gate pin is connected to Arduino pin 3 (MIRROR_LED_PIN), the MOSFET Drain pin is connected
 * to the LED negative terminal and the MOSFET Source pin is connected to ground.  
 *
 * This sketch is extensible to support more than one MOSFET/PWM dimmer per circuit.
 *
 * REVISION HISTORY
 * Version 1.0 - February 15, 2014 - Bruce Lacey
 * Version 1.1 - February 4, 2014 - Pete B - added buttons to control on/off and dim level and a motion sensor
 ***/
 
 
#define SN "Mirror LED with PIR and LDR"
#define SV "1.2"
#define NODE_ID 50  //change to a number to assign a specific ID

#include <SPI.h>
#include <MySensor.h>
#include <Bounce2.h>
#include <MySigningNone.h>
#include <MyTransportNRF24.h>
#include <MyHwATMega328.h>

#define MIRROR_LED_CHILD 0    //ID of the LED child
#define MOTION_CHILD 1  //ID of the motion sensor child
#define CHILD_ID_LIGHT 2 //ID for LDR sensor

#define LIGHT_SENSOR_ANALOG_PIN 0

// NRFRF24L01 radio driver (set low transmit power by default) 
MyTransportNRF24 radio(RF24_CE_PIN, RF24_CS_PIN, RF24_PA_LEVEL_GW);  

#define MIRROR_LED_PIN 3      // Arduino pin attached to MOSFET Gate pin
#define UP_BUTTON_PIN 8  // Arduino Digital I/O pin number for the fade up button 
#define DOWN_BUTTON_PIN 7  // Arduino Digital I/O pin number for the fade down button 
#define POWER_BUTTON_PIN 4  // Arduino Digital I/O pin number for the power button 
#define MOTION_PIN  6  // Arduino pin tied to trigger pin on the motion sensor.

#define FADE_DELAY 10  // Delay in ms for each percentage fade up/down (10ms = 1s full-range dim)
#define FADE_PERCENTAGE 10 //The percentage the fade level will be changed when a button is pressed

MyHwATMega328 hw;
// Construct MySensors library
MySensor gw(radio, hw);

//MySensor gw; //Don't need to define pins unless they are changing from the default

static int currentLevel = 0;  // Current dim level...
uint8_t fadeLevel = 0; //used to store the fade level when using the buttons
uint8_t upPreviousValue;
uint8_t downPreviousValue;
uint8_t powerPreviousValue;

Bounce upDebouncer = Bounce();
Bounce downDebouncer = Bounce();
Bounce powerDebouncer = Bounce();

//motion sensor
uint8_t lastMotion = 0;


unsigned long previousMillis = 0; // last time update //see http://stackoverflow.com/questions/10773425/performing-a-function-after-x-time for more details on this
unsigned long motionDelay = 10000; // interval at which to keep motion sensor trippped (milliseconds).  Used to prevent too frequent updates to Vera. 
unsigned long upPreviousMillis = 0;
unsigned long downPreviousMillis = 0; 
unsigned long buttonFadeDelay = 200; 
int lastLightLevel;

boolean metric = true; 

MyMessage motionMsg(MOTION_CHILD, V_TRIPPED);
MyMessage dimmerMsg(MIRROR_LED_CHILD, V_DIMMER);
MyMessage msg(CHILD_ID_LIGHT, V_LIGHT_LEVEL);
//MyMessage lightMsg(LED_CHILD, V_LIGHT);  removed, updating with dimmer values only

/***
 * Dimmable LED initialization method
 */
void setup()  
{ 
  Serial.println( SN ); 

  gw.begin( incomingMessage,  NODE_ID);

  // Register the LED Dimmable Light with the gateway
  gw.present(MIRROR_LED_CHILD, S_DIMMER );
  gw.present(MOTION_CHILD, S_MOTION);
  gw.present(CHILD_ID_LIGHT, S_LIGHT_LEVEL);
  
  // Send the sketch version information to the gateway and Controller
  gw.sendSketchInfo(SN, SV);
  
  metric = gw.getConfig().isMetric;
  
 
   // Setup the button
  pinMode(UP_BUTTON_PIN,INPUT);
  pinMode(DOWN_BUTTON_PIN,INPUT);
  pinMode(POWER_BUTTON_PIN,INPUT);
  
  // Activate internal pull-up
  digitalWrite(UP_BUTTON_PIN,HIGH);
  digitalWrite(DOWN_BUTTON_PIN,HIGH);
  digitalWrite(POWER_BUTTON_PIN,HIGH);
  
  // After setting up the button, setup debouncer
  upDebouncer.attach(UP_BUTTON_PIN);
  downDebouncer.attach(DOWN_BUTTON_PIN);
  powerDebouncer.attach(POWER_BUTTON_PIN);
  upDebouncer.interval(5);
  downDebouncer.interval(5);
  powerDebouncer.interval(5);
  

}

/***
 *  Dimmable LED main processing loop 
 */
void loop() 
{
  
  
  
  //process the LED commands from gateway
  gw.process();
  
 int lightLevel = (1023-analogRead(LIGHT_SENSOR_ANALOG_PIN))/10.23; 
 // Serial.println(lightLevel);
  if (lightLevel != lastLightLevel) {
      gw.send(msg.set(lightLevel));
      lastLightLevel = lightLevel;
  }  
 
 
  //motion sensor code
  unsigned long currentMillis = millis();
  
     if(currentMillis - previousMillis > motionDelay){
      uint8_t motionDetect = digitalRead(MOTION_PIN);
  
      if(motionDetect != lastMotion){
//        Serial.print("motionDetect Value: ");
//        Serial.println(motionDetect);
        gw.send(motionMsg.set(motionDetect));  // Send tripped value to gw
        
        if(motionDetect == 1){
          previousMillis = currentMillis;  //"Tripped" delay 
        }
        else{
          previousMillis = currentMillis - motionDelay + 1000; //"Not tripped" delay for 1 second to stop rapid "not tripped" and "tripped" updates to Vera
        }
  
         lastMotion = motionDetect; 
      }    
    }

  
/*
There are 3 buttons attached to the mirror.  One is an on/off button and the other two will fade up/fade down.  
The sensor will remember the last fade state and fade the lights to that level next time they are turned on.

If fade up or fade down button is pressed it should store that value into a variable and when the ON button is pressed
it will fade to that previous value.
 */ 

    upDebouncer.update();
    // Get the update value
    uint8_t upValue = upDebouncer.read();
    
    unsigned long upCurrentMillis = millis();
    
    if(upCurrentMillis - upPreviousMillis > buttonFadeDelay){
      if ((upValue == LOW) && (fadeLevel<100)) { //Because of the internal pullup resistors LOW = button is presssed
      
        fadeLevel += FADE_PERCENTAGE;
        fadeLevel = fadeLevel > 100 ? 100 : fadeLevel;
        fadeToLevel( fadeLevel );
        
      }
      upPreviousMillis = upCurrentMillis;
    }
  
    downDebouncer.update();
    // Get the update value
    uint8_t downValue = downDebouncer.read();
    
    unsigned long downCurrentMillis = millis();
    
    if(downCurrentMillis - downPreviousMillis > buttonFadeDelay){
      if ((downValue == LOW) && (fadeLevel>0)) {
        
        fadeLevel -= FADE_PERCENTAGE;
        fadeLevel = fadeLevel < 0 ? 0 : fadeLevel;
        //powerState = fadeLevel; //Remember fade level for when power button is pressed
        fadeToLevel( fadeLevel );
        
      }
      downPreviousMillis = downCurrentMillis;
    }
      
    powerDebouncer.update();
    // Get the update value
    uint8_t powerValue = powerDebouncer.read();
    
    if(powerValue != powerPreviousValue){
      if (powerValue == LOW) {
      Serial.print("Power Button Pressed. fadeLevel is ");
      Serial.println(fadeLevel);
        if (currentLevel > 0) {
          fadeToLevel( 0 );
        }
        else{
          if (fadeLevel == 0) {
            fadeToLevel(50);
            fadeLevel = 50;
          }
          else{
            fadeToLevel(fadeLevel);
          }
        }
      }
      powerPreviousValue = powerValue;
    }
  
   
}

void incomingMessage(const MyMessage &message) {
  if (message.type == V_LIGHT || message.type == V_DIMMER) {
    
    //  Retrieve the power or dim level from the incoming request message
    int requestedLevel = atoi( message.data );
    
    // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on]
    requestedLevel *= ( message.type == V_LIGHT ? 100 : 1 );
    
    // Clip incoming level to valid range of 0 to 100
    requestedLevel = requestedLevel > 100 ? 100 : requestedLevel;
    requestedLevel = requestedLevel < 0   ? 0   : requestedLevel;
    
//    Serial.print( "Changing level to " );
//    Serial.print( requestedLevel );
//    Serial.print( ", from " ); 
//    Serial.println( currentLevel );

    fadeToLevel( requestedLevel );
    }
}

/***
 *  This method provides a graceful fade up/down effect
 */
void fadeToLevel( int toLevel ) {

//  Serial.print("toLevel Value: ");
//  Serial.println(toLevel);
//  Serial.print("currentLevel Value: ");
//  Serial.println(currentLevel);
  
  int delta = ( toLevel - currentLevel ) < 0 ? -1 : 1;
  
  while ( currentLevel != toLevel ) {
    currentLevel += delta;
    analogWrite( MIRROR_LED_PIN, (int)(currentLevel / 100. * 255) );
    delay( FADE_DELAY );
  }

   // Inform the gateway of the current DimmableLED's SwitchPower1 and LoadLevelStatus value...
  //gw.send(lightMsg.set(currentLevel > 0 ? 1 : 0));  //used to send status of light (on/off) to Vera
  gw.send( dimmerMsg.set(currentLevel) );
}

@mikemayers have a look at this forum link for a dimmable led with buttons it works great
http://forum.mysensors.org/topic/936/backlit-dimmable-led-mirror-with-motion-sensor

@tekka I update my bootloader to MYSbootloader and the fuses as per the doc but now when I try to program the Arduino mini pro I get this error can you help?

@C.r.a.z.y. I have 10 nodes running at this stage and it is very fast. What in the gui don't you like?

Hi I am using PiDome although it's still in alfa stage it is really easy to setup as it integrated nicely with MySensor nodes and it just works. I try OpenHab and never get it to work right with MySensor maybe it is just to complex to setup and to do rule for automatic for me it is to complex

Hi I just complete and compile the pulse power-meter on lib 1.4.1 and I don't get any values back from the sensor. The pulse sensor is wire as per the instruction what can the problem be here?

Here is the info from the serial port:

send: 21-21-0-0 s=255,c=3,t=11,pt=0,l=12,sg=0,st=ok:Energy Meter
send: 21-21-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.0
send: 21-21-0-0 s=1,c=0,t=13,pt=0,l=5,sg=0,st=ok:1.4.1
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:
send: 21-21-0-0 s=1,c=2,t=24,pt=0,l=0,sg=0,st=ok:

@ntruschsess

I am getting this compile error when I compile the MQTT Client gateway on lib1.4.1.

In file included from MQTTClientGateway.ino:63:0:
MyMQTTClient.h:43:35: error: 'RF24_PA_LEVEL_GW' was not declared in this scope
void begin(rf24_pa_dbm_e paLevel=RF24_PA_LEVEL_GW, uint8_t channel=RF24_CHANNEL, rf24_datarate_e dataRate=RF24_DATARATE, uint8_t _rx=6, uint8_t _tx=5, uint8_t _er=4 );
^
MQTTClientGateway.ino: In function 'void setup()':
MQTTClientGateway.ino:136:12: error: 'RF24_PA_LEVEL_GW' was not declared in this scope
Error compiling.

Hi I got this sketch to work. There must have being something wrong with MySensor library 1.4.1 once I re-install it and recompile the sketch it is working.

@hek this is the sketch from about that that copy and recompile on 1.4.1. I did not used the codebender to compile the sketch.

This is the serial info on the MQTT Gateway:
0;0;3;0;9;read: 25-25-0 s=255,c=0,t=17,pt=0,l=5:1.4.1
0;0;3;0;9;read: 25-25-0 s=255,c=3,t=6,pt=1,l=1:0
0;0;3;0;9;send: 0-0-25-25 s=255,c=3,t=6,pt=0,l=1,st=ok:M
0;0;3;0;9;read: 25-25-0 s=0,c=0,t=4,pt=0,l=5:1.4.1
0;0;3;0;9;read: 25-25-0 s=1,c=0,t=1,pt=0,l=5:1.4.1
0;0;3;0;9;read: 25-25-0 s=255,c=3,t=11,pt=0,l=10:Mirror LED
MyMQTT/25/255/V_SKETCH_NAME
30 27 00 1B 4D 79 4D 51 54 54 2F 32 35 2F 32 35 35 2F 56 5F 53 4B 45 54 43 48 5F 4E 41 4D 45 4D 69 72 72 6F 72 20 4C 45 44
0;0;3;0;9;read: 25-25-255 s=255,c=3,t=7,pt=0,l=0:
0;0;3;0;9;send: 0-0-25-25 s=255,c=3,t=8,pt=1,l=1,st=ok:1
0;0;3;0;9;read: 0-25-25 s=255,c=3,t=8,pt=1,l=1:1
0;0;3;0;9;send: 0-0-25-25 s=255,c=3,t=8,pt=1,l=1,st=ok:1

@hek Yes I am using 1.4.1 on both the sensor. This the error I am getting on the sensor node: The sensor was working on a different node it also has cap on VCC and GRD.

sensor started, id=25, parent=0, distance=2
send: 25-25-0-0 s=255,c=0,t=17,pt=0,l=5,st=fail:1.4.1
send: 25-25-0-0 s=255,c=3,t=6,pt=1,l=1,st=fail:0
read: 0-0-25 s=255,c=3,t=6,pt=0,l=1:M
send: 25-25-0-0 s=0,c=0,t=4,pt=0,l=5,st=fail:1.4.1
send: 25-25-0-0 s=1,c=0,t=1,pt=0,l=5,st=fail:1.4.1
send: 25-25-0-0 s=255,c=3,t=11,pt=0,l=10,st=fail:Mirror LED
lost parent
find parent
send: 25-25-255-255 s=255,c=3,t=7,pt=0,l=0,st=bc:
read: 0-0-25 s=255,c=3,t=8,pt=1,l=1:1
new parent=0, d=2

@petewill under what version of mysensor library did you compile this sketch library 1.4 or 1.4.1? I compile you sketch under 1.4.1 and cannot get it to work

Francois

@hek if I compile the sketch without that argument (9,10) the sensor is not working.

@hek I alos runs IDE 1.5.8

Yes it compiles if I only have it like this;

MySensor gw;

What is the values in the brakes for?

@hek yes I did restart the IDE after installing. I did compile out sketches and the all work I only have an problem with this one.

@hek I am getting the following error when I compile this sketch under Mysensor ver 1.4.1. what can the problem be. If I do i on ver 1.4 it works

DimmableLEDActuator.ino:33:17: error: no matching function for call to 'MySensor::MySensor(int, int)'
DimmableLEDActuator.ino:33:17: note: candidates are:
In file included from DimmableLEDActuator.ino:26:0:
E:\ardruino progammes\libraries\MySensors/MySensor.h:79:2: note: MySensor::MySensor()
MySensor();
^
E:\ardruino progammes\libraries\MySensors/MySensor.h:79:2: note: candidate expects 0 arguments, 2 provided
E:\ardruino progammes\libraries\MySensors/MySensor.h:70:7: note: MySensor::MySensor(const MySensor&)
class MySensor
^
E:\ardruino progammes\libraries\MySensors/MySensor.h:70:7: note: candidate expects 1 argument, 2 provided
Error compiling.

@filoucaenais I starting to play with Jeedom but I am not getting my sensor to display Do Jeedom have an auto discovery? As per the Main Plugin MySensor Ethernet gateway is up and running but when I goto the Plugins Automation Protocols Mysensors there is no nodes showing up why will this be the case?

@BulldogLowell do you mind sharing the sketch I not seeing in this forum or on the Build pages of MySensor.org

@bjornhallberg can you measure the voltage on your batteries it will be great to know what you're voltage are.

@BulldogLowell I also busy building an rain gauge. How is your one performing? Now did you set this up in the arduino? How did you do the calculation?

Regards

Francois

At first I didn't understand why this was happening I was thinking it could be voltage but was not sure till I see this discussion now I know if the voltage get to 3v its time to replace the battery's.

I have the same problem as long as the voltage is above 3v the sensors work right. The moment the voltage get to 2.98v I get false triggers. I run my sensor of 2 aa battery's and my sensor is setup as per this forum link http://forum.mysensors.org/topic/225/hc-sr501-motion-sensor/13. I order a step up voltage supply to see if it this will solve the problem once the battery goes below 3v.

@petewill Great video when are you planning in doing the power monitoring for this project?

@ToSa I am running this version and I don't have any problems with it so far. I only have one node up and running with a humility sensor. I order 5 more Anarduino units and hope to get them in Jan so will do more testing then. The humility node is up and running now for more than 3 weeks with out any resets.

Merry Xmas and happy new year thanks for all the support from everyone

@ToSa do you see the RFM69 only work on the serial gateway or will it also work on the MQTT gateway?

@John I never skip an release the moment there is new release I installed.

@John I must say that you product is getting better with every release. This new discovery process that you now add is making things ever easier to add sensors to the system Thanks for all the hard work that you are putting into this project. I real appreciate this. Keep up the good work. You product just work and I don't have to worries about it.

@John This version (510) fix the issue and it did discovered the sensor. Thanks

@John yes it is also not in discovery

@John download the ver509 and still doing the same thing.

@John Hi my system was running fine till I what to add more sensor. Pidome do see the sensor but do not present the it in the "New nodes presentation" or the new "Discovered device". I can add the new nodes manually and that works. I am on version 508

here is info from the applog file:

Hi have a look at nodered http://nodered.org. Easy to setup work flows and can run on any platform.

Hi I now have my first MySensor RFM69 node up and running in PiDome This is great as with the NFR24L01 I battle to get coverage in my House. I put the RFm69 node in the farthest point in my house any it just work. To get the NFR24L01+ to work at the same location I have to use an repeater node. The other thing I like about the RFM69 solution like Moteino (https://lowpowerlab.com) or Anarduino (http://www.anarduino.com/miniwireless) is the size you don't have to use any wires to connected the radio and it comes fitted to the arduino board. So if you look for a small sensor I think that this is the way to go for automation.

@hek It looks to me that all the activity that happen on getting the RFM69 integrated as part of the Mysensor ecosystem is dying. Can we not see if we can talk to Felix from Lowpower (https://lowpowerlab.com/) to see if he is not willing to get his Moteino integters as part of the MySensor ecosystem. Here is the tread on his forum where I asked him about this. https://lowpowerlab.com/forum/index.php/topic,542.0.html

@daulagari what ranges do you get on the NRF2401 without having and repeater in you network? I do have a 4.7uf cap on all my radio's. At this stage am also have debugging on on all my sensor while in dev phase of testing all the sensor.