Maurice Faber
Maurice Faber
+1 Verified thrown by this custom component installed from this repo. ``` Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 162, in _async_subscribe_for_data entry_data.client.nest_session = await entry_data.client.authenticate(auth) File "/config/custom_components/nest_protect/pynest/client.py", line...
@jeanpaul ?? I find react agents to be MORE reliable and I have switched to that from tools agents. I will provide my workflow here in a bit
@jeanpaul I never saw I did not correctly add the test workflow files in my OP, but have added it now.
I would assume that n8n deals with passing on keys that are given undefined values correctly. (It seems messy in the traces, as I see `[undefined]` as well as `[null]`...
@jeanpaul I tested it again and this bug still holds. Your assumption that an `undefined` or `null` value being passed to another workflow via "Extra Workflow Inputs" will be cast...
None of the information about Zep in your docs is correct. (They do not even have a vector store!)
Why would you want to maintain OSX builds if you don't want to support the rest of the usual suspects? Just to allow devs to test it on their Mac?
I think it would be rather trivial to set up and see how it behaves...if one runs into issues draw conclusions then?
All I am saying is that HomeAssistant is one very big project with hundreds of thousands of users and they switched to page size 16 long time ago for this...
I can build it to see if it passes the smoke test if that is helpful