[App][Cloud&Pro] Twinkly

Apps
2

Legacy Driver

  • Using the legacy driver may disrupt functionality of the original Twinkly App.
    This is a known problem caused by that unofficial api, which is not designed to have multiple clients at the same time. The latest version supports the official cloud api, which also is under continuous improvement. Please migrate your devices to the new driver as soon as possible.

FAQ

  • Q: I have a RGBW device but Homey does not seem to make use of the white channel?
  • A: This is correct. RGBW is currently not support by the Homey app. As a workaround you can create an effect replicating your color setting as a workaround. Proper direct RGBW support might come at a later time.
  • Q: Why am I getting a “499” error?
  • A: This is a known issue occuring randomly. Twinkly is working on a fix for this.
  • Q: Why am I getting a “504” error?
  • A: This is a known issue occuring randomly. But be aware that this most likely means that your device as stopped communicating with the Twinkly servers or is not powered. Usually you can resolve this by power cycling your Twinkly device. You can catch this error with advanced flows as well. Twinkly is working on a solution for this.
  • Q: Why am I getting a “Network request failed” error?
  • A: This is issue with Homey itself. A bug report is open at Athom about this. This error typically would hide a 499 or 504 error in the background but Homey does not properly propagate this error to the user. This behavior is seen in the Homey user interface as well as when testing flows. When running flows normally you will get the correct actual error from the flowcard error output.
  • Q: What does the error message “Could not get OAuth2Client” mean?
    A: If for any reason your authentication becomes invalidated, please go into one of the devices advanced settings and do a “Repair” from there. You might need to restart the app from the settings menu afterwards (“More…” → “Apps” → “Twinkly” → ‘little gear icon’)
  • Q: What is the reason for the device status “Device seems to be offline”?
    A: This message is issued by the Twinkly api itself. You can not do anything in the app or Homey to work around this. It literally means that your Twinkly is not connected to Twinkly’s api servers, for whatever reason this might happen. Doing a power cycle of your Twinkly will enforce an immediate reconnect. Please ensure your Twinkly device has internet access.
  • Q: Why is the select effect flowcard not showing for my device?
  • A: Selecting effects through the Twinkly api is not supported for Gen1 devices. Hence, if you have a Gen1 device or a group containing a Gen1 devices, the flowcard will not be available.

Changelog

v4.3.1 (in public test)

  • Fixed: App crash when Homey Premium Subscription is missing.

v4.3.0

  • Added: Trigger flowcard when the device changes the mode.
  • Added: Mode check condition flowcard.
  • Fixed: Improved app robustness against crashes for some Homey cloud only edge cases.
  • Removed: RGBW white channel support is removed for now as it requires a bigger rework.

v4.2.3 (unreleased)

  • Fixed: Effects flowcard filter is now working as expected.
  • Fixed: A race condition with capabilitiy changes. Gen1 device limitations are now correctly reflected in Homey.
  • Fixed: A connection timeout issue when chaning the brightness, resulting in strange values calucated from the Homey data.
  • Changed: It is now no longer required to explictly turn a device on before running the select effect flowcard.
  • Changed:: The commands api has been tweaked to be more tolerant to networking issues. Errors are reported by flowcards and the UI only if the automatic mitigation attempt failed.
  • Added: Dedicated support for RGBW devices. If a device or device group has RGBW devices only, Homey will now use the white channel to represent kelvin settings. If the device has no RGBW profile or the group does contain at least one device not having the RGBW profile, Homey will emulate kelvin as usual using the RGB spectrum.

v4.2.2 (unreleased)

  • Added: A choose random option to the effects selection flowcard.
  • Changed: The effects selection flowcard is now hidden from Gen1 devices and groups containing Gen1 devices.

v4.2.1 (unreleased)

  • Changed: Internal command processing has changed to mitigate errors when multiple commands are executed for the same device at once.

v4.2.0 (unreleased)

  • Added: Effect selection action flowcard is now available to retail devices as well.
  • Changed: API backend has been upgraded from polling to event based, massively reducing the traffic caused by the app.
  • Changed: Commands api is now using a managed command execution rather than a fire and forget strategy. This should actually populate any commands failing up to the UI and the flowcard system.

v4.1.0 (unreleased)

  • Added: Ability to select on device stored effects, using action flowcard, for Twinkly Pro devices.

v4.0.18

  • Fixed: A potential problem where the app could possibly crash due to the retrieved hue value being slightly out of range.
  • Updated: Athom OAuth library.

v4.0.16

  • Fixed: A potential problem where newly added grouped devices would not turn on.
  • Fixed: A rare race condition during device init could unexpectedly crash the app.
  • Fixed: Device capabilities are now limited to controllable capabilities correctly.
  • Fixed: An issue where the device status polling would not get disabled for devices which have been removed from Homey.
  • Fixed: A bug during status polling which would cause device infos not get updated if the device supports color temperature mode only.
  • Fixed: A potential bug when handling on/off versus dim value changes.
  • Fixed: A status info problem which would cause devices show available even if the API reports them as offline right after Homey device initialization.
  • Fixed: Toggling device back on now restores the last mode known by Homey.
  • Fixed: Device status in Homey should not bounce back to previous status anymore.
  • Fixed: Device on/off commands should be much more responsive now if toggled within a short period of time.
  • Updated: Improved unavailable error messages, now giving more information on what is wrong.
  • Updated: Homey oauth2 library.
  • Updated: The device unavailable status should now indicate when it is unavailable because of it being controlled by another Twinkly in group mode.

v4.0.12

  • Added: Support for the official Twinkly cloud api.
  • Added: Support for Homey Cloud.
  • Deprecation: This version deprecates the old lan protocol. Devices will still work but you should consider migrating to the cloud driver as soon as possible.

v3.0.6

  • Fixed: Dimming not working on SDKv3 version.
  • Fixed: Potential memory leaks when uninstalling/updating the app. Note: This only fixes the issue for upcoming updates/uninstalls. You might want to consider rebooting your Homey after this update.
  • Few minor under the hood changes to improve performance.

App ownership changed

v3.0.5 - 2021-02-22

  • Update to SDK3 (requires Homey firmware 5.x)
  • Added dimming capability
  • Minor improvements

v1.1.1 - 2019-12-18

Added an action card for switching demo mode on or off.

v1.1.0 - 2019-11-18

  • Autodiscovery has been added to make pairing easier
  • An action card for setting your Twinkly lights to a solid color has been added as extra functionality

v1.0.3 - 2019-02-07

  • FIX: improvements to pairing template for firmware 2.x
  • FIX: code refactoring in driver (replace callbacks with promises)

v1.0.2 - 2019-01-21

FIX: small fix to avoid app crashes when reconnecting after a disconnect

v1.0.1 - 2018-12-02

  • FIX: small improvement that might fix issues for some people

v1.0.0 - 2018-11-25

NEW: initial version