Backlog

Next up

In Progress

Done

Main Roadmap

Add Claude integration for the Creator Micro 2.

In Review

Anthropic Claude - Creator Micro 2

David Vazquez

It would be great to have the option to create unlimited layers (or at least significantly more than 6) within a profile.The current 6-layer limit can become quite restrictive when using the Creator Micro 2 Pro with many different applications. With AppSense/App Linking, it would be extremely useful to assign a dedicated layer to each application and have the device automatically switch to the correct layer when that application is active.I understand that the three LEDs may make it difficult to visually indicate a large number of different layers. However, this would not be an issue for me personally, since I rarely look at the LEDs and would use the device almost exclusively through App Linking / automatic application detection. I don't need to know which layer is currently active because the correct layer would be selected automatically based on the application I'm using.For example, I might want separate layers for Photoshop, Illustrator, Premiere Pro, After Effects, Blender, DaVinci Resolve, VS Code, Discord, Spotify, my browser, and many more.Even if there were no way to visually distinguish every layer through the LEDs, I would still strongly prefer having unlimited layers available in the software.Ideally, users could create as many layers as they need, with App Linking automatically selecting the appropriate layer based on the active application.This would make the Creator Micro 2 Pro much more flexible for power users who work with a large number of different applications.

Unlimited Layers for Unlimited Programs

ionqg-w27105

It would be great to have full control over the LEDs under the individual keys, including the ability to assign different colors to individual keys.For example, users could assign specific colors to certain functions so that important or frequently used actions visually stand out at a glance.Some possible use cases:<ul><li>Red for destructive actions</li><li>Green for frequently used or active functions</li><li>Blue for navigation controls</li><li>Yellow for recording or special actions</li><li>Different colors for different categories of shortcuts</li></ul>It would also be useful to have the option to turn individual key LEDs on or off independently, rather than having to use the same lighting behavior for all keys.This could make the Creator Micro 2 Pro much more intuitive to use, especially for complex workflows with lots of custom shortcuts. Being able to visually identify important functions immediately would be a huge quality-of-life improvement.

Per-Key LED Color Control

I use Wispr Flow heavily, and I was hoping to map the shortcut that triggers dictation to Wispr Flow to a key on my Creator Micro 2, but it doesn't seem like that works. I don't understand why.Does anyone else have this issue?

Using Wispr Flow with Creator Micro 2

It would be great to have an automatic sleep/standby mode for the Creator Micro 2 Pro.For example, users could set an adjustable timeout, such as 10 minutes, after which the device automatically enters standby if there has been no activity.Even better would be an option to automatically put the device into standby when the computer is shut down or goes to sleep.Ideally, this could include settings such as:<ul><li>Adjustable inactivity timeout (e.g. 5, 10, 15, 30 minutes)</li><li>Automatically enter standby when the computer is shut down</li><li>Automatically enter standby when the computer goes to sleep</li><li>Wake up automatically when the computer becomes active again</li></ul>This would be especially useful for reducing unnecessary power consumption and would make the device feel more polished and integrated with the computer's power management.

Auto Sleep / Standby Mode

I’m having an issue with Creator Micro 2 native Codex integration. The device works as a normal HID/input device, but the Codex-specific controls do not activate.Summary:<ul><li>Device: Creator Micro 2</li><li>Firmware: v0.6.1</li><li>Firmware source checked: latest Work Louder cm-v2-fw-releases release is v0.6.1</li><li>Input app: 0.18.0</li><li>ChatGPT/Codex app: 26.727.51351</li><li>macOS</li><li>USB VID/PID: 0x303a / 0x8298</li><li>Connection: USB-C wired</li><li>Device appears in macOS <code>hidutil list</code> as <code>Creator Micro 2</code></li></ul>Expected behavior:<ul><li>Long-pressing the dial in Codex should open the Codex Micro configuration panel.</li><li>The dial should adjust Codex reasoning level.</li><li>Voice / push-to-talk and Codex-specific mappings should work.</li></ul>Actual behavior:<ul><li>Normal key/HID behavior works.</li><li>Codex native controls do not work.</li><li>Long-pressing the dial does not open the Codex configuration panel.</li><li>Reasoning level and voice mode controls do not activate.</li></ul>Troubleshooting already completed:<ol><li>Updated Creator Micro 2 firmware to v0.6.1.</li><li>Confirmed v0.6.1 is the latest published Creator Micro 2 firmware.</li><li>Reset/deleted the Input profile from Input.app.</li><li>Quit Input.app completely.</li><li>Quit Chrome completely.</li><li>Restarted the Mac.</li><li>Reconnected the Micro by USB before opening other apps.</li><li>Confirmed no obvious keyboard utilities were running:<ul><li>Input.app not running</li><li>Chrome not running</li><li>Karabiner not running</li><li>Logitech Options not running</li><li>BetterTouchTool not running</li><li>Keyboard Maestro not running</li></ul></li></ol>Relevant macOS / app log evidence:Codex/Input successfully read the device firmware:<code>{"result":{"version":"v0.6.1"},"id":389,"method":"sys.version"}</code>Device status was also readable:<code>{"result":{"version":"v0.6.1","profile_index":0,"layer_index":1,"battery":100,"is_charging":true},"id":415,"method":"device.status"}</code>But when ChatGPT/Codex attempts native device access, macOS logs:<code>ChatGPT@(null): AppleUSBHostUserClient::openGated: failed to open Creator Micro 2@00100000: provider is already opened for exclusive access by AppleUSBHostCompositeDevice</code>The device then continues to enumerate normally as:<code>AppleUserHIDDeviceManufacturer: Work LouderProduct: Creator Micro 2VendorID: 12346ProductID: 33432PrimaryUsagePage: 1PrimaryUsage: 6</code>My read: The device is visible and responding over HID/RPC, and firmware is current. The failure appears to be in the native Codex control handshake or device-claim path, not in the Input profile or firmware update state.Can you confirm whether this is a known issue with Creator Micro 2 firmware v0.6.1 and ChatGPT/Codex app 26.727.51351 on macOS? If there is a beta firmware/app build, permission setting, or reset sequence needed for the Codex native mode, please send the exact steps.

