error on generating image

I am also experiencing the exact same issue and error. Text and chat functions work, but I am completely unable to generate any images. Did you ever find a solution to this?

I confirmed that Fireworks AI is receiving and attempting to fulfill the requests I submit from the AI explorer. My failed requests are being applied against the billing. However the AI logs indicate that no response is received from Fireworks AI. I hope this helps. These AI modues are really amazing and the hard work is much appreciated.

I am really looking forward to getting this working because the OpenAI image generation cost adds up quicker than I would like but its the only image model I can get working right now.

I logged a different error while trying to create an image with Fireworks AI using an automator upon node creation:
------------------------
The website encountered an unexpected error. Try again later.

Error: Call to undefined method GuzzleHttp\Psr7\Stream::getAsBinary() in Drupal\ai_automators\PluginBaseClasses\TextToMediaImage->generate() (line 170 of modules/contrib/ai/modules/ai_automators/src/PluginBaseClasses/TextToMediaImage.php).

The module was not updated in a long time, it didn't have normalized output. This is now fixed and can be tested on dev - I'm setting it to Needs Review until anyone tests it but me.

I'm going to add tools/function calling before another release. Thanks for reporting and investigating.

Thanks for your help in the repair and hard work on the module!

I installed the dev module and have been using it successfully for the last day in the AI explorer as well as the automator. Images are generated successfully now, thanks!

One issue I discovered while doing this is that some images are provided more than once as the result in the AI explorer. I have not had this happen in the automator yet. Should I create a separate issue for that and close this one?

I confirmed that there are sometimes issues with Fireworks AI communication and I have a few details that may help.

When creating images with Fireworks AI images are sometimes duplicated. I have tried running the cron and clearing the cache multple times with no alteration in the behavior. There are no messages in the logs related to this.

- When using the automator, if an image had already been generated for the content then removed, the replaced image is actually the first image. This seems to be cached, as I can sometimes change the image later and it creates a new image successfully. I think it is getting the new image back from FireworksAI, but it may be having an issue saving the new image. This is only tied to the node that is created. If i create a new node, I get a new image successfully every time.

- When using the AI explorer, each model within the Fireworks AI connection will create a new image, but behaves the same way as the automator. Whenever I try to create the second image with the same model, its a duplicate of the first. I can switch models and get an original the first time, but then a duplicate afterwards. After a while it allows me new images.

I have been looking into this much further, and I am no longer convinced that its a module error.

It appears that if I submit similar prompts to a stable diffusion model within a few minutes of each other, it will return nearly identical images with slight variations.

I have been able to verify this by
1. Submit a prompt to generate a specific person. Ex:Create an image of XX person in a suit and tie.
2. Image returns successfully
3. Submit the same prompt again, hoping for a different output
4. Image is returned that appears to be identical to the first
5. Submit an identical prompt, but change the name of the person only. em>Ex:Create an image of ZZ person in a suit and tie.
6. Almost the exact same image is returned down to specific details, but the face is replaced with ZZ's face.

So, from what I can tell this is an issue with the prompt or model rather than the API connection.

I have been using this heavily for the last few days and have found no other issues to report.

Should we close this then?

I believe this can be closed. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.