function tool async def wait for actual bill self record id LiveKit Community #ask-ai

@function_tool() async def wait_for_actual_bill(se...

numerous-shampoo-46454

09/13/2025, 9:58 AM

@function_tool() async def wait_for_actual_bill(self, record_id: str) -> str: """ Wait until the actual bill amount is added in MongoDB, then return it. During waiting, disable user audio. Re-enable when bill is found. """ job_ctx = get_job_context() local_participant = job_ctx.room.local_participant # Disable audio input/output while waiting local_participant.set_microphone_enabled(False) try: while True: try: record = await self._get_record(record_id) if record and record.get("actual_bill") is not None: bill = record["actual_bill"] # Re-enable mic before returning local_participant.set_microphone_enabled(True) return str(bill) except Exception as e: logger.error(f"Error checking actual bill: {e}") local_participant.set_microphone_enabled(True) return "Error while checking bill" await asyncio.sleep(5) finally: # Ensure mic is re-enabled in any exit case local_participant.set_microphone_enabled(True) Check this code for errors

tall-airline-16756

09/13/2025, 9:58 AM

Thanks for reaching out, Mubbashir. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

tall-airline-16756

09/13/2025, 9:59 AM

Let's work together to debug your Python code for managing audio states and MongoDB integration with LiveKit. Here are some helpful steps you can try: • Enable Detailed Logging: Turning on debug-level logging can really help you keep an eye on audio processing and device states. For instance, in LiveKit's Python SDK, you can activate detailed logs using a debug flag. • Monitor Audio Processing: Adding debug counters to track audio data flow—like callback frequency and frame processing—can give you valuable insights. Logging these stats periodically might reveal where things slow down. • Visual Debugging: Using a terminal UI to show microphone levels, mute status, and connection stats can be a great way to spot issues such as low volume or connectivity hiccups. • Handle Audio Device Issues: Running a device listing script helps confirm that the right audio devices are in use, which can prevent unexpected problems. • MongoDB Integration: Since the LiveKit SDK doesn’t natively support MongoDB, you’ll want to use an async Python MongoDB driver like

motor

to handle database operations smoothly without blocking your event loop. For your specific code, it’s important to make sure that: • Audio states are toggled correctly using LiveKit's SDK methods. • Database operations are awaited properly to keep everything running smoothly. • Error handling is in place to ensure the microphone gets re-enabled no matter what. If you’d like, I’m here to help with any particular parts of your code—just let me know! Sources: README.md

numerous-shampoo-46454

09/13/2025, 10:05 AM

File "C:\Users\HP\AppData\Local\Programs\Python\Python311\Lib\site-packages\livekit\agents\voice\generation.py", line 517, in _traceable_fnc_tool val = await function_callable() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\HP\AiCallAgentBackend\classes\helpful_assistant.py", line 171, in wait_for_actual_bill local_participant.set_microphone_enabled(False) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\HP\AppData\Local\Programs\Python\Python311\Lib\unittest\mock.py", line 653, in getattr raise AttributeError("Mock object has no attribute %r" % name) AttributeError: Mock object has no attribute 'set_microphone_enabled'

numerous-shampoo-46454

09/13/2025, 10:05 AM

???

tall-airline-16756

09/13/2025, 10:05 AM

It looks like you're running into the error

AttributeError: Mock object has no attribute 'set_microphone_enabled'

because the mock object in your test doesn’t have the

set_microphone_enabled

method set up correctly. No worries, I’m here to help you through this! Here are some friendly tips to fix it: • Try the
mock_tools
Helper: The LiveKit SDK offers a handy

mock_tools

utility that helps mock specific tools or components properly. This way, your mock will include all the attributes and methods it needs. • Use `create_autospec`: When you’re mocking objects like

local_participant

, it’s a great idea to use Python’s

unittest.mock.create_autospec

. This creates a mock that really matches the original object’s interface. For example:

Copy code

from unittest.mock import create_autospec
mock_participant = create_autospec(OriginalParticipantClass)
mock_participant.set_microphone_enabled = MagicMock()

• Double-check Your Mock Setup: Make sure all the methods and attributes your code uses are explicitly defined on your mock object. This helps avoid surprises! I hope these suggestions make things clearer and get you back on track. If you have any more questions or want me to walk you through any of these steps, just let me know—I’m happy to help! Sources: Docs::Agents | livekit-agents/livekit/agents/ipc/mock_room.py

tall-airline-16756

09/13/2025, 10:05 AM

It looks like you're running into the error

AttributeError: Mock object has no attribute 'set_microphone_enabled'

. This usually happens because the mock object in your test doesn’t have the

set_microphone_enabled

method defined yet. It’s a pretty common hiccup when working with mocks during testing. Here’s a friendly way to fix it: • Try using Python's

unittest.mock.create_autospec

to create a mock that closely resembles your original object. For example:

Copy code

from unittest.mock import create_autospec

# Assuming local_participant is an instance of a specific class
mock_local_participant = create_autospec(OriginalClass)
mock_local_participant.set_microphone_enabled.return_value = None

• Make sure your mock includes all the methods and attributes your code expects to call. • If you’re working with LiveKit’s SDK, it might help to use their

mock_tools

or similar utilities, which can make your mocks behave just like the real SDK objects. Feel free to reach out if you want me to walk you through this or if you have any other questions—I’m here to help!

Open in Slack

Previous Next