Creator Micro 2 STILL not activating Codex native controls on macOS

Matt

Homebrew is a popular package manager used by many Mac OS users and developers. Having input as a Homebrew cask would make it a lot easier to install and update for those of us who use the program.Would the team consider adding input to Homebrew?

Adding input to Homebrew

nejm

Does the standard Creator Micro 2 get detected by the ChatGPT desktop app as a Codex Micro and support Agent Keys with live RGB chat status, push-to-talk and Codex settings without Work Louder Input? (or can be used in the same fashion)

Is Creator Micro 2 also detected by Codex / ChatGPT app?

PeterP

I’d like to request a dedicated macOS / Apple Keyboard preset in Input.Instead of only adding a few individual shortcuts, it would be very helpful if Knob1 could support a more complete set of macOS-native system keys and function-row actions, so it can behave more consistently with a native Mac keyboard.For example: Globe / Fn Spotlight Search Do Not Disturb …Some of these actions can be recreated with custom shortcuts or third-party tools, but having them built directly into Input as official macOS actions would make the experience much easier, cleaner, and more reliable for Mac users.

Add a macOS / Apple Keyboard preset for native Mac function keys

Neiko

Environment: Creator Micro V2 / Input 0.18.0 / firmware flashed 0.4.0 to 0.6.1 / macOS over Bluetooth, also seen on Windows 11.A single physical key press registers as two or more presses. It affects every key, not one switch.THE DECISIVE TEST: after the problem survived the firmware update, I ran a full “Reset settings” from the Setup tab, leaving the device factory-blank (no custom layers, no macros, no Multi keys). I then assigned a single plain letter A to one key via Basic, opened a plain text editor, and tapped it slowly ten times. I still get doubled characters (aa) from single presses.That rules out everything on my end: not my keymap (device was wiped), not Multi-key logic (none existed), not macro complexity (a single unmodified keystroke).TIMING DETAIL: before the reset I built a Multi key to characterise it (tap types 1, double-tap types 2, hold types 3).<ul><li>One quick tap: expected 1, got 1 or 2</li><li>- Deliberate double-tap: expected 2, got 2, 22, or 21</li><li>- Hold ~1 second: expected 3, sometimes got 31</li></ul>A single tap yielding 2 means one press bounces into two contacts inside the 250ms tap window. Hold yielding 31 means the RELEASE bounces too: the hold fires, then letting go registers as a fresh tap. So the board chatters on both make and break.This also corrupts ordinary single-action keys, not just Multi keys. A Delete key can remove two items from one press, which makes the pad risky to use in Outlook.ALSO: since flashing 0.6.1, the Firmware version field in Setup displays blank. Device model and Input version populate normally. It read 0.4.0 before the update. Possibly unrelated, possibly a sign the flash did not complete cleanly.I saw the report here about a corrupted keymap.json surviving a firmware update and producing repeated key input (“endless K”). Mine looked similar, which is why I tried the reset, but the reset did not resolve it.QUESTIONS:<ol><li>Is this known on this hardware revision or firmware line?</li><li>2. Is there a debounce / tapping-term setting, or a firmware build with a longer debounce window?</li><li>3. Should the Firmware version field be blank after a successful 0.6.1 flash?</li><li>4. If this is a hardware fault, what is the warranty process?</li></ol>Happy to run any diagnostic or reflash. My profile is exported, so wiping the device again costs me nothing.

Creator Micro V2: all keys double-fire (chatter) — persists after factory reset AND firmware 0.6.1

CrockDaddyFlex

Hi Work Louder team,I've just ordered a Creator Micro 2 Pro. Before it arrives I'd like to check what's possible on the host side, so I build the right thing rather than guess.I'm writing a small local macOS app for my own use that supervises coding-agent sessions - conceptually the same job the Codex Micro does for Codex, but for a different tool and running entirely on my own machine. Mapping keys to actions is straightforward with Input. What I'd like to know is whether the feedback direction is available to me: lighting individual keys from my own app to show live status, the way the Agent Keys work on the Codex Micro.Three specific questions:<ol start="NaN"><li>Does the Creator Micro 2 expose a raw HID interface (QMK-style usage page <code>0xFF60</code>, or any vendor-specific interface) that a third-party host application can open and write to?</li><li>Is there a supported or permitted way to set per-key RGB from a host app — an Input API, a documented report format, a local socket, anything? I understand the Codex integration is a specific partnership; I'm asking about the general capability, not access to that integration.</li><li>If nothing exists today, is it something you'd consider? A documented "set key N to colour X" channel would make the Micro the obvious controller for any agent-style tool, not only Codex — that seems like it's in your interest as much as mine.</li></ol>Also useful to know, if you can say: is the Creator Micro 2 firmware QMK/VIA-based like the original Creator Micro, or a different stack? I noticed the v2 isn't in QMK mainline, so I don't want to assume.Happy to be pointed at docs if these are already answered somewhere — I couldn't find them.Thanks, Paulo

Planned

Can a third-party app drive per-key RGB on the Creator Micro 2?

Paulo Ribeiro

I love my Creator Micro, but there is one feature I wish it had. I really like how it switches layers when a specific program is in focus, but it would be great if it reverted to a default layer when no specific programs are active. When I’m working in Illustrator, I don't want the same functions active in Chrome or File Explorer. It’s possible this feature already exists and I just haven’t found it yet.

