So while attempting to replace my macros for “Jarvis” via Alexa Media Player with the OpenAI GPT integration, I stumbled across this problem. I’m not entirely sure it’s a bug as it seems the reload service does what it’s intended to do, but that’s what makes me request and alternate function to go along with it.
Let me explain,
In my testing, in order to obtain a brand new response from GPT3, the input_text field that is used to send the prompt must be set to blank, then re enter the prompt you want to send. Unfortunately, leaving the input_text filled, just results in the same response over and over without updating the sensors. This is where my problem lies.
I had the default or initial value of my input_text set to “” in the config. I was hoping that calling the input_text.reload service would then reset the field to “” or blank, getting it ready for the next prompt to be entered. This is not what happens. Apparently the reload service doesn’t work like that and the value set in the config is only use after a reset.
To solve this (if reload is doing exactly as the devs intended) I request a Refresh service that can do what is needed here. Reload can keep it’s function and Refresh can set the sensor to whatever ‘default’ state it’s given. For my use case, I could use my script that would call input_text.refresh to clear the field…then send a prompt, obtain the response, send it to Alexa Media Player and then once again call the refresh service to set the input_text back to it’s default state.
As is stands, attempting to call the set_value service, set it to “” then send a prompt, then call set value back to “” is just not working as expected and results in problematic results.