Hi @ts11
It looks like you have that action running before the plugin has fully started up, as I can see the error appearing before it reports those other console logs that start with [aibot]…
Where do you have it in your workflows? Maybe you could try moving it into the “ai_bot_ready” event? Let me know what happens when you try that.
I’ve just added a conditional check before the state attempts to populate which will be in the next update soon.
That did the trick! Thank you. Still having to stay on 1.35.0 to avoid the other error, related to “total_tokens,” however. Unrelated, but the bot doesn’t seem to be able to speak when I access via Brave browser on the latest iphone model. It listens, but when it speaks, there is no audio. Do you know why that might be?
I’ll take a look, it’s not a browser I’ve tested against (or heard of) but I’ll install it and see what’s going on. I’m just working on fixing a few cross browser issues with Pinecone right now, and the total tokens error I’ve fixed already. Should be ready tomorrow.
Brave is essentially Chromium, but with a privacy focus.
Can you try the update I’ve just pushed (v1.43.0). It has some changes around the Pinecone/RAG integration so it works with all browsers now and the total_tokens error should now be resolved. I tried the Brave browser and the first time it opened up and I started a call, the audio playback didn’t seem to trigger at all but I restarted and tested again on both desktop and iPhone then it seemed to work. It feels like there could be an underlining issue still so I’ll keep working on it but if you can try everything again then just keep me updated. Feel free to PM me on this. Anything I find, I’ll try and let you know.
with mine, i clear cache on new plugin updates for my website. Works fine then.
