I'm tearing my hair out on this. The Stream Deck is receiving information from the Web API but not writing anything back. When I look at the "Change Web API address" modal in AAO, the "StreamDeck Plugin" is unchecked. I'm assuming that is why it can't write back.

If I quit Stream Deck, I can check the box for this plugin. Apply, and restart AAO. The plugin remains checked.

As soon as I start Stream Deck however, the plugin immediately gets unchecked again.

5 hours ago, Agathorn said:

I'm assuming that is why it can't write back.

That assumption is wrong. The checkmark does not indicate that something is "active". It is just local to this dialog, the checkboxes are there for selecting the addons that you want to change the web address/port for with the buttons below the list. It is disabled when you run the StreamDeck software, because in this state, AAO cannot change the Web Address in the plugin's config file (=the buttons wouldn't do anything)

The Stream Deck is receiving information from the Web API but not writing anything back

Please explain a bit more what you mean by that. What does "writing back" mean, what do you expect to happen when you do what exactly? When the WebAPI works one way, it works the other way too - this is one single mechanism.

Edited June 5Jun 5 by Lorby_SI

8 hours ago, Lorby_SI said:

That assumption is wrong. The checkmark does not indicate that something is "active". It is just local to this dialog, the checkboxes are there for selecting the addons that you want to change the web address/port for with the buttons below the list. It is disabled when you run the StreamDeck software, because in this state, AAO cannot change the Web Address in the plugin's config file (=the buttons wouldn't do anything)

Please explain a bit more what you mean by that. What does "writing back" mean, what do you expect to happen when you do what exactly? When the WebAPI works one way, it works the other way too - this is one single mechanism.

Ahh there goes a logical fallacy :)

What I mean is the buttons on the stream deck are all getting live information from the sim, but none of the buttons do anything in the sim. I've tried multiple profiles, and even my own, and they all properly show live data being red from the sim such as heading or altitude, but none of the event being sent back to the sim do anything.

2 hours ago, Agathorn said:

What I mean is the buttons on the stream deck are all getting live information from the sim, but none of the buttons do anything in the sim. I've tried multiple profiles, and even my own, and they all properly show live data being red from the sim such as heading or altitude, but none of the event being sent back to the sim do anything.

Sounds strange, never heard of that before, sorry. The only situation where this does happen is when the profiles call scripts and the user forgot to import the script package(s) into AAO...

There used to be a button we could add that tested the connection to the sim but that seems to have been removed?

I've even tried creating very simple buttons that don't call a script, using a simple event name.

I will also add in this case I DID import the script but more than that, I tried looking at all of the various data/script monitors in AAO and none of them show any activity from the SD. Should they?

19 minutes ago, Agathorn said:

I will also add in this case I DID import the script but more than that, I tried looking at all of the various data/script monitors in AAO and none of them show any activity from the SD. Should they?

Maybe your firewall is intefering? Letting the data pass one way only? To be on the safe side, you should create firewall rules that allow all traffice through the TCP port that you have configured for the WebAPI - in both directions, incoming and outgoing. Creating a rule for the AAO app itself is the wrong way to go, that won't work.

Sorry, my bad, but this was B.S.

When you are seeing data on the StreamDeck, then the WebAPI and the connection are both fully functional. The SD plugin is sending requests to AAO and gets the data in the response. So the API is working both ways.

You are certain that the buttons on your SD are working? No others plugins that could interfere? The easiest way to check would be using an empty profile and creating a single AAO "Button" Action on it. This should be picked up in AAO when you open the "Add Button" dialog (same as with a joystick or button box, but it would show "WebAPI" as the source).

Edited June 5Jun 5 by Lorby_SI

I do have both inbound and outbound rules on the primary and secondary ports.

Furthermore I can manually go to http://localhost:43381/webapi?conn=1 and see an OK message.

wow the forum just completely ate my response it seems and somehow posted an old response that must have been cached. Very strange.

Let me try again

First, apologies for the late reply. I got lost in work.

Ok, so first thing I tried was your button test and that worked. AAO so the button as coming from the WebAPI.

Next, I bound that button to an event in the sim inside AAO and pressing the button on the SD had the expected result (parking brake).

I then tried to make a SD button with the "Event" type that would directly do the parking break instead of it showing up as a button in AAO then AAO doing the parking brake, but this did nothing, I then tried a different event, K:MASTER_BATTERY_ON and this also did nothing.

To make sure I had them correct, I tried both parking brake and battery in AAO with the spacebar and they functioned as expected so the events were correct, they just wont' function from SD. The only thing that seems to work on SD is the basic "Button" which just acts as a button press on a peripheral which is not what I want. I want to use the more advanced features of the SD integration to read and write data directly through the WebAPI

16 minutes ago, Agathorn said:

I then tried to make a SD button with the "Event" type that would directly do the parking break instead of it showing up as a button in AAO then AAO doing the parking brake, but this did nothing, I then tried a different event, K:MASTER_BATTERY_ON and this also did nothing.

You must be doing something wrong. Please post a screenshot of this assignment, what it looks like in your StreamDeck app.

Edited Friday at 06:17 PM4 days by Lorby_SI

1 hour ago, Lorby_SI said:

You must be doing something wrong.

No doubt. I'm 100% certain I'm doing something wrong, and I? thank you very much for your patience because I feel like I'm closer to getting it figure out than when I started :)

Hmm can't seem to upload an image. If I drag it into the post it shows a red line but then does nothing when I let go, and I don't see an attach image option.

I'll keep digging on this and see if I can figure out what I'm missing.

Did you read the PDF that comes with the plugin? There are screenshots in it that show what the actions should look like.

Most common mistakes are:

1. With the ready made profiles, many people overlook that you usually have to import one or more script packages into AAO that come bundled with the download.

2. Not supplying an "Event value". With every event box (Key Down, Key Up, etc.) there is a numerical input called "Event value". This cannot be left empty, you must enter a value. For simple events, 0 or 1 will do.

3. Entering the event incorrectly. "(K:PARKING_BRAKES)" gets entered by selecting "K:" from the drop down, then entering "PARKING_BRAKES" into the textbox to the right

4. Copy/pasting code from the AAO script editor into the Elgato software. In general, you cannot copy script directly from the white editor box - you have to C&P it from the grey box below it, that contains the compiled code.

5. Forgetting to press the "Submit" button at the bottom of the action dialog in the Elgato software

6. Running an outdated version of the AAO plugin

7. Expecting all events to work for all aircraft - that is not the case. In you test scenario, make sure that when something works while assigned to a button, keep the same aircraft/livery when you test it with the StreamDeck.

On a side note, when posting questions here, please make sure to always include the simulator and aircraft that you are trying to control. Especially in the MSFS world they are all different. Some react to the SDK events, others don't. And all of them have custom logic of some kind that must be assessed from scratch for each aircraft.

Edited Friday at 09:23 PM4 days by Lorby_SI