Author Topic: gateway did not react on connect request  (Read 218 times)

bdevlin

  • Newbie
  • *
  • Posts: 38
    • View Profile
gateway did not react on connect request
« on: July 04, 2017, 06:43:31 pm »
Finally upgraded everything to 9.615.

Trying to connect to my devices (MC-110s in this case) responds with "gateway did not react on connect request". Then disconnects the gateway.

Devices on latest firmware. Gateway on app and firmware 9.615

Basically, I can't even upload new code to my devices now.

Please advise.

Social Buttons


mc-T2

  • Administrator
  • Full Member
  • *****
  • Posts: 239
  • mc-Things! The opportunities are endless!
  • Location: Canada
    • View Profile
Re: gateway did not react on connect request
« Reply #1 on: July 05, 2017, 11:24:43 am »
Hi bdevlin,

Just to confirm on where you are at with everything:

The mcMod110 should be at: V0.9.615
The mcGateway110 should be at V0.9.615
Can you confirm that you are the latest version of mcStudio (V0.9)?

Can you take a screenshot of the 'device menu' where you connect to your gateway - just want to check that it is on the same subnet

And finally, can you try connecting to the gateway a couple of times (disregard the error) and see if this works as well please?
Need more mc-Modules, mc-Gateways or other mc-Things? Check out our product page: www.mcthings.com/products. mc-Development kits are available too!
Check out a live Dashboard using mcThings and Losant! Click here: https://goo.gl/ST43hB

bdevlin

  • Newbie
  • *
  • Posts: 38
    • View Profile
Re: gateway did not react on connect request
« Reply #2 on: July 05, 2017, 02:21:14 pm »
mc-Studio is 9.534
gateway firmware and software are 9.615
all mc-mod110 are 9.615 firmware
mc-OTA is 1.2.13

Everything seems up to date, but I get this error.

Connected over and over and the gateway loses connection as soon as the error comes up.

Rebooted as well and re-launched studio.


mc-T2

  • Administrator
  • Full Member
  • *****
  • Posts: 239
  • mc-Things! The opportunities are endless!
  • Location: Canada
    • View Profile
Re: gateway did not react on connect request
« Reply #3 on: July 05, 2017, 04:27:39 pm »
Can you post a screen shot of the device menu (showing your gateway IP) please?

Also, a screenshot of the error would help too

Thanks!
Need more mc-Modules, mc-Gateways or other mc-Things? Check out our product page: www.mcthings.com/products. mc-Development kits are available too!
Check out a live Dashboard using mcThings and Losant! Click here: https://goo.gl/ST43hB

bdevlin

  • Newbie
  • *
  • Posts: 38
    • View Profile
Re: gateway did not react on connect request
« Reply #4 on: July 05, 2017, 05:27:31 pm »
I am connecting about 1 in 50 times... Not good. The error is actually not thrown as often as a simple inability to connect to the devices. There is a lot of difficulty connecting compared to the prior firmwares. Even when an mc-110mod is right next to the gateway (both ethernet wired and wireless).

Also my scripts no longer work and I have not changed anything. Did you deprecate IFTTT? Messages were relaying through my IFTTT applet fine right up until my firmware upgrades. I have re uploaded the script, but now my applet quit working? I have not had a chance to rebuild for MQTT yet.

mc-Studio still crashes like crazy, even for simple things like copy paste or even typing in a single character of code.
----------------------------------------------------------------
Class Devlin_Temp
    Shared Event CheckTemp() RaiseEvent Every 3 Minutes
     
        Dim temp As Float = TempSensor.GetTemp()
        Dim tempstring As String = temp.ToString()

        Dim ID As String
        ID = Device.mcUID().ToString("x8")
       
        Lplan.IFTTT("{key}", "Devlin_Temperature", tempstring, "", ID)
     
    End Event
   
    Shared Event measureVoltage() RaiseEvent Every 2 Hours
       
        Dim BattVolt As Short = Device.BatteryVoltage
        Dim Volts As String = BattVolt.ToString()
        Dim mcID As Float = Device.mcUID
        Dim ID As String = mcID.ToString("x8")
        If BattVolt < 2200 Then
            Lplan.IFTTT("{key}", "Devlin_Temp_Battery", Volts, "", ID)
        Else
           
        End If
       
    End Event
   