Мне очень нравится моя мышь Creator Micro, но есть одна функция, которую я бы хотел в ней видеть. Мне очень нравится, как она переключает слои, когда в фокусе находится конкретная программа, но было бы здорово, если бы она возвращалась к слою по умолчанию, когда ни одна конкретная программа не активна. Когда я работаю в Illustrator, я не хочу, чтобы те же функции были активны в Chrome или Проводнике. Возможно, эта функция уже есть, а я просто ещё не нашел её.

Переключаться на «слой по умолчанию», когда ни одно из подключенных программных обеспечений не находится в фокусе

Switch to a "default layer" when no linked software is in focus

Kollegard

A firmware update to use the CM1 with Input app! 🙏

Input support for the Creator Micro v1 (legacy)

Riccardo Delfanti

Idea: Improve ‘Actions’ and ‘Multi’ tabs to allow individual key assignments to be done via the icon grid, rather than selecting from the nested drop down list.The drop down list is ‘hard’ to navigate:<ul><li>Key names are often truncated (shared sentiment with existing feedback posts)</li><li>Drop down list shows 5 selectable keys in view while 10 section labels are always visible —&gt; only 1/3 of the 'rows’ are actionable</li><li>Feels sluggish for the core feature</li></ul> IMO, it would be much easier to select keys from the icon view that’s already used when assigning keys from the ‘Basic’ list to Framer. Screenshot below shows how much unused space is available and how this could fit cleanly (says the non-UI guy making mocks in Excel).<ul><li>2 less clicks per key assignment, ∞ less scrolling (NOW that’s what I call IMPACC)</li><li>More direct, less navigation</li><li>Visible keys per view go from 5 —&gt; 40+</li><li>Consistent UI for all 3 tabs</li><li>Appeases that 1 annoying customer who made 3 posts in one day</li></ul><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/69437b55da4c4d1a9770f383/019b2f23-1009-72da-a0aa-341eccbdc687/b64u-aW1hZ2UucG5n.png" data-featurebase-content-filename="image.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/69437b55da4c4d1a9770f383/019b2f23-1009-72da-a0aa-341eccbdc687/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=8aed8f9b2a9e856114b3eae8ed7c1b4cde7923529b8d7364ff76ffa8d5cab01a">

Input UI improvements

Scott Lanning

I received my Framer CM2 a few days ago, and I had been hoping to use the joystick on the CM2 for arrow keys so I wouldn’t have to take up four whole buttons for them, but apparently there is no way to remap the down direction on the joystick. It would be nice if there would be a way to move or get rid of what I’m told is the radial backout option (as an aside: if the device is meant to be displaying some kind of menu when using the joystick, I have not been able to get that to display nor is there any documentation describing this feature or how it works). I saw in the backlog in the discord one of the WL people claimed there would be a way to toggle the joystick between the menu and “joystick mode” but that does not appear to be the case as far as I can tell (unless I’m missing something, again there is no documentation to reference). Personally, I’d appreciate it if there was an option to use the joystick just for regular keystroke inputs without a menu (ideally on press rather than on release in this sort of mode). And also it’d be nice if there was some kind of documentation at all about the features of both the CM2 and Input—I’ve seen the setup video/quickstart guide, but while it looks very nice, I don’t mean to be rude, but it’s wholly inadequate even to introduce the products’ basic features. As I alluded to before, I wouldn’t even know there (maybe? is this even still a thing?) is supposed to be some kind of menu appearing when using the joystick, or what that un-remappable X is meant to represent if I hadn’t been lurking the discord for months for updates on the project.

More options for the CM2 joystick please (also in desperate need of more documentation)

good_haro

Not sure if this is a function but if so it doesn’t seem to be working on mine. But I accidentlly left my Creator Micro V2 on overnight and it didn’t automatically power off. Is this a feature, if not, is it something the user could set to do, along with how long till it does this within Input?

Automatic Power-Off

Tom Watson

Just getting to know the keyboard, but some things I'd really like to see after first impressions (I’m on Mac M1 btw).<ol><li>Auto-detect default: I’ve set up a layer to auto-detect on a particular bit of software, but when I exit that software, I'd like the device to reset the layer back to layer 1. I can't see anywhere where this is possible. I have to manually touch the layer select button to go back to layer one. It would be great to be able to select a layer that auto-selects when no auto-detect software has been detected.</li><li>Edit radial button broken?The edit radio button menu is broken in the latest release. In the setup video, you show the ability to add multiple options when using the radio button, but I can't see that menu anywhere.</li><li>Rotate button cycle through different actions: I think I can achieve the same feature with the radial button (if the edit button gets fixed) but I'd love to be able to cycle through a set of actions by rotating the dial. For instance, I'm using Claude code, and I'd like to cycle through a defined set of shortcuts as I rotate, rather than it essentially acting as a repeater for the same key</li><li>Open Software: I'd love to be able to open specific software with a key press!</li><li>Repeated options in modifiers: when I create an action and assign a key, looking into modifiers: Option, Command, Control, and Shift are repeated in the menu. They are also repeated under modifiers under basic</li></ol>

Feedback First hour of use.

Samuel Gregory

<img src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/694a4c95112237b38e5333d5/019b4a37-892d-7d91-acd3-e2bb9a0a4003/b64u-MDE5YjRhMzctODkxZi03NGMxLTkxMDktMTJhMjZlZmYxODM2.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=aa816ebae692721feb714a4f9db58f29dc85f3d71509d3fe4ae7a4b307f9ae86" data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/694a4c95112237b38e5333d5/019b4a37-892d-7d91-acd3-e2bb9a0a4003/b64u-MDE5YjRhMzctODkxZi03NGMxLTkxMDktMTJhMjZlZmYxODM2.png" data-featurebase-content-filename="019b4a37-891f-74c1-9109-12a26eff1836">Like with the Knob1, it would be very useful to have these as things you can bind for on the go, when you can’t open Input for any reason (e.g., being in a work environment that disallows external software that isn’t whitelisted).

