Author Topic: Sensors Stop Sending MQTT Messages and have to reboot mcGW to start sending again.  (Read 262 times)

kbrooking

  • Full Member
  • ***
  • Posts: 104
    • View Profile
I notice a couple times a day my sensors stop sending MQTT messages and I have to reboot the mcGW to get them to start reporting again. Has anyone else seen this issue?

Share on Facebook Share on Twitter Share on Google+


mc-T2

  • Administrator
  • Sr. Member
  • *****
  • Posts: 252
  • mc-Things! The opportunities are endless!
  • Location: Canada
    • View Profile
Can you confirm what version of mcOS(firmware) your gateway is at and your devices 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

NorGer

  • Newbie
  • *
  • Posts: 4
    • View Profile
Hi,

I have the same issue.

Configuration:
- mcGateway110
                  * GwVersion: 0.9-958
                  * LpLanVersion: 09-615
- mcModule120 firmware: v0.9.615
- mosquitto: local server
- mcGateway connection to local network: wifi

Problem description:
Temperature application project (using MQTT class with method Lplan.Publish) from the GitHUB was running on the mcModule120. This program generates bacons in very short cycles for different topics (as .../Temerature, .../BatteryVoltage). I can receive a "lifecycle" bacon in the topic home/mcThings too and the greenLED blinks on the module if a bacon was sent to the MQTT server. I used a private MQTT sever with windows application-, mobile- and mcModule120 clients. After some hours the application- and mobile-client were still able to publish and receive messages, but I lost all bacons from the mcModule. The modul was alive, because the greenLED was still blinking and I could measure the required power voltage level (about 3V on the battery). So, I thought that the only problem could be at the mcGateway side. I restarted the gateway and after some secounds the bacons from the mcModule ware received in the topics again.

Any idea or solution to handle this issue?

kbrooking

  • Full Member
  • ***
  • Posts: 104
    • View Profile
My configuration is:

- mcGateway110
                  * GwVersion: 0.6-367
                  * LpLanVersion: 08-420
- mosquitto: local server
- mcGateway connection to local network: wifi

kbrooking

  • Full Member
  • ***
  • Posts: 104
    • View Profile
This platform is very frustrating.

I upgraded to GW Version 0.9-958 and LP Lan Version 0.0.615. Now mcStudio can only see the GW when the ethernet cable is connected. The GW does not show up when in wi-fi mode.

Wi-fi settings are the same in GW config as before the upgrade.

kbrooking

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Here are some recent updates…

As I mention above, after upgrading the mcGW to the new Host & application firmware I lost wi-fi connectivity on the mcGW and was forced to use the Ethernet cable. Since then all the sensors have been reporting at their expected intervals without any lockups.
Maybe NorGer can confirm this if he can disconnect the wi-fi connection and  use Ethernet connection instead and see if issue is resolved as well?

A few more details that maybe worth mentioning. In the past I would get up the morning after leaving the sensors on all night and 100% of the time there would be at least two sensors that stopped reporting over MQTT. However, the beacons seemed to keep reporting. Because only two of the four sensors would stop reporting, I suspected maybe a bug in my script code so I would open mcStudio, connect to the mcGW, connect to the module and run the debugger only to find the code working properly. I would then also begin to see the MQTT messages to start reporting again.

Maybe there is some issue with wi-fi connection and MQTT locking up and when I connect to the gateway via mcStudio; somehow that clears it up. Just thinking out loud. Any suggestions?

strikeaxe

  • Newbie
  • *
  • Posts: 1
    • View Profile
I struggled with my mcGateway110 in mcStudio using wifi most of the day. I can use Ethernet to see/connect the gateway. I can see the mcGateway110 on my wireless router. Here are the steps that I used and so far has corrected not being able to connect to wifi.  It is as noted not reliable as wifi seems to drop out when using mcStudio.

1) Power off the mcGateway110
2) Move selector switch to wifi
3) Power on the mcGateway110
4) Run a ping test to the mcGateway110 (100% Success)
5) Launch mcStudio Tools > Devices and the mcGateway110.
6) Attempt to connect to the gateway after >20 seconds the gateway disappears from the list.
7) Run ping on the mcGateway110 (100% Success)
8) Close and launch mcStudio "wifi' gateway still does not show up.
9) Move the selector switch to "Ethernet". (Do not power cycle mcGateway110)
10)Close and restart mcStudio and I can connect "Ethernet" to the mcGateway110
11)Move the selector switch to "wifi". (Do not power cycle the mcGateway110)
12)Launch mcStudio Tools > Devices and the mcGateway110
13)Connection using mcStudio on "wifi" successful

Note you must close and re-open mcStudio between selector switch moves. Failing to do so produces and error "see attached log file" I am curious if the mcStudio program checks for the selector switch location before loading either wifi or ethernet settings.



mcStudio v0.9.534.0
mcGateway110
  GwVersion 0.9-958
  LpLanVersion 0.9-615
VM Firmware Version 0x0.9r615
Bootloader Version 1v1.0r0

Tomasu

  • Newbie
  • *
  • Posts: 3
    • View Profile
I'm having the same problem. After a day or two, the data stops flowing and I need restart the gateway.

Versions:
McGateway 110:
GwVersion: 0.9-958
LpLanVersion: 0.9-615
McModule 110:
Version: not sure, but probably 0.9-615 as I updated everthing at the same time and I see 0.9.615 in my download/mcthings folde but the devices tool shows 0 for version.

Any way we can fix this?

