Particle Tools Changelog


#17

1/26/2017: SIM management for products

A big announcement today! For Particle product creators building cellular-connected devices, seamlessly managing a fleet of SIM cards becomes increasingly important as you grow. Today, we launched SIM management for products, equipping you with another useful tool that makes it even easier to go from prototype to production when using the Electron in your deployment.

Some of the most valuable features of SIM management for products include:

  • Import and pre-activate SIM cards en-masse to ensure a smooth unboxing experience for end users of your products
  • Gain meaningful insights into data usage patterns by viewing fleet-wide usage information
  • Set sensible cellular defaults to save you time and effort without sacrificing control of individual SIM cards
  • Take advantage of volume-based pricing for cellular service available exclusively to product creators

This feature is being launched in public beta. For more information on how to get started, check out the guide on our docs!


#18

1/31/2017: Build Quick Help Drawer

Hello friends! Today we’ve added a new item in the Build sidebar, because we know that sometimes it can be hard to understand how a device is feeling.

Clicking on it brings up the new Quick reference drawer. It will show you all the device modes (docs), so you can quickly figure out in which state your device is currently in.

Hopefully it will help and will reduce some time going back and forth to the docs!


#19

2/2/2017: Preprocessor improvements

Here’s something new to make sure every day doesn’t feel like groundhog day: you can now use custom classes in your code on the Web IDE and you will no longer get tripped up by if else(foo).

class X {
};
// no longer says X does not name a type
void doit(X &x) {
}
bool foo, bar;
void setup() {
  X x;
  doit(x);
  if (bar) {
   return;
  }
  // no longer confuses else if(foo) with a function declaration...
  else if (foo)
    return;
}

#20

2/7/2017: Particle CLI 1.19.4

Features

  • #338 - particle keys protocol displays the currently configured protocol for the connected device
  • #205 - webhook delete all command. Thanks @kennethlimcp!
  • #240 - particle serial monitor --follow reconnects to the serial port when the device resets. Thanks @derekmpeterson!
  • #225 - ability to specify a .json file to enter wifi credentials. Thanks @markterrill!
  • --no-update-check to skip checks for updated versions

Fixes

  • #326 - unhandled rejection in help
  • #235 - Unhandled error in particle setup
  • #331 - Flashing a known app causes exception
  • #328 - ParticleCLISetup for Windows broken due to OpenSSL download problem
  • #326 - Unhandled rejection in help
  • #321 - keys doctor (device id) is case sensitive
  • #292 - this -> self
  • #280 - Incorrect key pulled for Electron using TCP
  • #279 - Server key address output incorrect for Electron using TCP
  • #231 - max retry for wifi scan error
  • #299 - update glob dependency to avoid warning about minimatch vulnerability. Thanks @snyk-bot.

Serial monitor auto-connect?
PuTTY or other serial monitor that automatically reconnects Windows
#21

2/7/2017: Bug fixes and improvements to the Web IDE

We care a lot about the way that our tools help you achieve your goals and we know that sometimes the experience can be affected by bugs. This sprint we knocked some off and also added some small improvements.

Web IDE

  • Fixed: Users could change selected device when a flash was in progress. Sometimes, in a rush, users changed their starred device during a flash, and this caused some minor confusion. You will see a modal if you try this now, so hopefully, no more confusion around.
  • Fixed: Claiming a device is broken in the Web IDE, as it also loads products. After claiming a device, the list of products was loaded in the list of devices. This doesn’t happen anymore, now only your cool new device :sunglasses: will be added to the list.
  • Fixed: Remember last code a user had open, reopen when they return We want you to be able to get back to your code fast, so after opening an app, next time you go to build.particle.io, you will be presented with the last app you’ve opened.
  • Fixed: Refresh devices doesn’t show newly claimed devices Claim a device through the CLI or the API? We’ll make sure it shows up when you hit the refresh button in the Devices sidebar.
  • Improved: Device selection Previously, if you deselected the active device, flash and verify were disabled until you selected a new one. You must now change your device target to another device to “un-select” the original one.
  • Improved: Console menu item now directs to /logs. Need a quick sneak peek of what your device is telling to the world? Click on the Console icon and we will show you. Not seeing anythings in the logs? Make sure you’re publishing events.

#22

2/7/16 - New FAQ on Eclipse Debugging

There is a new FAQ that describes how to use Eclipse, a free IDE for Windows, Mac, and Linux, along with OpenOCD, to do source-level debugging of code running on a Particle Photon, P1, or Electron.
Some of the things you can do:

  1. Set breakpoints in code and view source.
  2. See the call stack.
  3. View variables.
  4. Single-step through code.


#23

2/8/2017: Docs: webhooks and search

There is a new webhook reference section in the docs that documents all the properties of webhooks and the template syntax.

The search box at docs.particle.io was revamped to remove all the duplicate results for multiple devices and provide more accurate results.

This is also available on prerelease-docs.particle.io which is currently serving docs for 0.6.1-rc.2 firmware.


#24

2/9/2017: Console: Create products using Bluz

Ayo! Today we enabled creation of products using Bluz (an amazing bluetooth microcontroller platform, find out more about them here bluz.io).

This now means that Bluz devices have access to all our great product features in the Console, including:

  • Send batch firmware updates to groups of devices
  • Connect devices to web services
  • Gain insights into device fleets


When Redbear Duo will gain product support?
#25

3/2/2017: Console: Edit integrations

If you look at the bottom of the integrations page, you should see a new fancy button which enables you to edit your integrations.