Backlight and Underglow Brightness Control via Key Press

Legendary-Wizard

Might already be on the roadmap, but a setting to determine the number of minutes before most of the LEDs DIM to save battery life. Maybe the bottom right key with the transparent cap stays on but dim to show the device is still on, but all the rest turn off to save batt?

Creator Micro v2 - Power saving features

Nick Collura

I'm on a Mac and I use a QWERTY keyboard (Apple Wireless Keyboard) and it's set up in the settings to be Dvorak. When I go to record an action, it ignores this override and registers the key input of the QWERTY keyboard.I can imagine a world where some people would want to have this setting optional. So maybe some sort of indication or toggle to use QWERTY settings or keyboard override settings.<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/69429cd76989e9ecb4c9e77a/019b2c34-12ec-7002-a86c-a6c903ff037c/b64u-Q2xlYW5TaG90IDIwMjUtMTItMTcgYXQgMTIuMDYuMDBAMngucG5n.png" data-featurebase-content-filename="CleanShot 2025-12-17 at 12.06.00@2x.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/69429cd76989e9ecb4c9e77a/019b2c34-12ec-7002-a86c-a6c903ff037c/b64u-Q2xlYW5TaG90IDIwMjUtMTItMTcgYXQgMTIuMDYuMDBAMngucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=7c35509d78b70a4dc75d97cb71a59dac880f89baa448b67003c03fc883eb0089">

Recording actions does not respect non-ANSI keyboard settings

The device doesn’t seem to want to sleep and subsequently keeps waking up my computer.I’m on Mac M1 and have latest firmware installed

Creator Micro v2 Wont Sleep

Would be awesome to have a way of knowing the battery status directly through Input app and/or through the RGB present in the Framer Creator Micro. Aside from when it’s in bluetooth mode, that forces me to remove the cable &amp; connect wirelessly, I can’t see how much battery the device currently has.

Battery Status

João Dória

As a product designer, I see several issues in Input’s current UI and UX that impact usability, consistency, and perceived product maturity. Below is a structured summary of areas that could be improved:<ul><li>Once an icon is assigned to an action, there is no way to remove it without deleting and recreating the entire action. It would be more user-friendly to allow clearing or resetting the icon directly.</li><li>When creating a new multi-action, selecting keys/actions from long dropdown lists can become cumbersome. Providing search within these dropdowns would make it much easier and faster to find the desired key or action.</li></ul><ul><li>The interface appears to use multiple icon libraries, which results in visual inconsistency. Standardizing on a single, cohesive icon set (such as an open-source library like Lucide which contains thousands of icons) would improve visual harmony and make it easier for users to find relevant icons.</li><li>Whenever an action is created or modified, the hardware updates immediately, which feels slow and interrupts the workflow. Providing a setting to switch between manual and automatic updates would make the experience more efficient.</li><li>The “My actions” section in the drawer can become difficult to manage when working with multiple apps and many shortcuts. As the list grows, it becomes harder to locate the right action. Allowing users to organize actions into groups or folders (for example, by app or context) would significantly improve navigation and usability.</li><li>Requiring users to open a drawer every time they want to add or edit an action introduces unnecessary friction. Making this interface persistent (such as a sidebar that remains visible) would reduce repetitive interactions and make better use of screen real estate.</li><li>Basic keyboard shortcuts are not consistently supported within Input. For instance, using ⁠cmd + A to select the entire HEX code in the RGB context menu does nothing. Supporting standard platform shortcuts (select all, copy, paste, undo, etc.) would make the product feel more polished and efficient for power users.</li><li>From an accessibility standpoint, the app appears to use relatively small font sizes and button styles with insufficient contrast. Increasing type sizes where appropriate and ensuring buttons meet recommended contrast ratios would improve readability and make the app more inclusive.</li><li>Many interactive elements do not have tooltips or any form of inline explanation. Adding concise, informative tooltips for icons, controls, and less obvious features would reduce the learning curve and help users build confidence faster.</li></ul>Overall, the app currently gives the impression of being somewhat unfinished or in an early stage. Addressing the issues above, tightening visual consistency, and refining interaction details would substantially improve the quality and maturity of the product.

Feedback on Input’s UI and UX

Balázs Barta

It would be helpful if we were able to create custom groups of actions and multiactions to be able to organize them. At this point i have to hover to figure out if an action is set for mac or windows or app specific. If we could group them(like when you import presets) it would be much easier.

Create Groups for Actions/Multi Actions

Milan Baweja (Djmvlan)

WL Team Edit: GIF Support is planned for Q2 2026. Upload a static image to Input and AI will create an animated/looping gif of your image for the display. Users can also directly upload an existing gif as a background for the Nomad and/or Knob1.

Knob1, Nomad - GIF Support

wrkboi

With the NomadE keyboard connected (software v0.3.3), my Mac Pro updated to the latest OS keeps showing this error message again. It has been happening for quite a while and across several updates. Any advice?<img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/6946a5c9c77d4e31fafa9341/019b3bf7-08ce-740a-a563-f11674195c5d/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTIwIGFsbGUgMTQuMjguMDgucG5n.png" data-featurebase-content-filename="Screenshot 2025-12-20 alle 14.28.08.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/6946a5c9c77d4e31fafa9341/019b3bf7-08ce-740a-a563-f11674195c5d/b64u-U2NyZWVuc2hvdCAyMDI1LTEyLTIwIGFsbGUgMTQuMjguMDgucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=0e60f75620391e51e62aed8a68f6e67a1d9813bc4c329a347bb5e9be1c408a9e">

