Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. alterfritz
    3. Posts
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by alterfritz

    • RE: Flashed mysensors dev branch to my sensors - not showing up in home assistant

      Thanks. I will do that...

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Flashed mysensors dev branch to my sensors - not showing up in home assistant

      Correct - I flashed it some time ago - actually I detect 1 min. ago if I remove some parts of the config ...

      customize:

      light.WallLight1_1_1:

      friendly_name: WallLight 1

      light.WallLight6_6_1:

      friendly_name: WallLight 2

      light.WallLight3_3_1:

      friendly_name: WallLight 3

      light.WallLight4_4_1:

      friendly_name: WallLight 4

      light.WallLight5_5_1:

      friendly_name: WallLight 5

      group.Wall_Lights:

      friendly_name: Wandleuchten

      the light appear ... I think I can get it working.

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Flashed mysensors dev branch to my sensors - not showing up in home assistant

      WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {3: '100'}: light platform: node 6 child 1: S_DIMMER requires value_type V_STATUS @ data[2]

      That one seems wrong - but if possible I simply want to switch on / off the lights, no dimmer needed if I can avoid flashing the sensors again.

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Flashed mysensors dev branch to my sensors - not showing up in home assistant

      I'm trying both the raspi mqtt and the esp8266 mqtt gateway. I have flashed the dev 2.1.1 branch towards a set of arduino pro mini led light, communication seems to work - I can see the sensors publishing towards mqtt.

      My config in configuration.yaml:

      ...
      mysensors:
      gateways:
      - device: mqtt
      persistence_file: '/home/homeassistant/.homeassistant/mysensors.json'
      topic_in_prefix: 'mysensors-out'
      topic_out_prefix: 'mysensors-in'
      optimistic: false
      persistence: true
      retain: true
      version: '2.0'
      ...

      When I switch on the lights, I see messages appear on the mqtt:

      mysensors-out/1/255/0/0/17 2.2.0-beta
      mysensors-out/1/255/3/0/6 0
      mysensors-in/1/255/3/0/6 M
      mysensors-out/1/255/3/0/11 WallLight1
      mysensors-out/1/255/3/0/12 1.0
      mysensors-out/1/1/0/0/4 (null)
      mysensors-out/1/1/1/0/3 100
      mysensors-out/6/255/0/0/17 2.2.0-beta
      mysensors-out/6/255/3/0/6 0
      mysensors-out/5/255/0/0/17 2.2.0-beta
      mysensors-out/5/255/3/0/6 0
      mysensors-in/6/255/3/0/6 M
      mysensors-in/5/255/3/0/6 M
      mysensors-out/6/255/3/0/11 WallLight6
      mysensors-out/6/255/3/0/12 1.0
      mysensors-out/6/1/0/0/4 (null)
      mysensors-out/5/255/3/0/12 1.0
      mysensors-out/5/1/0/0/4 (null)
      mysensors-out/5/1/1/0/3 100
      mysensors-out/6/255/0/0/17 2.2.0-beta
      mysensors-out/5/1/1/0/3 100
      mysensors-out/6/1/1/0/3 100
      mysensors-out/6/1/1/0/3 100
      mysensors-out/3/255/3/0/6 0
      mysensors-in/3/255/3/0/6 M
      mysensors-out/3/1/0/0/4 (null)
      mysensors-out/3/1/1/0/3 100
      mysensors-out/3/255/3/0/6 0
      mysensors-in/3/255/3/0/6 M
      mysensors-out/3/255/3/0/11 WallLight3
      mysensors-out/3/255/3/0/12 1.0
      mysensors-out/4/255/0/0/17 2.2.0-beta
      mysensors-out/4/255/3/0/6 0
      mysensors-in/4/255/3/0/6 M
      mysensors-out/4/1/0/0/4 (null)
      mysensors-out/4/1/1/0/3 100
      mysensors-out/4/255/0/0/17 2.2.0-beta
      mysensors-out/4/255/3/0/6 0
      mysensors-in/4/255/3/0/6 M
      mysensors-out/4/255/3/0/11 WallLight4
      mysensors-out/4/255/3/0/12 1.0

      However - they do not show up ... home assistant log shows like this...💯

      Jan 22 18:03:57 pi hass[744]: 2018-01-22 18:03:57 DEBUG (Thread-6) [mysensors.gateway_mqtt] Receiving 4;255;3;0;27;WallLight4
      Jan 22 18:03:57 pi hass[744]: 2018-01-22 18:03:57 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 4 child 255
      Jan 22 18:03:57 pi hass[744]: 2018-01-22 18:03:57 DEBUG (Thread-13) [homeassistant.components.mysensors] Not a child update for node 4
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 DEBUG (Thread-4) [mysensors.gateway_mqtt] Receiving 4;255;3;0;11;WallLight4
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 4 child 255
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 DEBUG (Thread-13) [homeassistant.components.mysensors] Not a child update for node 4
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 DEBUG (Thread-9) [mysensors.gateway_mqtt] Receiving 1;1;1;0;3;100
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 1 child 1
      Jan 22 18:03:58 pi hass[744]: 2018-01-22 18:03:58 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {19: '356', 3: '100'}: light platform: node 1 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:03:59 pi hass[744]: 2018-01-22 18:03:59 DEBUG (Thread-7) [mysensors.gateway_mqtt] Receiving 1;1;1;0;3;100
      Jan 22 18:03:59 pi hass[744]: 2018-01-22 18:03:59 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 1 child 1
      Jan 22 18:03:59 pi hass[744]: 2018-01-22 18:03:59 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {19: '356', 3: '100'}: light platform: node 1 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-10) [mysensors.gateway_mqtt] Receiving 4;1;1;0;3;100
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 4 child 1
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {3: '100'}: light platform: node 4 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-8) [mysensors.gateway_mqtt] Receiving 4;1;1;0;3;100
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 4 child 1
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {3: '100'}: light platform: node 4 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-5) [mysensors.gateway_mqtt] Receiving 4;1;1;0;3;100
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 4 child 1
      Jan 22 18:04:00 pi hass[744]: 2018-01-22 18:04:00 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {3: '100'}: light platform: node 4 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:04:03 pi hass[744]: 2018-01-22 18:04:03 INFO (MainThread) [homeassistant.components.http] Serving /description.xml to 192.168.10.211 (auth: True)
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-11) [mysensors.gateway_mqtt] Receiving 6;255;0;0;17;2.2.0-beta
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-3) [mysensors.gateway_mqtt] Receiving 6;255;3;0;6;0
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [mysensors.gateway_mqtt] Publishing 6;255;3;0;6;M
      Jan 22 18:04:04 pi hass[744]:
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1972866000-41, domain=mqtt, service=publish, service_data=payload=M, topic=mysensors-in/6/255/3/0/6, qos=0, retain=True>
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1972866000-41>
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-9) [mysensors.gateway_mqtt] Receiving 6;255;3;0;11;WallLight6
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-2) [mysensors.gateway_mqtt] Receiving 6;255;3;0;12;1.0
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-4) [mysensors.gateway_mqtt] Receiving 6;1;0;0;4;
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-7) [mysensors.gateway_mqtt] Receiving 6;1;1;0;3;100
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 6 child 255
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [homeassistant.components.mysensors] Not a child update for node 6
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 6 child 255
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [homeassistant.components.mysensors] Not a child update for node 6
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 WARNING (Thread-13) [mysensors] child_id 1 already exists in children of node 6, cannot add child
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [homeassistant.components.mysensors] Node update: node 6 child 1
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 WARNING (Thread-13) [homeassistant.components.mysensors] Invalid values: {3: '100'}: light platform: node 6 child 1: S_DIMMER requires value_type V_STATUS @ data[2]
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-10) [mysensors.gateway_mqtt] Receiving 6;255;0;0;17;2.2.0-beta
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-8) [mysensors.gateway_mqtt] Receiving 6;255;3;0;6;0
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 DEBUG (Thread-13) [mysensors.gateway_mqtt] Publishing 6;255;3;0;6;M
      Jan 22 18:04:04 pi hass[744]:
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1972866000-42, domain=mqtt, service=publish, service_data=payload=M, topic=mysensors-in/6/255/3/0/6, qos=0, retain=True>
      Jan 22 18:04:04 pi hass[744]: 2018-01-22 18:04:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1972866000-42>
      Jan 22 18:04:05 pi hass[744]: 2018-01-22 18:04:05 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.balcony to 192.168.10.6 (auth: True)
      Jan 22 18:04:05 pi hass[744]: 2018-01-22 18:04:05 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.cellar to 192.168.10.6 (auth: True)
      Jan 22 18:04:12 pi hass[744]: 2018-01-22 18:04:12 INFO (MainThread) [homeassistant.components.http] Serving /description.xml to 192.168.10.211 (auth: True)
      Jan 22 18:04:15 pi hass[744]: 2018-01-22 18:04:15 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.balcony to 192.168.10.6 (auth: True)
      Jan 22 18:04:15 pi hass[744]: 2018-01-22 18:04:15 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.cellar to 192.168.10.6 (auth: True)

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Flashed mysensors dev branch to my sensors - not showing up in home assistant

      If possible I would avoid to rip all apart and refash...

      posted in Troubleshooting
      alterfritz
      alterfritz
    • Flashed mysensors dev branch to my sensors - not showing up in home assistant

      Hi,

      I wounding how I can do static configuration in home assistant?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Seems this does the trick. Thanks!

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Many thanks - yes, will do today. Let you know results.

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Just to let you know - I have uploaded the ESP8266 sketch (from 2.1.1) via Arduino IDE, seems to run stable with the same NRF24L01 module.

      But if possible I would like to go back to have all run on the raspi.

      Again thanks for all that support here!

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Thanks a lot. Looking forward to any update... have a nice weekend, I will try the version for ESP8266 in the meantime, however run it on the pi would be preferred.

      Thanks again!

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      until it crashes...

      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=3
      mysgw: TSF:PNG:SEND,TO=0
      mysgw: TSF:CKU:OK
      mysgw: TSF:MSG:GWL OK

      Program received signal SIGSEGV, Segmentation fault.
      [Switching to Thread 0x75cc8450 (LWP 4759)]
      0x0001ac74 in RF24_spiMultiByteTransfer (readMode=true, len=6 '\006', buf=0x1 <error: Cannot access memory at address 0x1>, cmd=97 'a') at ./drivers/RF24/RF24.cpp:87
      87 *buf++ = *prx++;

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Here is another screenshot - seems that sometimes it works... for some time...

      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
      mysgw: GWT:TPS:TOPIC=mysensors-out/1/255/3/0/6,MSG SENT
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
      mysgw: TSF:MSG:PINGED,ID=6,HP=1
      mysgw: TSF:MSG:SEND,0-0-6-6,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-6-6,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.2.0-beta
      mysgw: GWT:TPS:TOPIC=mysensors-out/6/255/0/0/17,MSG SENT
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
      mysgw: GWT:TPS:TOPIC=mysensors-out/6/255/3/0/6,MSG SENT
      mysgw: TSF:MSG:READ,5-5-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.2.0-beta
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/255/0/0/17,MSG SENT
      mysgw: TSF:MSG:READ,5-5-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/255/3/0/6,MSG SENT
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=11,pt=0,l=10,sg=0:WallLight1
      mysgw: GWT:TPS:TOPIC=mysensors-out/1/255/3/0/11,MSG SENT
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
      mysgw: GWT:TPS:TOPIC=mysensors-out/1/255/3/0/12,MSG SENT
      mysgw: TSF:MSG:READ,1-1-0,s=1,c=0,t=4,pt=0,l=0,sg=0:
      mysgw: GWT:TPS:TOPIC=mysensors-out/1/1/0/0/4,MSG SENT
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,1-1-0,s=1,c=1,t=3,pt=2,l=2,sg=0:100
      mysgw: GWT:TPS:TOPIC=mysensors-out/1/1/1/0/3,MSG SENT
      mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=3
      mysgw: TSF:CKU:OK,FCTRL
      mysgw: TSF:MSG:GWL OK
      mysgw: TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
      mysgw: TSF:MSG:READ,4-4-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=4
      mysgw: TSF:CKU:OK,FCTRL
      mysgw: TSF:MSG:GWL OK
      mysgw: TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=11,pt=0,l=10,sg=0:WallLight6
      mysgw: GWT:TPS:TOPIC=mysensors-out/6/255/3/0/11,MSG SENT
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
      mysgw: GWT:TPS:TOPIC=mysensors-out/6/255/3/0/12,MSG SENT
      mysgw: TSF:MSG:READ,6-6-0,s=1,c=0,t=4,pt=0,l=0,sg=0:
      mysgw: GWT:TPS:TOPIC=mysensors-out/6/1/0/0/4,MSG SENT
      mysgw: TSF:MSG:READ,6-6-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
      mysgw: !TSF:MSG:SEND,0-0-6-6,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=NACK:1
      mysgw: TSF:MSG:READ,5-5-0,s=255,c=3,t=11,pt=0,l=10,sg=0:WallLight5
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/255/3/0/11,MSG SENT
      mysgw: TSF:MSG:READ,5-5-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/255/3/0/12,MSG SENT
      mysgw: TSF:MSG:READ,5-5-0,s=1,c=0,t=4,pt=0,l=0,sg=0:
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/1/0/0/4,MSG SENT
      mysgw: TSF:MSG:READ,5-5-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
      mysgw: TSF:MSG:SEND,0-0-5-5,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,5-5-0,s=1,c=1,t=3,pt=2,l=2,sg=0:100
      mysgw: GWT:TPS:TOPIC=mysensors-out/5/1/1/0/3,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
      mysgw: TSF:MSG:PINGED,ID=3,HP=1
      mysgw: TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.2.0-beta
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/255/0/0/17,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/255/3/0/6,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
      mysgw: TSF:MSG:PINGED,ID=4,HP=1
      mysgw: TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=11,pt=0,l=10,sg=0:WallLight3
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/255/3/0/11,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/255/3/0/12,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=1,c=0,t=4,pt=0,l=0,sg=0:
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/1/0/0/4,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
      mysgw: TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.2.0-beta
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/255/0/0/17,MSG SENT
      mysgw: TSF:MSG:READ,3-3-0,s=1,c=1,t=3,pt=2,l=2,sg=0:100
      mysgw: GWT:TPS:TOPIC=mysensors-out/3/1/1/0/3,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/255/3/0/6,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=11,pt=0,l=10,sg=0:WallLight4
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/255/3/0/11,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/255/3/0/12,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=1,c=0,t=4,pt=0,l=0,sg=0:
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/1/0/0/4,MSG SENT
      mysgw: TSF:MSG:READ,4-4-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
      mysgw: TSF:MSG:SEND,0-0-4-4,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
      mysgw: TSF:MSG:READ,4-4-0,s=1,c=1,t=3,pt=2,l=2,sg=0:100
      mysgw: GWT:TPS:TOPIC=mysensors-out/4/1/1/0/3,MSG SENT

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      pi@pi:~ $ sudo gdb /home/pi/mysensors_dev/MySensors/bin/mysgw
      GNU gdb (Raspbian 7.7.1+dfsg-5+rpi1) 7.7.1
      Copyright (C) 2014 Free Software Foundation, Inc.
      License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law. Type "show copying"
      and "show warranty" for details.
      This GDB was configured as "arm-linux-gnueabihf".
      Type "show configuration" for configuration details.
      For bug reporting instructions, please see:
      http://www.gnu.org/software/gdb/bugs/.
      Find the GDB manual and other documentation resources online at:
      http://www.gnu.org/software/gdb/documentation/.
      For help, type "help".
      Type "apropos word" to search for commands related to "word"...
      Reading symbols from /home/pi/mysensors_dev/MySensors/bin/mysgw...done.
      (gdb) run -d
      Starting program: /home/pi/mysensors_dev/MySensors/bin/mysgw -d
      [Thread debugging using libthread_db enabled]
      Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
      mysgw: Starting gateway...
      mysgw: Protocol version - 2.2.0-rc.2
      mysgw: MCO:BGN:INIT GW,CP=RNNGL-Q-,VER=2.2.0-rc.2
      mysgw: TSF:LRT:OK
      mysgw: TSM:INIT
      mysgw: TSF:WUR:MS=0
      [New Thread 0x75cc8450 (LWP 4703)]
      mysgw: TSM:INIT:TSP OK
      mysgw: TSM:INIT:GW MODE
      mysgw: TSM:READY:ID=0,PAR=0,DIS=0
      mysgw: MCO:REG:NOT NEEDED
      mysgw: MCO:BGN:STP
      mysgw: MCO:BGN:INIT OK,TSP=1
      mysgw: GWT:RMQ:MQTT RECONNECT
      mysgw: connected to 127.0.0.1
      mysgw: GWT:RMQ:MQTT CONNECTED
      mysgw: GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
      mysgw: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=3
      mysgw: TSF:PNG:SEND,TO=0
      mysgw: TSF:CKU:OK
      mysgw: TSF:MSG:GWL OK

      Program received signal SIGSEGV, Segmentation fault.
      [Switching to Thread 0x75cc8450 (LWP 4703)]
      0x0001ac74 in RF24_spiMultiByteTransfer (readMode=true, len=6 '\006', buf=0x1 <error: Cannot access memory at address 0x1>, cmd=97 'a') at ./drivers/RF24/RF24.cpp:87
      87 *buf++ = *prx++;
      (gdb)

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      Ok - thanks will do that...

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      The gateway basically stops with a segmentation fault after working ok for a few minutes... let me try it...give me a minute...

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Raspberry Pi stability problem

      I will try out the version for the ESP8266 (GatewayESP8266MQTTClient.ino), however this seems really strange to me. Any hint?

      posted in Bug Reports
      alterfritz
      alterfritz
    • Raspberry Pi stability problem

      Hi,

      running a raspi 3 with raspbian

      pi@pi:~ $ uname -a
      Linux pi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

      Have updated the system to latest status but I still have lots of stability issues with the gateway.

      I build it with

      ...

      git clone https://github.com/mysensors/MySensors.git --branch development
      cd MySensors/
      ./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-rf24-ce-pin=22 --my-rf24-cs-pin=24
      make
      cd MySensors/bin/
      sudo ./mysgw -d

      ...

      It works but very very unstable - if new sensor come online the gateway goes down with a segmentation fault.

      Its basically not usable. As mysensors have such a great reputation plus I already placed lots of sensors in my place - how I can get a mqtt gateway stable? What version? maybe some configure switches I forgot.

      I tried different pi's, different NRF24L01 modules, they have an extra capacitor etc.

      I really get frustrated and I can not believe its that unstable, so there must be something I must do wrong.

      Who has run it on a pi with out issues?

      Many thanks!
      Regards
      Joerg

      posted in Bug Reports
      alterfritz
      alterfritz
    • RE: Can't connect to radio on raspPi with latest stable 2.1.1 build, but works with 2.2.beta but with beta mqtt gateway very unstable...

      @alterfritz any update? Release 2.1.1 does not work for. Current dev branch 2.2 works.

      Any hint?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • Can't connect to radio on raspPi with latest stable 2.1.1 build, but works with 2.2.beta but with beta mqtt gateway very unstable...

      Hi, just wondering if I simple do something wrong.

      I try to setup a mysensors gateway on raspPi. What I did:

      git clone https://github.com/mysensors/MySensors.git --branch master

      ./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-rf24-ce-pin=22 --my-rf24-cs-pin=24 --my-rf24-irq-pin=15

      Build seems ok, but when I tried to start the gw, it seems radio can not be initialized. I got

      i@pi:~/msg_stable/MySensors $ sudo bin/mysgw -d
      mysgw: Starting gateway...
      mysgw: Protocol version - 2.1.1
      mysgw: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.1.1
      mysgw: TSM:INIT
      mysgw: TSF:WUR:MS=0
      mysgw: !TSM:INIT:TSP FAIL
      mysgw: TSM:FAIL:CNT=1
      mysgw: TSM:FAIL:PDT

      When I use same kind of install with the development branch 2.2.beta it all starts up, however the gateway seems very unstable (not surprisingly, as its dev build), it cashes a lot.

      So - how to get the stable 2.1.1 connecting to the radio (NRF24L01+ )? I guess the gateway on 2.1.1 is stable...

      Regards
      Joerg

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @rejoe2 Right... 🙂 I may look into this. For now I will try to get a stable version and load it without bootloader directly via usbasp...

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      So - thanks for all your help. Great forum. Let me summarize what I understand so far:

      1.) by using the before() procedbure I can execute immediately. Quickly tested. Seems perfect for me... however... 🙂
      2.) I really like this mysbootloader. But by using this it always takes up around 20 sec to boot up. There is NO way to switch on my LED directly when I power it up...

      Correct?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @rejoe2

      So
      #define MY_TRANSPORT_WAIT_READY_MS 1000
      Will wait for 1 sec?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @alterfritz

      sorry ... mean before ...like this

      void before()
      {
      analogWrite( LED_PIN,255);

      }

      This seems to have done the trick... LED switch on immediately! Thanks!

      Btw... I also try the mysbootloader. This wirless update is great, however - does this bootloader slows down bootup time?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @rejoe2 like this... btw - this forum is fanastic... responses more or less in real time... 🙂

      ...
      void presentation()
      {
      analogWrite( LED_PIN,255);

      }
      ....

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @rozpruwacz This is the way it was constructed. I plan to leave them on all time, maybe remove / replace them in the future - however if somebody uses the switches the lights should go on instantly, basically by set analogWrite( LED_PIN,255); like a normal switch.

      Any way to do so?

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @manutremo

      here it is - mostly the example... I'm using NRF24L01. Why the radio - I can check messages on gateway / mqtt (on raspPi). Took them around 10 sec to show up...

      /**

      • 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 - February 15, 2014 - Bruce Lacey
      • Version 1.1 - August 13, 2014 - Converted to 1.4 (hek)
      • 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 (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.
      • http://www.mysensors.org/build/dimmer
        */

      // Enable debug prints to serial monitor
      #define MY_DEBUG
      //#define MY_NODE_ID

      // Enable and select radio type attached
      #define MY_RADIO_NRF24
      //#define MY_RADIO_NRF5_ESB
      //#define MY_RADIO_RFM69
      //#define MY_RADIO_RFM95

      #include <MySensors.h>

      #define EPROM_LIGHT_STATE 1
      #define EPROM_DIMMER_LEVEL 2
      #define LIGHT_OFF 0
      #define LIGHT_ON 1

      #define SN "WallLight6"
      #define SV "1.0"
      #define CHILD_ID_LIGHT 1
      #define LED_PIN 3 // Arduino pin attached to MOSFET Gate pin
      #define FADE_DELAY 10 // Delay in ms for each percentage fade up/down (10ms = 1s full-range dim)

      static int16_t currentLevel = 0; // Current dim level...
      MyMessage dimmerMsg(CHILD_ID_LIGHT, V_DIMMER);
      MyMessage lightMsg(CHILD_ID_LIGHT, V_LIGHT);

      int16_t LastLightState=LIGHT_OFF;
      int16_t LastDimValue=100;

      /***

      • Dimmable LED initialization method
        */
        void setup()
        {
        // Pull the gateway's current dim level - restore light level upon sendor node power-up
        //request( CHILD_ID_LIGHT, V_DIMMER );
        //Serial.println( "Node ready to receive messages..." );

        int LightState=loadState(EPROM_LIGHT_STATE);
        if (LightState<=1) {
        LastLightState=LightState;
        int DimValue=loadState(EPROM_DIMMER_LEVEL);
        if ((DimValue>0)&&(DimValue<=100)) {
        //There should be no Dim value of 0, this would mean LIGHT_OFF
        LastDimValue=DimValue;
        }
        }

      //Here you actualy switch on/off the light with the last known dim level
      SetCurrentState2Hardware();

      Serial.println( "Node ready to receive messages..." );

      }

      void presentation()
      {
      // Register the LED Dimmable Light with the gateway
      sendSketchInfo(SN, SV);

      present( CHILD_ID_LIGHT, S_DIMMER );
      

      }

      /***

      • Dimmable LED main processing loop
        */
        void loop()
        {
        }

      void receive(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 );
      saveState(EPROM_DIMMER_LEVEL, requestedLevel);
      
      	// Inform the gateway of the current DimmableLED's SwitchPower1 and LoadLevelStatus value...
      	send(lightMsg.set(currentLevel > 0));
      
      	// hek comment: Is this really nessesary?
      	send( dimmerMsg.set(currentLevel) );
      
      
      }
      

      }

      /***

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

        int delta = ( toLevel - currentLevel ) < 0 ? -1 : 1;

        while ( currentLevel != toLevel ) {
        currentLevel += delta;
        analogWrite( LED_PIN, (int)(currentLevel / 100. * 255) );
        delay( FADE_DELAY );
        }
        }

      void SetCurrentState2Hardware()
      {
      if (LastLightState==LIGHT_OFF) {
      Serial.println( "Light state: OFF" );
      } else {
      Serial.print( "Light state: ON, Level: " );
      Serial.println( LastDimValue );
      }

      //Send current state to the controller
      SendCurrentState2Controller();
      }

      void SendCurrentState2Controller()
      {
      if ((LastLightState==LIGHT_OFF)||(LastDimValue==0)) {
      send(dimmerMsg.set((int16_t)0));
      } else {
      send(dimmerMsg.set(LastDimValue));
      }
      }

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @rozpruwacz its a normal wall switch, using 220v. The LED using a ac-dc converter with 5v output. I use pro mini with 3.3v on raw input. seesm to work, however when I switch on it took around 10 sec, even I place analogWrite( LED_PIN, 255); 1st line in setup().

      posted in Troubleshooting
      alterfritz
      alterfritz
    • RE: Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      @alterfritz ... one thing to add: of cause I tried adding it 1st line in setup(), does not work.

      posted in Troubleshooting
      alterfritz
      alterfritz
    • Startup time of arduino pro mini with mysensors 2.2 - took 10 sec (guess its the radio), can I execute some code immediately (<1sec)?

      Hi,

      just encounter an issue I need help on. I'm new to mysensors . Try to upgrade some of my LEDs with DimmableLED Sensors. I'm using the current development branch for 2.2 as I had issues with the radio on 2.1.

      All fine - I created a small ardunio mini with the radio and and MOSFET for switching, works. But then I encounter an issue: every time I switch on the led with the wall switch it tooks a few seconds >10 to get ON. I want it immediately to go ON with 100%, then getting old value from gateway. I tested with a simple sketch without mysensors - it switches almost immediately , especially without bootloader.

      So I guess this is related to the startup time of the mysensors lib, any way to place some code somewhere it get executed ASAP?

      Like "analogWrite( LED_PIN, 255);" to switch LED ON in milisecs, not secs?

      Thanks!
      Joerg

      posted in Troubleshooting
      alterfritz
      alterfritz