mc-T2

  • Administrator
  • Sr. Member
  • *****
  • Posts: 252
  • mc-Things! The opportunities are endless!
  • Location: Canada
    • View Profile
Hi Everyone,
sorry that you are experiencing these issues - As mentioned in other posts, we are no longer supporting the older version of the system in the fact that we are not going to make changes or fix any potential bugs as we are focused on the new system (with mcCloud: https://www.mcthings.com/getting-started-mccloud/). NOTE - Older hardware such as the gateway110 and mcMod110's will not function on the new system (they dont have the technical requirements to access the new system) so to work with the new release, you will need to upgrade your equipment.
We are planning on a discounted offer to existing users and backers soon (it has been delayed due to some massive projects we are working on). If you do want to get more information, you can ask us here or email as at info@mcthings.com.

In regards to the issue, our recommendation would be to re-load the firmware for all your devices, make sure your modules have fresh batteries and, if you are having issues using WIFI, switch to Ethernet as for some of you, it appears to be more stable.

Hope that helps!
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

Tomasu

  • Newbie
  • *
  • Posts: 3
    • View Profile
Hi Everyone,
sorry that you are experiencing these issues - As mentioned in other posts, we are no longer supporting the older version of the system in the fact that we are not going to make changes or fix any potential bugs as we are focused on the new system (with mcCloud: https://www.mcthings.com/getting-started-mccloud/). NOTE - Older hardware such as the gateway110 and mcMod110's will not function on the new system (they dont have the technical requirements to access the new system) so to work with the new release, you will need to upgrade your equipment.
We are planning on a discounted offer to existing users and backers soon (it has been delayed due to some massive projects we are working on). If you do want to get more information, you can ask us here or email as at info@mcthings.com.

In regards to the issue, our recommendation would be to re-load the firmware for all your devices, make sure your modules have fresh batteries and, if you are having issues using WIFI, switch to Ethernet as for some of you, it appears to be more stable.

Hope that helps!

*sigh*

That's incredibly disappointing.

I'm not really interested in a more closed system, it's already bad enough that the current one was dropped so quickly with so many issues still present.

I'm sorry but I don't think I'll be able to support you guys in the future. I'm disappointed. I was happy to support you guys as a fellow albertan.

mc-T2

  • Administrator
  • Sr. Member
  • *****
  • Posts: 252
  • mc-Things! The opportunities are endless!
  • Location: Canada
    • View Profile
Hi Tomasu,

I understand your disappointment and frustration - There are many good reasons why we had to move to a new system and drop the legacy version such as:

- SECURITY - as you know, in IoT, security is a big ticket item (there are news reports everyday about hackers, etc). The older system, while a bit more 'open', does not include the security required for large-scale enterprise IoT solutions. As we are a business and focused mostly on B2B opportunities, this is a critical thing that we needed to address and as such, a system like mcCloud was necessary

- SCALABILITY - if you have used the legacy system for some time, you understand that it can be frustrating to update even 10 or 20 devices with new code or firmware as you had to physically touch/get close to the devices. Imagine trying to do this with 100 or 100,000 devices! mcCloud changes this and makes it SO MUCH easier to manage the devices at scale.

-VERSATILITY - Using mcCloud, you can now easily send information to multiple locations (like Azure, Losant, Ubidots, etc) from the cloud, instead of configuring your gateway to send the information to one location only. While this might be nice for a DIY person, it is not scalable for anytype of real IoT solution.

IMPROVEMENTS - Just like almost anything else, as technology gets better and new requirements need to be addressed, systems need to change. As such, we needed to move to the new system for all the above reasons and it allows us to continue to add new features and functions in the future.

Sorry to hear that you are going to move away from our platform. Hopefully the above gives you some understanding of why we we changed from legacy and why we can no longer support the old system.
Take care.
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

Tomasu

  • Newbie
  • *
  • Posts: 3
    • View Profile
Hi Tomasu,

I understand your disappointment and frustration - There are many good reasons why we had to move to a new system and drop the legacy version such as:

- SECURITY - as you know, in IoT, security is a big ticket item (there are news reports everyday about hackers, etc). The older system, while a bit more 'open', does not include the security required for large-scale enterprise IoT solutions. As we are a business and focused mostly on B2B opportunities, this is a critical thing that we needed to address and as such, a system like mcCloud was necessary

- SCALABILITY - if you have used the legacy system for some time, you understand that it can be frustrating to update even 10 or 20 devices with new code or firmware as you had to physically touch/get close to the devices. Imagine trying to do this with 100 or 100,000 devices! mcCloud changes this and makes it SO MUCH easier to manage the devices at scale.

-VERSATILITY - Using mcCloud, you can now easily send information to multiple locations (like Azure, Losant, Ubidots, etc) from the cloud, instead of configuring your gateway to send the information to one location only. While this might be nice for a DIY person, it is not scalable for anytype of real IoT solution.

IMPROVEMENTS - Just like almost anything else, as technology gets better and new requirements need to be addressed, systems need to change. As such, we needed to move to the new system for all the above reasons and it allows us to continue to add new features and functions in the future.

Sorry to hear that you are going to move away from our platform. Hopefully the above gives you some understanding of why we we changed from legacy and why we can no longer support the old system.
Take care.

I think the most disappointing part is the increased closed-ness, the fact that this has been a problem for a while, theres no fix, and the only comment is "sorry, we're not supporting it anymore"

I get the whole running a business thing. It just doesn't seem like the product was particularly valued, nor are the customers.