Firmware update issue Input NomadE

Lorenzo Palazzolo

Hi,I was setting up the new device for a bit and tested around in Figma, and the “input” app somehow suddenly not recognizing the device anymore and showing the “No device found Please connect your device” message. Firmware has been updated to v.023 when first connected.Also tried connecting the device via BT but it didn’t show up in the Near By Device section.Please help debug this. Thanks. Btw if user can reset the device to default with the device itself it would be great.

No device found error Creator Micro v2

Ka Yu Ling

I’ve noticed a severe battery drain issue when using my Figma Creator Micro Pro in Bluetooth mode.When the device is fully charged and I switch to Bluetooth, the battery drops from 100% to 1% within a few minutes. I can literally watch the percentage decrease in real time in macOS System Settings. This makes the device essentially unusable in wireless mode.I understand that battery life won’t be unlimited, but I would expect at least a couple of hours on a full charge, not just minutes.To rule out lighting as the cause, I tested two scenarios:<ul><li>Backlight intensity at 50% (my usual setting when plugged in)</li><li>Backlight intensity at 0% </li></ul>In both cases, the battery drained extremely fast with no noticeable difference.I can also see that, when I press the on/off button the rgb lights going from green to yellow shortly after connecting FCM throug bluetooth (and the device was plugged in the entire day to my Mac mini). Input version: 0.12.5Firmware version: 0.2.2OS: MacOS Sequoia 15.7.2

Creator Micro v2 - Battery Drain Over Bluetooth

I have multiple computers that I switch between. I want to have my Creator Micro V2 wired into my monitor/hub and it would just work with any computer I hook to that monitor/hub. But every time I disconnect a computer it goes into Bluetooth mode (first LED flashing fast and blue pulsing underflow), and it doesn’t exit that mode when you plug in the new computer. You have to tap on the touch button 3 times to cycle through all the Bluetooth paring slots, and get back to USB. Is there some way to have it always prefer USB, or disable Bluetooth entirely? Currently on firmware v0.4.0, Input 0.17.1

Creator Micro V2 USB only, ignore Bluetooth

jamone

I received my Framer Micro v2 two days ago. At first glance, the build quality was amazing, and I really loved the design. However, my excitement didn't last long.After just 30 minutes of happily mapping keys, the device suddenly became completely unresponsive. I spent about two hours wrestling with it, and eventually had to open up the case to force a hard reboot on the PCB. After struggling for another hour, I finally managed to bring it back to life. (Yay!)But the relief was short-lived. Less than an hour later, it froze again. I rebooted it, it worked for an hour, and then it died again... It has been an endless loop. I've had to hard reboot this device five times in just two days. I think we can agree this is definitely not normal behavior.Just in case it was a connectivity issue, I even purchased two of the highest-quality cables available here in Korea to test it, but the results were exactly the same.This experience has been incredibly stressful. I would like to request an exchange for a fully functional unit or a refund.

5 Reboots in 2 Days - Requesting a replacement (Defective Unit)

Byeongsu Kim

<h1>SOLUTION: Follow the steps in this document</h1><file-preview-component data-featurebase-content-filename="c_micro_v2_complete_reflash_guide.pdf" data-featurebase-content-filesize="1449838" data-featurebase-content-filetype="application/pdf" data-featurebase-content-key="691bd17fee65b59cfee04021/post/693e9eb86ed43553065c6d74/019b4b5d-9cd7-7964-8d58-fbd7dd3866a7/b64u-Y19taWNyb192Ml9jb21wbGV0ZV9yZWZsYXNoX2d1aWRlLnBkZg.pdf" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/693e9eb86ed43553065c6d74/019b4b5d-9cd7-7964-8d58-fbd7dd3866a7/b64u-Y19taWNyb192Ml9jb21wbGV0ZV9yZWZsYXNoX2d1aWRlLnBkZg.pdf?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=5f6758a17497df4006e4bc5b200c18a452ed9514a1d3b13f3155f1e6b6aa7204"></file-preview-component>I’ve just updated the firmware on the Creator Micro v2 (CMv2) to the latest firmware version (v0.2.2 I believe) and even though the software said that the update was successful, after unplugging it, the device won’t turn on anymore at all.I went through a few TS steps, such as making sure I’ve got a functioning cable to test with plugging it in and then unplugging it. Made sure it’s fully charged, which it seems to be.SO far, nothing. It’s dead. Bit at a loss now…guess it’s a paperweight now? :(

<h1>해결 방법: 이 문서의 단계에 따라 진행하십시오</h1><file-preview-component data-featurebase-content-filename="c_micro_v2_complete_reflash_guide.pdf" data-featurebase-content-filesize="1449838" data-featurebase-content-filetype="application/pdf" data-featurebase-content-key="691bd17fee65b59cfee04021/post/693e9eb86ed43553065c6d74/019b4b5d-9cd7-7964-8d58-fbd7dd3866a7/b64u-Y19taWNyb192Ml9jb21wbGV0ZV9yZWZsYXNoX2d1aWRlLnBkZg.pdf" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/693e9eb86ed43553065c6d74/019b4b5d-9cd7-7964-8d58-fbd7dd3866a7/b64u-Y19taWNyb192Ml9jb21wbGV0ZV9yZWZsYXNoX2d1aWRlLnBkZg.pdf?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=5f6758a17497df4006e4bc5b200c18a452ed9514a1d3b13f3155f1e6b6aa7204"></file-preview-component>방금 Creator Micro v2(CMv2)의 펌웨어를 최신 버전(v0.2.2인 것 같습니다)으로 업데이트했는데, 소프트웨어에서는 업데이트가 성공했다고 표시되었음에도 불구하고, 케이블을 뽑은 후 기기가 아예 켜지지 않습니다.케이블이 정상적으로 작동하는지 확인하기 위해 연결했다가 분리하는 등 기술 지원(TS) 단계 몇 가지를 시도해 보았습니다. 배터리가 완전히 충전되었는지 확인했는데, 충전된 것 같습니다.하지만 지금까지 아무 반응도 없습니다. 완전히 고장 난 것 같아요. 이제 어떻게 해야 할지 막막하네요… 이제 그냥 문진으로 써야 할까요? :(