End Class
-------------------------------------------------------------------------
« Last Edit: July 05, 2017, 05:33:09 pm by bdevlin »

mc-Abe

  • Full Member
  • ***
  • Posts: 167
    • View Profile
    • mc-Things
Re: gateway did not react on connect request
« Reply #5 on: July 06, 2017, 09:58:15 am »
When mcStudio crashes, it should pop up a dialog with an exception. Would you be able to send us the text for this exception? It will give us an idea of what is going on on your system.

Due to the resource limitation on the gateway the connection mechanism from mcStudio is not 100% reliable. This would explain your 1/50 times connection, although this seems very unreasonable, I would not expect that much degradation. The system would suffer under high network loads. Is there anything out of the ordinary on your network? Any high bandwidth streaming or broadcasting?

IFTTT is still supported and was not deprecated in v0.9 so I am not sure what is going on here.

bdevlin

  • Newbie
  • *
  • Posts: 38
    • View Profile
Re: gateway did not react on connect request
« Reply #6 on: July 08, 2017, 02:39:49 pm »
The crashes seemed to have calmed down a little. As far as the error text, that's not possible because it literally just closes the app with no error report.

A have managed to get the gateway to receive MQTT pubs from the mods (four 110's and one 120). But success is still down at one in ten. I disconnect the gateway, close the connection screen, open it back up and cross my fingers. One in three times if I connect to one, then I maybe connect to a second.

My gateway120 on the new firmware does not seem to want to receive MQTT messages from the modules for a full 24 hours. It basically works for a while, then stops relaying until I reset the unit. When I hit the reset button, it relays again, so the modules work fine. You may not have the space in the gateway memory, but it would be good if you could write a basic routine (in the next firmware) that logs activity to a USB stick in the port. I would happily send the data to your team.

So for now:
   mcStudio is still unstable but functional in the mcScript editor. Crashes are just a shutdown most of the time. Try alternate click paths, you probably all use the perfect click paths when you are testing, put it in front of your kids and significant others. You'll find the problems fast. (HINT: don't tell them where to click!)
   mcStudio/gateway is now worse at discovering mcMods. Gateway discovery is fast. Mod discovery is rare and unpredictable. Same, Kids and SO's for testing, there are still many problems here.
   Gateway110 appears to be crashing inside 24 hours and failing to relay MQTT pubs without a restart. No debug options. I will monitor and advise while I build out my IFTTT replacement. This is a huge issue for me, and I am not even a commercial client, just a hacker geek for personal amusement. The gateway must not crash!

« Last Edit: July 08, 2017, 02:43:38 pm by bdevlin »

bdevlin

  • Newbie
  • *
  • Posts: 38
    • View Profile
Re: gateway did not react on connect request
« Reply #7 on: July 11, 2017, 05:42:57 pm »
I believe I have discovered the gateway110 problem.

I have my OpenWRT router configured to reset at 6am every morning. The previous Gateway110 firmwares would simply reconnect after the router reset, however, the latest firmware does not seem able to rediscover my network after a disconnect (during the reset). I removed the reset from my router and the gateway is relaying fine for over 24 hours now. However, I think the gateway should have the ability to rediscover the network after a lost connection without have to hit the reset button (as it worked in prior firmware).

Thanks,
Brad

mcThings

  • We Connect Things To The Internet... That Can't Be Plugged In.
  • Administrator
  • Jr. Member
  • *****
  • Posts: 68
    • View Profile
    • www.mcthings.com
Re: gateway did not react on connect request
« Reply #8 on: July 13, 2017, 10:46:13 am »
Thanks for following up @bdevlin regarding the Gateway110 connectivity issue you're having.