Recent Posts

Pages: 1 [2] 3 4 ... 10
11
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.
12
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.
13
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.
14
Hi Junkboy,

yes, you can insert a 'sleep' function into your code. Check out the attached mcScript guide (Also available on the website) and search through it for the function. I think i remember that it is discussed or displayed on page 23 (and other areas within the document).

The concept would be, to complete what you are asking below, is to raise an event every 60 minutes, insert the sleep function for a certain period of time (I believe the sleep function calculates time in milliseconds so you'll need to do some conversion). Should allow you to do what you are asking below.

Good luck!
15
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!
16
Basically what I want is to put the mcMod120 to send data 60 minutes, then put it in sleep mode for 20 minutes, then again 60 minutes sending and 20 minutes in sleep mode, and this is repeated infinitely.

I currently use this line to send data every 5 seconds:
Shared Event Publish() RaiseEvent Every 5 Seconds

What I'm going to do, is put in place of 5 seconds, 60 minutes, and I'm looking for a function to put:

Sleep (20 min)

And let this start again ..
17
mc-Innovations / Re: Communicate Wireless Sensor using MCthings platform
« Last post by fany89 on June 25, 2018, 04:13:40 am »
Hi,
I have bought this sensor and for the record I am able to use this sensor with arduino Uno to monitor the readings on my laptop by using using Zigbee module
But for WIFI connection I have raspberry pi so I ll try to implement this process by using raspberry pi.
18
mc-Innovations / Re: Communicate Wireless Sensor using MCthings platform
« Last post by kristofferis on June 25, 2018, 03:40:47 am »
Hello. That sounds like a good idea.
What temperature sensor do you use now? I guess you want to connect the same sensors that you have now.
19
mc-Innovations / Communicate Wireless Sensor using MCthings platform
« Last post by fany89 on June 25, 2018, 03:34:51 am »
Hi, I using wireless temperature sensor which consist of Zigbee module to make connection wireless but I am looking the better way to connect these sensor through wireless communication system with MC things software tools which help sensor readings should be stored to server data base and by using MqTT protocol we will be to send the alerts to user's smartphones whenever temperature sensor readings goes up or down from the mentioned range

This Platform is much newer for me so will be looking forward for your helpful advice
20
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?
Pages: 1 [2] 3 4 ... 10