[해결됨] 펌웨어 업데이트 v0.2.2로 인해 Creator Micro v2가 작동하지 않음

Completed

[SOLVED] Firmware Update v0.2.2 Kills the Creator Micro v2

Bristol Drones

Environment:<ul><li>macOS</li><li>Codex Micro</li><li>Work Louder Input 0.17.1</li><li>Device firmware v0.4.1</li><li>ChatGPT desktop app with Codex integration</li></ul>Issue: ChatGPT takes global control of the Codex Micro underglow and overrides the lighting configured for non-Codex layers.Steps to reproduce:<ol><li>In Input, configure Layer 2 with custom key backlighting and underglow at nonzero brightness.</li><li>Completely quit ChatGPT.</li><li>Switch to Layer 2. Both the key LEDs and underglow work correctly.</li><li>Open ChatGPT.</li><li>Switch between the Codex layer and Layer 2.</li></ol>Actual behavior:<ul><li>Opening ChatGPT overrides the device lighting.</li><li>On Layer 2, the configured key LEDs can still illuminate, but its configured underglow remains off.</li><li>Quitting ChatGPT restores the Layer 2 underglow.</li><li>The issue reproduces in both directions regardless of which layer is active when ChatGPT launches.</li></ul>Expected behavior: ChatGPT should control Codex status lighting only while the Codex layer is active. On Layers 2–6, firmware should release RGB control and apply that layer's backlight and underglow settings from Input.Diagnostics:<ul><li>Input successfully saves the Layer 2 lighting configuration.</li><li>Input logs show successful lights.preview and fs.writebin calls.</li><li>After ChatGPT opens, the logs show Codex-specific v.oai.rgbcfg commands.</li><li>The hardware and LEDs are confirmed working because all configured lighting operates normally when ChatGPT is closed.</li></ul>This appears to be a lighting-ownership conflict between ChatGPT's Codex integration and the per-layer Input configuration.

[SOLVED] Codex Micro: ChatGPT overrides underglow on non-Codex layers

Zandre Azogue

Hey everyone, If you’re experiencing problems with battery charging on your Creator Micro v2 or Knob1, please read the whole post before installing the diagnostic firmware.IMPORTANT NOTE: This update does NOT include a fix. It is designed solely to gather diagnostic data so we can understand what is preventing the charging cycle from completing. Installing it is not mandatory, but your participation would greatly help us resolve the issue. We’ve already solved about 90% of the charging issues reported so far, thanks to everyone who submitted feedback. However, there’s still a small number of cases where the problem persists, and we need to gather more information to identify and fix them.We are in contact with the chip manufacturer to figure out what’s going on, and your detailed reports are essential.Please include in your comment:<ul><li>What exactly happens when you try to charge (LED behavior, percentage stuck, etc.)</li><li>Which cable and adapter you’re using</li><li>Whether charging ever worked correctly</li><li>Any other symptoms</li></ul>To ensure we collect detailed diagnostic data on your specific case, we have created a custom version of Input and a matching device firmware with an integrated system which collects battery information and charging status. We kindly ask you to leave Input open in the background so the diagnostics can run continuously. You can keep using your device as usual during this process!The more data we are able to collect, the faster we are be able to provide a definitive fix.<h2>Instructions</h2>First, download and install the custom Input application that matches your operating system:<ul><li>Input for Mac (Apple Silicon): <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-0.13.1-rc.4-arm64.dmg">input-0.13.1-rc.4-arm64.dmg</a></li><li>Input for Mac (Intel): <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-0.13.1-rc.4.dmg">input-0.13.1-rc.4.dmg</a></li><li>Input for Windows: <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-Setup-0.13.1-rc.4.exe">input-Setup-0.13.1-rc.4.exe</a></li></ul>Next download only the firmware that matches your device model from this post:<ul><li>Creator Micro V2 custom firmware:<a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/firmware_cmv2_v0.3.0-rc.2_merged.bin">firmware_cmv2_v0.3.0-rc.2_merged.bin</a></li><li>Knob1 custom firmware: <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/firmware_knob1_v0.3.2-rc.3_merged.bin">firmware_knob1_v0.3.2-rc.3_merged.bin</a></li></ul>⚠️ IMPORTANT NOTE: Due to the diagnostic data being sent from the device, you might notice a small delay in typing every 10 seconds. This is completely normal and will go away when you decide to go back to the stock firmware.Finally install the custom firmware, to do so follow these steps carefully:<ol><li>Open the Input application and connect your device via USB. (If you have other Work Louder products turn them off)</li><li>Once the device appears in Input, go to the Setup tab.</li><li>Click Advanced Flash.</li><li>Click Bootloader and wait until the button turns yellow. This means the device is in bootloader mode.</li><li>Click Choose firmware file and select the custom firmware you downloaded.</li><li>Click the Flash button that appears and wait until the flashing process finishes.Do NOT disconnect the device during flashing.</li><li>When finished, exit the Advanced Flash screen.</li></ol>After the custom Input application and firmware are installed, you may continue using your device as usual.Thank you for reporting! Great new is that this is something 100% fixable in software and we just need to tweaks the right levers.

