Andreas Hochsteger

Here are the snapshots I took when using the Gecko in.touch app and HA. They numbers after light-app or light-ha indicate the sequence I pressed the respective action that follows...

@gazoodle thanks a lot for your work! I tried the latest releases but it seems to still not work for me. This time the device becomes unavailable after changing the...

I'm interested in using `jv` as nix package as well. @nwchandler did you find some time to work on it?

@MihaiSprinceana that's an interesting use case which should be possible with the next feature release. I'm currently working on introducing custom actions, which will allow to trigger any automation one...

@MihaiSprinceana I've just released version 2.11.0 which adds support for custom actions. Have a look at [this example](https://ahochsteger.github.io/gmail-processor/docs/examples/advanced/customActions) to see how it can be used. It would be great to...

@MikeDabrowski you can have a look at the types `AttachmentInfo` and `AttachmentContext` in [Context.ts](https://github.com/ahochsteger/gmail-processor/blob/main/src/lib/Context.ts) that define the context for attachment processing. Use `ctx.attachment.object` to get the currently processed attachment that...

@MikeDabrowski you may use `ctx.proc.gdriveAdapter` to get access to [GDriveAdapter](https://github.com/ahochsteger/gmail-processor/blob/main/src/lib/adapter/GDriveAdapter.ts) which provides the function `createFile(location, fileData, conflictStrategy)`. Have a look at the source code of the linked file for the...

@MikeDabrowski nice to see that you're making progress :-). Concerning async in custom actions: Unfortunately Google Apps Script is fully synchronous and does not support asynchronous processing, that's why custom...

@MikeDabrowski thanks for the PR - so far it looks good to me for the start. I'll add some comments to the code to let you know how I usually...

@MikeDabrowski I was able to do update this PR and it is now in a functional state using an async custom action. Moving the async support into the library did...