Clicking on it will bring you to a form where you can edit your integration. After you click ‘Save’, the changes will be propagated in a few seconds.

Also, Azure IoT Hub Integration: Particle device names will now be automatically synced with IoT Hub at the time of creation in the device registry


#26

March 1st 2017: Firmware v0.6.1

Hey friends! We have released new default firmware v0.6.1. Available now on https://build.particle.io for Core/Photon/P1/Electron.

Here are just some of the exciting features and enhancements:

  • New v11 Bootloader for Photon/P1/Electron automatically applied
  • RGB LED and SETUP/MODE button mirroring!
  • LED Signaling Themes!
  • Custom LED colors in bootloader v11 (Safe Mode, DFU Mode, Firmware Reset)
  • Improved Electron data usage and communications
  • Lots of new System Events!
  • Listening Mode timeout API (default: Wi-Fi = no timeout, Cellular = 5 minute timeout).
  • [Electron] IPAddress ip = Cellular.resolve(hostname);
  • Improved Arduino Compatibility (supported by default, added PARTICLE_NO_ARDUINO_COMPATIBILITY=y command line option for disabling)

For all features, enhancements and bug fixes please read the full release notes here.


Compilation FAILS #define ARDUINO?
#27

3/2/2017: Build: Status bar

You can see more information about your currently selected device in the bottom right corner of the Web IDE. It contains the following: Last Event Name, Last Event Data, Device Type, Device Name, Device Status, Device Version. Clicking on the lightbulb will signal the device.


#28

3/16/2017: Console: Functions & Variables

Do you use functions or variables in your applications? You are now able to call functions & see the value of variables in Console. You can use the new functionality in two places: On the Devices page / On the devices page of a Product, just click on any device row to expand it and you will see the new view.


#29

3/23/2017: API now sorts device lists by last connection time by default

GET /v1/devices and GET /v1/products/:productIdOrSlug/devices will now sort devices by the last time they connected to the cloud, with the most recently connected appearing first. This will help make it easier to quickly identify and interact with devices that are most active.


#30

3/29/2017: CLI version 1.21.0

  • Wi-Fi switching on Windows
  • Serial setup on Windows
  • Library publish defaults to library in current directory
  • White list files when uploading library to avoid publishing unnecessary files (only include code files when publishing so you don’t publish .bin, .png, .pdf by mistake)

Cloud

  • Fix viewing large libraries in the Web IDE
  • Relax validation rules to allow renamed libraries and header-only libraries

#31

3/30/2017: Updates to Particle on Raspberry Pi

A new version of firmware and the Particle Agent bring needed improvements to the Particle experience on Raspberry Pi.

See Update to Particle on Raspberry Pi beta - 0.2.4 for details!


#32

3/31/2017: Major updates to mobile SDKs and support!

iOS - Major update to the cloud SDK (0.6.0) and device setup library (0.7.0), as well as documentation and examples updates.

A very notable community supported 100% pure Swift library for the Particle Cloud SDK - would allow you to create Swift style apps with no compromises and build native apps not just for iOS but also macOS, tvOS, watchOS, Linux and even backend applications using IBM’s Kitura framework!

Android - New app release (1.7) in Google Play Store and many updates to both the Cloud SDK (0.4.2) and device setup library (0.4.3). Expect many more updates and improvements coming to Android support soon.

As usual for any questions/issues head to our Mobile community category.


#33

4/3/2017: Code sharing in Web IDE

A common scenario is a need to share your app with other users. From just sharing useful code/examples to basic collaboration. Now you can do this with any of your app in our Web IDE:

After sharing an app revision it will be available for anyone with the link. Note that any changes you make to the app after won’t be visible under the same link (you need to generate link for the new revision). Once you send the link to someone, they’ll be able to see your code, flash it to their devices or copy to their account and make changes:

Happy sharing!


#34

April 5th 2017: Firmware v0.6.2-rc.1

Hey friends! We have released a new pre-release firmware v0.6.2-rc.1. Available now on https://build.particle.io for Core/Photon/P1/Electron.

This release addresses one very important Enhancement / Bug fix:

:pencil: We have done extensive testing against all Particle Libraries currently published and if they were not compiling on 0.6.1, they are now compiling once again with 0.6.2-rc.1. Please give it a test and let us know if you find anything not working properly.


#35

4/19/2017: Product Development Devices

As a firmware engineer building a Particle product, it is important that you can rapidly iterate on new device firmwares, while still simulating the behaviors of production devices deployed in the field. Development devices allow you to do just this.

Development devices are special kinds of product devices marked specifically for internal testing, separate from the production fleet. Development devices are prevented from receiving any automatic product firmware updates from the Particle cloud. These devices will ignore both released product firmware as well as any firmware version it has been locked to run.

Mark a device as a development device in the Console, specifically on your product’s devices view:

Once you mark a device as a development device, you will see it marked with a special icon in the “Firmware” column:

For more info, check out the guide on Development Devices


"Released" Firmware updates overwriting 'newer' versions
#36

4/24/2017 Google Maps Integration

Particle and Google Maps can now be used in tandem to easily find and track the location of Particle devices without the need for any additional hardware. Wi-Fi or Cellular networks are collected by a Particle device, and sent to Google’s Geolocation API in exchange for latitude/longitude coordinates.

You can enable the integration from the Particle Console:

Check out the tutorial for details on how to get started. To visualize your devices coordinates, check out the open source visualization app provided by the Google Maps team.

Happy Building!