여러분, Creator Micro v2 또는 Knob1에서 배터리 충전 문제가 발생하신다면, 진단 펌웨어를 설치하기 전에 본 게시글 전체를 꼭 읽어주세요.중요 참고: 본 업데이트는 문제 해결을 위한 패치가 아닙니다. 충전 주기 완료를 방해하는 원인을 파악하기 위한 진단 데이터 수집 전용으로 설계되었습니다. 설치는 필수가 아니나, 여러분의 참여는 문제 해결에 큰 도움이 될 것입니다. 지금까지 보고된 충전 문제의 약 90%는 여러분의 피드백 덕분에 해결되었습니다. 그러나 여전히 소수의 사례에서 문제가 지속되고 있으며, 이를 식별하고 수정하기 위해 더 많은 정보가 필요합니다.현재 칩 제조사와 협력하여 문제 원인을 파악 중이며, 여러분의 상세한 보고가 필수적입니다.댓글에 다음 내용을 포함해 주십시오:<ul><li>충전을 시도할 때 정확히 어떤 현상이 발생하는지 (LED 상태, 충전률 멈춤 등)</li><li>사용 중인 케이블 및 어댑터 종류</li><li>충전이 정상적으로 작동한 적이 있는지</li><li>기타 증상</li></ul>귀하의 특정 사례에 대한 상세한 진단 데이터를 수집하기 위해, 배터리 정보와 충전 상태를 수집하는 통합 시스템이 적용된 맞춤형 Input 버전과 해당 기기 펌웨어를 제작했습니다. 진단이 지속적으로 실행될 수 있도록 Input을 백그라운드에서 실행 상태로 유지해 주시기 바랍니다. 이 과정 동안 평소처럼 기기를 계속 사용하셔도 됩니다!수집할 수 있는 데이터가 많을수록, 저희가 확실한 해결책을 더 빨리 제공할 수 있습니다.<h2>사용 방법</h2>먼저, 사용 중인 운영 체제에 맞는 맞춤형 Input 애플리케이션을 다운로드하여 설치하세요:<ul><li>Mac용 Input (Apple Silicon): <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-0.13.1-rc.4-arm64.dmg">input-0.13.1-rc.4-arm64.dmg</a></li><li>Input for Mac (Intel): <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-0.13.1-rc.4.dmg">input-0.13.1-rc.4.dmg</a></li><li>Input for Windows: <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/input-Setup-0.13.1-rc.4.exe">input-Setup-0.13.1-rc.4.exe</a></li></ul>다음으로, 본 게시물에서 기기 모델에 맞는 펌웨어만 다운로드하세요:<ul><li>Creator Micro V2 맞춤형 펌웨어:<a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/firmware_cmv2_v0.3.0-rc.2_merged.bin">firmware_cmv2_v0.3.0-rc.2_merged.bin</a></li><li>Knob1 커스텀 펌웨어: <a target="_blank" rel="nofollow" class="Truncate link" href="https://github.com/worklouder/input-releases-internal/releases/download/battery.charging.diagnostic/firmware_knob1_v0.3.2-rc.3_merged.bin">firmware_knob1_v0.3.2-rc.3_merged.bin</a></li></ul>⚠️ 중요 참고: 장치에서 진단 데이터가 전송되기때문에 10초마다 타이핑에 약간의 지연이 발생할 수 있습니다. 이는 완전히 정상적인 현상이며, 기본 펌웨어로 되돌리기로 결정하면 사라집니다.마지막으로 커스텀 펌웨어를 설치하려면 다음 단계를 주의 깊게 따르세요:<ol><li>Input 애플리케이션을 열고 USB로 장치를 연결하세요. (다른 Work Louder 제품이 있다면 전원을 끄세요)</li><li>Input에 기기가 표시되면 설정 탭으로 이동하세요.</li><li>고급 플래시를 클릭하세요.</li><li>부트로더를 클릭하고 버튼이 노란색으로 변할 때까지 기다리세요. 이는 기기가 부트로더 모드에 진입했음을 의미합니다.</li><li>펌웨어 파일 선택을 클릭하고 다운로드한 커스텀 펌웨어를 선택하세요.</li><li>표시되는 플래시 버튼을 클릭하고 플래싱 프로세스가 완료될 때까지 기다리십시오.플래싱 중에는 절대로 장치를 분리하지 마십시오.</li><li>완료되면 고급 플래시 화면을 종료하십시오.</li></ol>사용자 지정 입력 애플리케이션과 펌웨어가 설치된 후에는 평소처럼 기기를 계속 사용할 수 있습니다.보고해 주셔서 감사합니다! 좋은 소식은 이 문제가 소프트웨어로 100% 해결 가능하며, 적절한 조정만 필요하다는 점입니다.

Creator Micro v2, 노브1 - 배터리 충전 문제 (메가스레드)

Creator Micro v2, knob1 - Battery charging issue (MEGATHREAD)

Davide // Work Louder

WL Team Edit: We are planning to implement an overlay cheat-sheet (similar to what happens to the radial menu), you can trigger with a specific key. It would be incredible to do a higher end version of the Creator Micro where the keys have digital, backlit icons that dynamically change based on the layer you’re on, app you’re in, etc. I would pay extra money for that.To be honest, sometimes I forget what I mapped where on my blank keycaps (I keep them blank because I work within 3 main apps). I would be willing to pay a good amount more for this feature.

Creator Micro v2 - Cheat Sheet Overlay

Joel Machemer

