The documentation and scripts are committed to the new GITHUB repository: https://github.com/jvanderzande/GarbageCalendar
I am have been reworking the set of scripts currently supported on GITHUB (https://github.com/jvanderzande/mijnafvalwijzer), to make the whole setup modular. The issue that I have is that the script aren't all working in the same way, making it very cumbersome to add/update logic as that would require to visit all the scripts. Also adding new garbage websites was more difficult in the old setup.
The new setup consist of these modules:
- A single main script with all standard logic for updating Domoticz and sending the notifications, which will be scheduled by the Domoticz event system as Time script running each minute.
- A personal configuration file avoiding having to copy your settings each time you update the script.
- A separate script module for each garbage website. You config the module to use in your config file. This module script will be ran by the main script in the background (separate process) ones per day, avoiding to potentially slowdown the event system.
- Possibility to configure all text so it can be setup for other language than the standard supplied Dutch & English examples.
- Possibility to create an ICS calendar file to use in a calendar application.
Here you can find the currently available modules:
https://github.com/jvanderzande/Garbage ... le_modules
In case there are issues, check here for things to check.
When you like my assistance with debugging your issue, just provide me with a copy of the following files in a zip file to my Github email, so I can see what is happening:
- all 5 garbagecalendar*.log files:
- garbagecalendar_*modulename*_run.log => log of the last time the script was ran
- garbagecalendar_*modulename*_run_update.log => log of the last time the script ran the update process in foreground
- garbagecalendar_*modulename*_run_webupdate_background.log => log of the background webupdate process.
- garbagecalendar_*modulename*_run_webupdate.log => log of foreground process that shelled the background webupdate process.)
- garbagecalendar_*modulename*.data => the file containing the result of the webupdate process by the module.
- garbagecalendarconfig.lua
Ensure you have these variables set in your garbagecalendarconfig.lua as follows, so there will be extra debugging
information in the logfiles:
Code: Select all
-- Switch on mydebug in case of issues and initially and check the domoticz log for any issues or missing
mydebug = true -- (true/false)
testdataload = true -- (true/false)
Jos