@tazman ,

eisy-ai does not know anything about network resources neither for programs nor for plugin-dev. And that's on purpose.

Regarding session management, that's something we need to finetune. For now, you can change history_token_budget to 500000 in the configuration json.

Awesome regarding the occupancy plugin!

With kind regards,
Michel

I'm just getting back into this, and created a second plugin, of a totally different nature. No hardware or network access, strictly making date related calculations, like if we're in an odd or even week of the year, if we're in the last full Monday to Friday week of the month, etc. Cities have been getting creative on setting up services like garbage collection (pardon the trash talk...) and getting advance notifications for these can be useful. In my city garbage collection is every week, but alternating between recyclables and regular garbage. Compostables is every week, except for winter (December to March) where it's every two weeks. Then there is large item pickup once a month, on your regular garbage day that falls in the last full Monday to Friday week of the month. Automate that... Well now I can! 🙂Other handy values are weekday instance of the month (eg: second Wednesday)

I need to get around to setting up github and make this available to others.

Edited 22 hours ago22 hr by Guy Lavoie

I ran into an interesting little issue this morning. In modifying my Calendar plugin, I asked it to remove some text descriptors it was putting in some values, such as "13 days" for the number of days left in the month. I want just the number because I want to be able to do numeric comparisons, like > , etc. It was trying to change the UOM to 56 (raw) to do that and at one point asked me to delete the existing nodes in PG3x. It seems to be thinking that PG3x is being used for plugin management, even though this one was created from scratch as an integrated plugin. The other thing is that unlike with PG3x where you can click on the "Nodes" heading of a plugin and manually delete nodes, there is no such thing available in the integrated plugins, that I can see anyway. When it saw that it couldn't work, it took a more roundabout route to getting done, successfully.

@Guy Lavoie ,

Thank you very much for the feedback. Definitely remnants in the codebase. We'll fix it.

With kind regards,
Michel