I’ve got a creator micro 2. I’d like to be able to write custom scripts/macros. For instance, terminal commands or open certain apps or links (relying on default apps to open the links). In general, I could accomplish this with the ability to run shell scripts. For macos, I could accomplish this with the ability to run <code>osascript</code> scripts. (There’s also the Shortcuts app…but that adds a lot of bulk/overhead and organizing them is a pita.) There are also third-party tools that allow the writing of custom macros, like [karabiner-elements](<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://karabiner-elements.pqrs.org">https://karabiner-elements.pqrs.org</a>) and [skhd](<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://github.com/asmvik/skhd">https://github.com/asmvik/skhd</a>) — skhd is my personal preference because it’s super fast. Are there any workarounds or plans to do support this?

Creator Micro v2 - Open Apps/links/custom scripts

Erik Thorelli

I keep getting the “We need Input monitoring permissions” even though I’ve already provided the correct permissions. I’ve tried with both bluetooth and wired. I’m using the Knob1 macOS Version 15.6.1 (24G90) Input Version 0.12.2 (0.12.2) It works fine on Windows. <img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/691ebdc6ba3da7283b247ce0/019aa014-dc40-7c5a-95fc-452ea849258d/b64u-Q2xlYW5TaG90IDIwMjUtMTEtMjAgYXQgMDguMDQuNDBAMngucG5n.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/691ebdc6ba3da7283b247ce0/019aa014-dc40-7c5a-95fc-452ea849258d/b64u-Q2xlYW5TaG90IDIwMjUtMTEtMjAgYXQgMDguMDQuNDBAMngucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=85e320e2ebe52c16133920e9a238f12ba137debba0160c148bbfbe2d0473b489" data-featurebase-content-filename="CleanShot 2025-11-20 at 08.04.40@2x.png"><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/691ebdc6ba3da7283b247ce0/019aa014-eb0b-7753-883e-f825ef9bb6d2/b64u-Q2xlYW5TaG90IDIwMjUtMTEtMjAgYXQgMDguMDQuNTBAMngucG5n.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/691ebdc6ba3da7283b247ce0/019aa014-eb0b-7753-883e-f825ef9bb6d2/b64u-Q2xlYW5TaG90IDIwMjUtMTEtMjAgYXQgMDguMDQuNTBAMngucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=938fc6a0e21e1a22fc1a7268c1db82ebc90dceef3d9eb4cabfab48b63a407ab0" data-featurebase-content-filename="CleanShot 2025-11-20 at 08.04.50@2x.png">

MacOS "We need Input monitoring permissions"

mads-hartmann

Hi everyone, this is a demo post! :)

Hello 👋🏻

It would be great to add a bug report modal form to the Input platform. When a user submits a bug report or feature request, it creates an issue or ticket in the Input repository with the information provided by the user.To combat spam, authentication, such as GitHub authentication, would be necessary before allowing users to submit their reports or requests.

Bug Report/Feature Request Form in Input

Conner Luzier

After watching the video on how Input works, I saw that I could add icons to actions on my FCM but currently it’s bugged &amp; only shows momentarily before collapsing/hiding again.Input version: 0.12.2<video data-width="100%" data-align="left" alt="" data-featurebase-content-filename="Screen Recording 2025-11-20 at 18.13.33.mov" data-featurebase-content-key="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJvYmplY3RLZXkiOiIwMTlhYTI4NS0zN2NjLTcxYjctYTE1Mi01NmM0YTc2NDEwZmIiLCJ0eXBlIjoidmlkZW8tdXJsIiwicmVzb3VyY2VJZCI6IjY5MWY1ZGI5YTBlODE1Y2I0NTY1N2UxMCIsInJlc291cmNlVHlwZSI6InBvc3QiLCJvcmdJZCI6IjY5MWJkMTdmZWU2NWI1OWNmZWUwNDAyMSIsImlhdCI6MTc2MzY2MzI4OX0.Hl8Memwudfiu8d63FAxopxTZJ_B51gmbcBY18Hg_LTo" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/videos/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJvYmplY3RLZXkiOiIwMTlhYTI4NS0zN2NjLTcxYjctYTE1Mi01NmM0YTc2NDEwZmIiLCJleHAiOjE3OTAwMDY0MDAsInR5cGUiOiJ2aWRlby11cmwiLCJvcmdJZCI6IjY5MWJkMTdmZWU2NWI1OWNmZWUwNDAyMSIsInJlc291cmNlSWQiOiI2OTFmNWRiOWEwZTgxNWNiNDU2NTdlMTAiLCJyZXNvdXJjZVR5cGUiOiJwb3N0In0.7zVqvLxtmdS3zlqRqi_oy0COzt237H_-PrRvXM3iDyo/manifest.mpd"></video><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="691bd17fee65b59cfee04021/post/691f5db9a0e815cb45657e10/019aa283-c42d-7e3b-a21c-6643d502e711/b64u-U2NyZWVuc2hvdCAyMDI1LTExLTIwIGF0IDE4LjEyLjMzLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-11-20 at 18.12.33.png" src="https://691bd17fee65b59cfee04021.featurebase-attachments.com/c/post/691f5db9a0e815cb45657e10/019aa283-c42d-7e3b-a21c-6643d502e711/b64u-U2NyZWVuc2hvdCAyMDI1LTExLTIwIGF0IDE4LjEyLjMzLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260921T150000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260921%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=76efdce036fbf9cf57e2f928c57bea66ec1efafeeb3929bd5692cbe8b040aff7">

Action Icons Not Working

Just got the new creator in over the holiday break. I went to start working this morning, and Input prompted me for an update, so I went ahead and installed the update. Now neither of my WorkLouder products are connecting via cable to Input. It’s frustrating because I am trying to program them.