Skip to content
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Controllers
  3. OpenHAB
  4. openHAB 2.0 binding
  • Getting Started
  • Controller
  • Build
  • Hardware
  • Download/API
  • Forum
  • Store

openHAB 2.0 binding

Scheduled Pinned Locked Moved OpenHAB
534 Posts 88 Posters 479.5k Views 99 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • FrancoisF Offline
    FrancoisF Offline
    Francois
    wrote on last edited by
    #161

    @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
    
    andreacioniA 1 Reply Last reply
    0
    • FrancoisF Francois

      @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
      
      andreacioniA Offline
      andreacioniA Offline
      andreacioni
      wrote on last edited by
      #162

      Hi @Francois ,

      thanks for report. Seems that the you are using 2.0 version of MS Gateway. If you do not need it for particular task, try install the 1.5 version. I'll try to fix your problem as soon as possible!

      1 Reply Last reply
      0
      • FrancoisF Offline
        FrancoisF Offline
        Francois
        wrote on last edited by
        #163

        @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

        1 Reply Last reply
        0
        • T Offline
          T Offline
          TimO
          Hero Member
          wrote on last edited by
          #164

          I have a serial and ethernet gateway with version 2.0 running without any problems.
          In your case there are a lot messages arriving within a short time, maybe that is the reason the gateway won't react on the I_VERSION message from the binding.

          Please disable debugging in the gateway and try again. The reliability of my gateway improved a lot after disabling debugging.

          1 Reply Last reply
          0
          • FrancoisF Offline
            FrancoisF Offline
            Francois
            wrote on last edited by
            #165

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

            andreacioniA 1 Reply Last reply
            0
            • FrancoisF Francois

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

              andreacioniA Offline
              andreacioniA Offline
              andreacioni
              wrote on last edited by
              #166

              @Francois could you please send manually the I_VERSION command to the gateway? By no this is done by binding to check if the startup of the gateway was completed without errors. In your case that check fail. The I_VERSION message is this: 0;0;3;0;2;, you could try also 0;255;3;0;2; and see if gateway answer. Let we know what you see!

              1 Reply Last reply
              0
              • FrancoisF Offline
                FrancoisF Offline
                Francois
                wrote on last edited by
                #167

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

                andreacioniA 1 Reply Last reply
                0
                • FrancoisF Francois

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

                  andreacioniA Offline
                  andreacioniA Offline
                  andreacioni
                  wrote on last edited by
                  #168

                  @Francois is a simple serial text message, just open the serial monitor of Arduino IDE and send it from there.

                  1 Reply Last reply
                  0
                  • FrancoisF Offline
                    FrancoisF Offline
                    Francois
                    wrote on last edited by
                    #169

                    @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
                    
                    andreacioniA 1 Reply Last reply
                    0
                    • FrancoisF Francois

                      @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
                      
                      andreacioniA Offline
                      andreacioniA Offline
                      andreacioni
                      wrote on last edited by andreacioni
                      #170

                      @Francois ok, this is the normal output. What happens if you send the I_VERSION message (just copy, paste and send one of them: 0;0;3;0;2; or 0;255;3;0;2; )?

                      UPDATE: Issue posted on tracker here

                      1 Reply Last reply
                      0
                      • T Offline
                        T Offline
                        TimO
                        Hero Member
                        wrote on last edited by
                        #171

                        @Francois : I've updated my serial gw to the most recent development version and checked it against the binding. It is working for me. The response to I_VERSION does not belong to the RF, I've checked the current implementation of the MySensors library, so it should make not difference if you use RFM69, NRF or no RF at all.

                        Maybe the gateway is too busy to answer the request? Maybe we could an option for the binding to omit the check for I_VERSION? I'm out of ideas at the moment.

                        andreacioniA 1 Reply Last reply
                        0
                        • FrancoisF Offline
                          FrancoisF Offline
                          Francois
                          wrote on last edited by
                          #172

                          @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

                          1 Reply Last reply
                          0
                          • T TimO

                            @Francois : I've updated my serial gw to the most recent development version and checked it against the binding. It is working for me. The response to I_VERSION does not belong to the RF, I've checked the current implementation of the MySensors library, so it should make not difference if you use RFM69, NRF or no RF at all.

                            Maybe the gateway is too busy to answer the request? Maybe we could an option for the binding to omit the check for I_VERSION? I'm out of ideas at the moment.

                            andreacioniA Offline
                            andreacioniA Offline
                            andreacioni
                            wrote on last edited by
                            #173

                            @TimO said:

                            Maybe we could an option for the binding to omit the check for I_VERSION?

                            I could do it without any problem.

                            1 Reply Last reply
                            0
                            • FrancoisF Offline
                              FrancoisF Offline
                              Francois
                              wrote on last edited by
                              #174

                              @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?

                              1 Reply Last reply
                              0
                              • T Offline
                                T Offline
                                TimO
                                Hero Member
                                wrote on last edited by
                                #175

                                @Francois : No, I don't think so. I can't explain this behaviour and I'm sure the binding will just work fine after the initial check of I_VERSION.

                                @andreacioni : Would you be so kind to prepare a PR? I suggest to leave the check on by default.

                                andreacioniA 1 Reply Last reply
                                0
                                • T TimO

                                  @Francois : No, I don't think so. I can't explain this behaviour and I'm sure the binding will just work fine after the initial check of I_VERSION.

                                  @andreacioni : Would you be so kind to prepare a PR? I suggest to leave the check on by default.

                                  andreacioniA Offline
                                  andreacioniA Offline
                                  andreacioni
                                  wrote on last edited by
                                  #176

                                  @TimO simple update, tonight I'll push it :+1:

                                  1 Reply Last reply
                                  1
                                  • T Offline
                                    T Offline
                                    TimO
                                    Hero Member
                                    wrote on last edited by
                                    #177

                                    New version of the binding available!

                                    • A requestTime from a node is now answered by the controller. Is anyone able to test it? (@undee )
                                    • The controller will answer a request for "imperial or metric" like temperature sensors might ask. We need to test that too.

                                    Big thanks @andreacioni for the implementation and @Francois for testing/reporting!

                                    I've added an example page in the wiki: https://github.com/tobof/openhab2-addons/wiki/Examples
                                    These are the type of things I'm currently using. (SensebenderMicro, Humidity, Temperature, Cover, Motion, Light ...)

                                    Has anyone additional examples yet?

                                    undeeU andreacioniA 2 Replies Last reply
                                    1
                                    • T TimO

                                      New version of the binding available!

                                      • A requestTime from a node is now answered by the controller. Is anyone able to test it? (@undee )
                                      • The controller will answer a request for "imperial or metric" like temperature sensors might ask. We need to test that too.

                                      Big thanks @andreacioni for the implementation and @Francois for testing/reporting!

                                      I've added an example page in the wiki: https://github.com/tobof/openhab2-addons/wiki/Examples
                                      These are the type of things I'm currently using. (SensebenderMicro, Humidity, Temperature, Cover, Motion, Light ...)

                                      Has anyone additional examples yet?

                                      undeeU Offline
                                      undeeU Offline
                                      undee
                                      wrote on last edited by
                                      #178

                                      @TimO

                                      Thanks for your work! It's really nice to see the progress!

                                      I have tried the TimeAwareSensor and the MockMySensors examples. The I_TIME message is sent by the node, obviously received by the gateway, but there the gateway is not sending anything in response. Are you sure your code for sending a time response is already active?

                                      andreacioniA 1 Reply Last reply
                                      0
                                      • FrancoisF Offline
                                        FrancoisF Offline
                                        Francois
                                        wrote on last edited by
                                        #179

                                        @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!
                                        
                                        1 Reply Last reply
                                        0
                                        • undeeU undee

                                          @TimO

                                          Thanks for your work! It's really nice to see the progress!

                                          I have tried the TimeAwareSensor and the MockMySensors examples. The I_TIME message is sent by the node, obviously received by the gateway, but there the gateway is not sending anything in response. Are you sure your code for sending a time response is already active?

                                          andreacioniA Offline
                                          andreacioniA Offline
                                          andreacioni
                                          wrote on last edited by
                                          #180

                                          Hi @undee

                                          Can you post your node firmware version and log of OH2? It's very important for us to troubleshoot your problem.
                                          Thanks!

                                          undeeU 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          4

                                          Online

                                          11.7k

                                          Users

                                          11.2k

                                          Topics

                                          113.0k

                                          Posts


                                          Copyright 2019 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular