Update to 2.7.0 makes the deck go black
I updated the app to 2.7.0 (deb), all went well. After reboot, all icons on the StreamDeck-console are gone (all are black). OpenDeck shows its connected to the Deck. Within the app (2.7.0) all seems okay. Running Ubuntu 25.10 KDE Plasma 6 Wayland. Find attached opendeck.log (fresh log, after deleted the previous one). tokio-runtime-error? (edited)Sunday 9 November 2025 at 11:57
31 Replies
so you updated from 2.6.1, and restarting the PC didn't fix it
could you please try using another profile in OpenDeck?
Correct. I updated to 2.7.0. Deck and app shows correct info. Interaction worked, also websocket to OBS. Only after reboot, issue started. Created a new profile, added something on an empty slot. Shows in opendeck app, deck remains fully black.
ok, please try backing up your
profiles folder in the OpenDeck config dir, then deleting it and restarting ODho, wait! it does show on deck! sorry, was too quick. So new profile does it okay
oh, nice!
that means it's a problem with the first profile you tried
yup
could you send over the file for that profile?
what file is itr and location of it?
I might have to leave for about an hour now, sorry, but I can look at the file when I get back and see if we can restore the profile
no problem!
should be <profile name>.json inside the
profiles folder in the OpenDeck config dirah found it. hang on
GTG, please try to change
"current_state": 1, lines to "current_state": 0,
make the changes when OpenDeck is closed and then open it again after making the changes
that should hopefully fix it I thinkFirst start after setting 1 -> 0 it worked. But, after quitting opendeck and manually restart it, same issue again. current_state back to 1
So, we found the cause.
see you later
no rush
current_state=1 only in multi_obs I see. Added a button of multi_obs in my new profile. Quit opendeck -> restart. No issue with this new profile, all is good. Current_state set to 1.
maybe just delete the action that has current_state: 1
by replacing the whole block with
nullI am streaming with an hour. Creating a new profile is minutes work for me (dont have much). I will keep the defunct profile. Take your time, I have a quick workaround with a new profile
Replacing all current_state: 1 with new in my default profile (I have a copy made of it 😉 ). And after that, streaming time.
Replacing all current_state=1 with null makes all the buttons go away in opendeck and creates a 100% empty profile with the same name. Good I have a backup of that profile 😉
GTG, having lunch, and then streaming. I have a workround.
Removed plugin multi_obs, and removed all references (whole block) of multi_obs from my (Default) profile. v2.7.0 when default profile is running fine now.
yeah I meant replace the entire
{} of the action inside the keys array, not just current_state
slightly weird bug, it means the plugin is sending setState event with value of 1 even when it only has a 0th state...
I can add a sanity check in the setState handler to ignore setState events where the index is too high so that this hopefully doesnt happen in the future
sorry you keep having so many weird issues... :(
have a good streamNah, dont feel sorry! For me, getting things done on Linux (and enjoy all the benefits of it) is part of the journey. If I want to play safe&quick, I'd run on Windows 😂 (although...). And about the keys-array... Yeah, when asking in human language to do something in source code: a lot of misinterpretations can take place. That's my experience at least, when building code and doing some reviews. Get rid of the human interface, that always improves quality.
Right, now about 2.7.0 and multi-obs. If I understand correctly, that plugin is doing something wierd, and OpenDeck does not know hoe to handle that. Right? If that's the case, yeah, a try/catch/exception will be good to have. To make OpenDeck fail-safe against wierd actions of 3rd party plugins.
Or did I misunderstood?
well, I havent investigated thoroughly, but it looks like that's the case, yeah
although Multi OBS is a popular plugin and I havent seen this before so maybe just something wrong with that 1 action
Yeah, could be. But I am running multi-obs since 2.5.0 (2.6.0 -> 2.6.1), and didnt had problems with it, until 2.7.0. My workaround today was using obs-cmd, I got those scripts ready for just in case.
I just got out of the stream, wanted to let you know I've read your message.
Just wanted to add: I am almost always on the latest git commit, and last Saturday I had no problems with Multi-OBS while I was Streaming.
yeah no commits were made between 2.6.1 and 2.7.0 touching this so not an update issue
Right. Lemme know to check/verify something on my OS. Willing to help.
pushed a small fix
https://github.com/nekename/OpenDeck/commit/1932a26af70eeef93879ecb49fb95037afe67a04
if that was actually the issue, this wont fix anything if that wasnt the issue, but its always nice to have sanity checks in code so not doing any harm at least
Ok. Lets find out how I am doing on building opendeck. Maybe tonight.
what OS you said you are on?
Ubuntu 25.10
Just checking, you're also on the latest git commit of multi-obs? It changed from 0.8.0 to 0.8.1 two weeks ago.
I am on 0.8.0 right now.
Ahh.... Well, I suppose I am going back to 0.8.0 now on opendeck 2.7.0 and see how THAT goes. That makes things clear to pinpoint stuff eh
its atleast one difference. (Apart from I am on Arch and you are on Ubuntu.)