I also just order my gateway 
Francois
@Francois
Best posts made by Francois
- 
    RE: Which is better: RFM69 or NRF24L01+?posted in HardwareHi 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: 
 
- 
    RE: Rain Guageposted in My Project@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 :). 
- 
    RE: Which is better: RFM69 or NRF24L01+?posted in Hardware@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. 
- 
    RE: Which is better: RFM69 or NRF24L01+?posted in Hardware@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. 
- 
    RE: Which is better: RFM69 or NRF24L01+?posted in Hardware@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. 
Latest posts made by Francois
- 
    RE: NodeManger with motion sensorposted in NodeManagerHI @user2684 thanks for that is is working now  
- 
    NodeManger with motion sensorposted in NodeManagerHi @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 
- 
    No seeing BH1750 sensor in Home Assistantposted in Home AssistantHi 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:11Log 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]```
- 
    RE: Serial Gateway Beta version 2 not Sending data on the RFM69 radioposted in Bug ReportsThank @hek this fix my problem as I was using 8Mhz Arduino mini pro as a gateway. 
- 
    Serial Gateway Beta version 2 not Sending data on the RFM69 radioposted in Bug ReportsHi @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 
- 
    RE: openHAB 2.0 bindingposted in OpenHAB@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. 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!
- 
    RE: openHAB 2.0 bindingposted in OpenHAB@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? 
- 
    RE: openHAB 2.0 bindingposted in OpenHAB@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 
- 
    RE: openHAB 2.0 bindingposted in OpenHAB@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