Sharing : Afval kalendar in text sensor

[jvdz]

Did you check if there is a rights issue?
What is the result of this command performs from the console?: ls -l /opt/domoticz/scripts/lua/garbagecalendar

[RonkA]

Man...
The rabbithole again went way deeper for me.. But i digress;
I did the 'ls' command in dockerterminal and it states: no files in directory.

So the 'garbage collect' files and dir ARE in the correct location in the docker folder on my nas, but thats not enough to get the files to be useful in docker.

Looking around in docker terminal using 'cd' and 'ls' command i compared some other folders to the 'same' folders on the nas and they have diferent files!!
I am a old 'DOS' user, so Linux is new to me, i'm trying but I did not see that comming, this might be the reason i cannot get other things (like dzVents scripts) to run like they should because i've assumed the folders matched inside and outside docker..

To try something so i coupled the dir adding the volume path:

synology.jpg (34.02 KiB) Viewed 1729 times

Now i run ls -l /opt/domoticz/scripts/lua/garbagecalendar and it got the files shown correct.. Hurray!

But now i'm here..

Spoiler: show

MainScript: ### Start garbagecalendar script v20220503-1709 Wed Jul 27 11:24:00 2022
MainScript: ---> Debuging with extra messages because "mydebug=true" in garbagecalendarconfig.lua
MainScript: ---> please change it back to "mydebug=false" when done testing to avoid growing a big domoticz log.
MainScript: domoticzjsonpath: /opt/domoticz/scripts/lua/
MainScript: datafilepath: /opt/domoticz/
MainScript: scriptpath: /opt/domoticz/scripts/lua/
MainScript: Loaded /opt/domoticz/scripts/lua/garbagecalendar/garbagecalendarconfig.lua.
MainScript: Loaded /opt/domoticz/scripts/lua/garbagecalendar/generalfuncs.lua (v20220503-1709)
MainScript: => Start checking garbagetype_cfg table whether an action is needed:
MainScript: > NotificationTime=02:30 Garbagetype=reloaddata
MainScript: > NotificationTime=02:31 Garbagetype=dummy1
MainScript: > NotificationTime=19:22 Garbagetype=pmd
MainScript: > NotificationTime=19:22 Garbagetype=gft
MainScript: > NotificationTime=19:22 Garbagetype=papier
MainScript: #> Perform update because mydebug=true.
MainScript: => Action starting, First check access to required files:
MainScript: Run command:
ls -l /opt/domoticz/garbagecal*m_omrin*:
Status: LUA: -rw-r--r-- 1 root root 1351 Jul 27 11:24 /opt/domoticz/garbagecalendar_run_m_omrin.log
-rw-r--r-- 1 root root 560 Jul 27 02:31 /opt/domoticz/garbagecalendar_web_m_omrin.log
Status: LUA: 11:24:00 MainScript: File doesn't exists: /opt/domoticz/garbagecalendar_m_omrin.data
Status: LUA: 11:24:00 MainScript: Access OK: /opt/domoticz/garbagecalendar_run_m_omrin.log
Status: LUA: 11:24:00 MainScript: Access OK: /opt/domoticz/garbagecalendar_web_m_omrin.log
Status: LUA: 11:24:00 MainScript: => Start update for text device:
Status: LUA: !!! table.load error:cannot open /opt/domoticz/garbagecalendar_m_omrin.data: No such file or directory
Status: LUA: !!! unable to read Data from /opt/domoticz/garbagecalendar_m_omrin.data
Status: LUA: 11:24:00 MainScript: ### Warning: Datafile not found:/opt/domoticz/garbagecalendar_m_omrin.data . Start webupdate now.
Status: LUA: 11:24:00 MainScript: => Start new foreground WebUpdate for module m_omrin
Status: LUA: 11:24:00 _runmodule: > Input arg table:
Status: LUA: 11:24:00 _runmodule: Foreground scriptpath /opt/domoticz/scripts/lua/
Status: LUA: 11:24:00 _runmodule: --> Start -- foreground _runmodule.lua (v20220503-1709) for garbage module m_omrin file:/opt/domoticz/scripts/lua/garbagecalendar/m_omrin.lua

garbagecalendar_m_omrin.data is not beeing created and if i don't set debug to false domotics crashes every minute..

Now knowing, looking at files in a docker container is not as straigtforward as looking at files on a nas with a file explorer, it's a steep learingcurve for me.. but everyday you learn...

[jvdz]

Code: Select all

Status: LUA: 11:24:00 MainScript: ### Warning: Datafile not found:/opt/domoticz/garbagecalendar_m_omrin.data . Start webupdate now.
Status: LUA: 11:24:00 MainScript: => Start new foreground WebUpdate for module m_omrin
Status: LUA: 11:24:00 _runmodule: > Input arg table:
Status: LUA: 11:24:00 _runmodule: Foreground scriptpath /opt/domoticz/scripts/lua/
Status: LUA: 11:24:00 _runmodule: --> Start -- foreground _runmodule.lua (v20220503-1709) for garbage module m_omrin file:/opt/domoticz/scripts/lua/garbagecalendar/m_omrin.lua

garbagecalendar_m_omrin.data is not beeing created and if i don't set debug to false domotics crashes every minute..

This part look ok for a first run and the WebUpdate script is ran as there is no data yet. I would need to see all the logs to check what is happening. Lets take this offline and please Email all the generated log files in a zip file so I can have a look, but the WEB log should contain the information about the Data retrieval process as described in the Wiki: https://github.com/jvanderzande/Garbage ... ki/Testing

Jos

[smaus]

has anyone gotten the garbage calendar running on a synology with docker.

unfortunately I can't

[jvdz]

The thread for the GarbageCalendar is this one: viewtopic.php?f=61&t=31295
what seems to be the problem?
can you share your logs with me?

[smaus]

here is the log


2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: ### Start garbagecalendar script v20220503-1709 Fri Dec 16 20:14:00 2022
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: ---> Debuging dataload each cycle in the foreground because "testdataload=true" in garbagecalendarconfig.lua
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: ---> please change it back to "testdataload=false" when done testing to avoid growing a big domoticz log and slowing down the event system.
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: ---> Debuging with extra messages because "mydebug=true" in garbagecalendarconfig.lua
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: ---> please change it back to "mydebug=false" when done testing to avoid growing a big domoticz log.
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: domoticzjsonpath: /volume1/docker/domoticz1/scripts/lua/
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: datafilepath: /var/tmp/
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: scriptpath: /volume1/docker/domoticz1/scripts/lua/
2022-12-16 20:14:00.215 Status: LUA: 20:14:00 MainScript: Loaded /volume1/docker/domoticz1/scripts/lua/garbagecalendar/garbagecalendarconfig.lua.
2022-12-16 20:14:00.216 Status: LUA: 20:14:00 MainScript: Loaded /volume1/docker/domoticz1/scripts/lua/garbagecalendar/generalfuncs.lua (v20220503-1709)


[2022-12-16 20:14:00.216 Error: LUA: 20:14:00 MainScript: ### Error: module not found: /volume1/docker/domoticz1/scripts/lua/garbagecalendar/m_opzet_api.lua
2022-12-16 20:14:00.216 Error: LUA: 20:14:00 MainScript: ### Error: Please check the path&name in variables "scriptpath=" "websitemodule= " in your "garbagecalenderconfig.lua" setup and try again.
2022-12-16 20:14:00.216 Error: EventSystem: Lua script /opt/domoticz/userdata/scripts/lua/script_time_garbagecalendar.lua did not return a commandArray[/color]

[jvdz]

Did you also copy the garbagecalendar subdirectory with all its modules to: /volume1/docker/domoticz1/scripts/lua/garbagecalendar/* ?
I see the config and general functions files are found:
/volume1/docker/domoticz1/scripts/lua/garbagecalendar/garbagecalendarconfig.lua
/volume1/docker/domoticz1/scripts/lua/garbagecalendar/generalfuncs.lua

but the module isn't found:
/volume1/docker/domoticz1/scripts/lua/garbagecalendar/m_opzet_api.lua

What do you have defined in garbagecalenderconfig.lua?

[smaus]

yes i put it here

[jvdz]

yes i put it here

Good ....

What do you have defined in garbagecalenderconfig.lua?

... and the answer to my second question is?

[smaus]

sorry forgotten

i switch from domoticz1 to domoticz.

Code: Select all

hostname of your website. eg 'inzamelkalender.hvcgroep.nl'
                      -- *m_ximmio: Specify the companycode. (See m_ximmio.lua on how to find this code).
Street=''             -- Street name Only needed for: m_recycleapp
-- ==============================
-- choose one of these modules ==
-- ==============================
--websitemodule = "m_deafvalapp"
--websitemodule = "m_goeree-overflakkee"
--websitemodule = 'm_mijnafvalwijzer'
--websitemodule = "m_montferland"
--websitemodule = "m_recycleapp-be"
--websitemodule = "m_opzet"
websitemodule = "m_opzet_api"
--websitemodule = "m_omrin"
--websitemodule = "m_rova_api"
--websitemodule = "m_westland"
--websitemodule = "m_ximmio"           --
--websitemodule = "m_zuidlimburg"
-------------------------------------------------------------------------------------------------------
-- When using a CSV input file uncomment the next 2 lines and specify the location and name of the file.
-- check the m_csv_file.lua file for the appropriate format.
--websitemodule = "m_csv_file"
--input_csv_file = "/volume1/docker/data/garbage_input.csv"
--input_csv_file = "/volume1/docker/imput/garbage_input.csv"
-- =====================================================================================================

-- Switch on mydebug in case of issues and initially and check the domoticz log for any issues or missing
mydebug = true -- (true/false) -- run the script as it normally does when any of the scheduled times is the current time
testdataload = true -- (true/false) -- run the web update module with each run for testing/debugging purposes
testnotification = true -- (true/false) -- this will trigger a test notification for the first record for testing the notification system

-- Specify the appropriate directories (Raspberry Pi example)
datafilepath = '/var/tmp' -- specify the directory where the garbagecalendar.data & garbagecalendar.log will be stored
scriptpath = '/Volume1/docker/domoticz/scripts/lua' -- specify the directory for the main "script_time_garbagecalendar.lua" script
domoticzjsonpath = '/Volume1/docker/domoticz/scripts/lua' -- specify the path to domoticz where the JSON.lua file can be found
-- Specify the appropriate directories (Windows example)
--datafilepath     = 'D:/temp'                            -- specify the directory where the garbagecalendar.data & garbagecalendar.log will be stored
--scriptpath       = 'D:/_domoticz/scripts/lua'   -- specify the directory for this script
--domoticzjsonpath = 'D:/_domoticz/scripts/lua'   -- specify the path to domoticz where the JSON.lua file can be found

------------------------------------------------------------------------------------------------------------------------------------
-- ### define format for text device in Domoticz
-- date options:
--    wd   = weekday in 3 characters as defined in the daysoftheweek table below. eg zon;maa;din
--    wdd  = weekday as defined in the Longdaysoftheweek table below. eg zondag;maandag;dinsdag
--    dd   = day in 2 digits   eg 31
--    mm   = month in 2 digits eg 01
--    mmm  = month abbreviation in 3 characters as defined in the ShortMonth table below. eg : jan
--    mmmm = month  as defined in the LongMonth table below. eg: januari
--    yy   = year in 2 digits eg 19
--    yyyy = year in 4 digits eg 2019
-- Garbage type description options
--    sdesc = short garbage type description from Website  eg pmd
--    ldesc = long garbage type description from Website when available, will be replaced by table description when not
--    tdesc = Use the description available in the table text field
textformat = 'tdesc: wd dd mmm'
-- One can also add some html formatting formating to the output when the used interface supports that:eg:
--    textformat = '<font color="red" size=1>tdesc: wd dd mmm</font>'

-- ### define  what to show in the domoticz text device
-- !!! ShowSinglePerType will be forced to false when Combine_Garbage_perDay = true
ShowSinglePerType = false        -- (default) false => show multiple occurrences of a garbagetype (default)
                                    -- true  => show one the next occurrence for a unique garbagetype
ShowNextEvents = 3               -- indicate the next x eventlines to show in the TEXT Sensor in Domoticz
Combine_Garbage_perDay = false   -- (default) false will show each garbagetype on its own line
                                    -- true will show multiple garbagetype on a single line when collected the same day

------------------------------------------------------------------------------------------------------------------------------------
-- Configuration for the Notificaton system:
NotificationEmailAdress = {'[email protected]'} -- Specify multiple Email Addresses for the notifications. Leave empty to skip email notification
Notificationsystem = 'pushbullet' -- Specify notification system eg "telegram/pushover/gcm/http/kodi/lms/nma/prowl/pushalot/pushbullet/pushsafer" leave empty to skip
Notificationscript = '' -- Specify personal notification script/command eg:  lua sendmessage.lua "@TEXT@"  (where @TEXT@ will be replaced by the notification text.)
--                                                                                                                     It also supports: @GARBAGETYPE@; @GARBAGEDATE@; @GARBAGETEXT@
-- Define how the title and bodytext should look
-- @DAY@         ==> Will be replaced by notificationtoday; notificationtomorrow; notificationlonger depending on the days difference.
-- @GARBAGETYPE@ ==> Will be replaced by the GarbageType definition from the WebSite
-- @GARBAGEDATE@ ==> Will be replaced by the pickup date found on the schedule data
-- @GARBAGETEXT@ ==> Will be replaced by the text from garbagetype_cfg[].text field
-- @REMINDER@    ==> Will be set to "" for first notification and "notificationreminder" for the reminder run
-- @TEXT@        ==> Will be replaced by the finalised notificationtext and can be used in the notification script
--### Dutch example
notificationreminder = 'herinnering'
notificationtitle    = 'GarbageCalendar: @DAY@ de @GARBAGETEXT@ aan de weg zetten!'
notificationtext     = '@GARBAGETEXT@ wordt @DAY@ opgehaald! (@REMINDER@)'
notificationtoday    = 'vandaag'
notificationtomorrow = 'morgen'
notificationlonger   = 'over @DAYS@ dagen'
notificationdate     = 'wd dd mmmm yyyy' -- @GARBAGEDATE@ format -> Options are the same as available for textformat date options

--### English example
--~ notificationtitle    = 'GarbageCalendar: @GARBAGETEXT@ will be picked up in @DAY@!'
--~ notificationtext     = 'Put the @GARBAGETEXT@ out as it will be picked up @DAY@.!'
--~ notificationtoday    = 'today'
--~ notificationtomorrow = 'tomorrow'
--~ notificationlonger   = 'in @DAYS@ days'
--~ notificationdate     = 'wd dd mmmm yyyy'      -- Options are the same as available for textformat date options
------------------------------------------------------------------------------------------------------------------------------------
-- Configuration for the generation of an ics file:
-- IcalDesc:
--   @GARBAGETYPE@ ==> Will be replaced by the GarbageType definion from the WebSite
--   @GARBAGETEXT@ ==> Will be replaced by the text from garbagetype_cfg[].text field
IcalEnable = false -- false/true: When true, a garbagecalendar_Modulename.ics will be created in the datafilepath which can be used in a calendar application.
IcalTitle = 'GarbageCalendar' -- title of the calendar
IcalDesc = '@GARBAGETEXT@ wordt opgehaald.' -- text for the events in the calendar
IcalEvents = 10 -- max number of upcomming events to save to icalfile, but could be less when less events are provided by the website.
IcalNotify = 12 -- Notification Time in hours before event. 0=no notification
------------------------------------------------------------------------------------------------------------------------------------
-- ### define a line for each garbage type returned by the webrequest.
-- Look at the Domoticz log for any missing records as they will be displayed there and can be just copy/pasted in.
-- Fields description:
-- hour & min ==> the time the check needs to be performed and notification send when daysbefore is true
-- daysbefore ==> 0 means that the notification is send on the day of the planned garbage collection
-- daysbefore ==> X means that the notification is send X day(s) before the day of the planned garbage collection
-- reminder   ==> Will send a second reminder after x hours. 0=no reminder (can be between 0 - 24 hours)
-- text       ==> define the text for the notification and Text Device.
-- active     ==> (optional)  default="on"
--           active="on"   Both will show in Domoticz Text Device and Send notifications
--           active="off"  Will show in Domoticz Text Device but not send notifications
--           active="skip" Will not show in Domoticz Text Device and not send notifications
-- The "reloaddata" entry is required to run the background process to update the data one time per day.
-- The "dummy" entry can be used to force reading the data, update the Domoticz text device and see if there are any errors or missing garbadge types.

garbagetype_cfg = {
   -- Add any missing records below this line
   ['pmd']        = {hour = 00, min = 01, daysbefore = 1, reminder = 0, text = 'pmd'},
   ['gft']        = {hour = 00, min = 01, daysbefore = 1, reminder = 0, text = 'gft'},
   ['papier']     = {hour = 00, min = 01, daysbefore = 1, reminder = 0, text = 'papier'},
   -- Add any missing records above this line
   --  "reloaddata" is used to start the background update process at this given time.
   ['reloaddata'] = {hour =12, min = 01, daysbefore = 1, reminder = 0, text = 'trigger for reloading data from website into garbagecalendar.data'},
   ['dummy1']     = {hour = 12, min = 01, daysbefore = 0, reminder = 0, text = 'dummy to trigger testing'}
}

-------------------------------------------------------------------------
-- Language options Dutch
-- Date/day info:
-- used by getdate for formats "mmm" & "mm"
--
-- Pas deze tabellen aan indien de afvalverwerker andere afkortingen gebruikt.
daysoftheweek = {'zon', 'maa', 'din', 'woe', 'don', 'vri', 'zat'}
Longdaysoftheweek = {'zondag', 'maandag', 'dinsdag', 'woensdag', 'donderdag', 'vrijdag', 'zaterdag'}
ShortMonth = {'jan', 'feb', 'maa', 'apr', 'mei', 'jun', 'jul', 'aug', 'sep', 'okt', 'nov', 'dec'}
LongMonth = {'januari', 'februari', 'maart', 'april', 'mei', 'juni', 'juli', 'augustus', 'september', 'oktober', 'november', 'december'}
-- Wordt gebruikt om de maand afkorting van de ontvangen kalender data te vertalen naar het maandnummer. Meerder opties mogelijk.
InputMonth = {jan = 1, feb = 2, mrt = 3, maa = 3, apr = 4, mei = 5, jun = 6, jul = 7, aug = 8, sep = 9, okt = 10, nov = 11, dec = 12}
-------------------------------------------------------------------------
-- Language options English
-- Date/day info:
--~ daysoftheweek={"Sun","Mon","Tue","Wed","Thu","Fri","Sat"}
--~ Longdaysoftheweek={"Sunday","Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"}
--~ ShortMonth={"Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"}
--~ LongMonth={"January","February","March","April","May","June","July","August","September","October","November","December"}
-- Used to translate the month abbreviation back to the month number. Can contain multiple options for abbreviations.
--~ InputMonth={jan = 1, feb = 2, mar = 3, apr = 4, may = 5, jun = 6, jul = 7, aug = 8, sep = 9, oct = 10, nov = 11, dec = 12}

[jvdz]

I see you have a capital V in the path ....shouldn't that be a lowercase v?

Code: Select all

scriptpath = '/volume1/docker/domoticz/scripts/lua' -- specify the directory for the main "script_time_garbagecalendar.lua" script
domoticzjsonpath = '/volume1/docker/domoticz/scripts/lua' -- specify the path to domoticz where the JSON.lua file can be found
 

is this path also correct to store the Data and Logfiles?:

Code: Select all

datafilepath = '/var/tmp' 

.. and only use the testnotification=true to test he notification system one time. The other 2 only when debugging issue:

Code: Select all

mydebug = true -- (true/false) -- run the script as it normally does when any of the scheduled times is the current time
testdataload = true -- (true/false) -- run the web update module with each run for testing/debugging purposes
testnotification = false -- (true/false) -- this will trigger a test notification for the first record for testing the notification system

Could you please make the change to ensure the path is correctly defined taking into account it is case sensitive and then send me the log files when they still fail? Just zip them up and send them to my GitHub Email address.

[smaus]

i dont have a log file in my /var/tmp

[jvdz]

I understand when you are looking in the actual /var/tmp! You are running this in Docker, so it will be stored inside the Docker structure!
That is why I made the comment about the setting for datafilepath = '/var/tmp'

[smaus]

i changed it to /volume1/docker/tpm/ but still no log file

[RonkA]

i changed it to /volume1/docker/tpm/ but still no log file

tpm ==> tmp

[smaus]

changes but no result

[smaus]

changes but no result

I removed it dont get it working

[jvdz]

Well, i can't test the docker setup myself, but there has to be something wrong there when the logfiles& data files aren't generated when you set the proper directory. I would ensure this directory is outside of the container to ensure you can access them and they are also persistent.

[hoeby]

Well, i can't test the docker setup myself

I want to try to help, if that is OK.

I was using to old script from JVDZ, but that doesn't work anymore, because we have a new trash collector this year with a different app.
Want to use the new script, because the new collector uses "De Afvalwijzer", which is supported by the new script.
My system gives the same notifications back, i also run in docker.

I will setup a test docker environment, to test out what is needed, to protect my live environment from doing things which i will regret afterwards.
Don't expect an answer this evening, give me some time.

[FireWizard]

Hi all,

For anyone, who might need it, I have a Node-RED flow available, which pushes the next collection date to MQTT.
Uses "mijnafvalwijzer,nl" and Custom icons.

It is updated once a day (in my case 18:00h).

Screenshot_custom icons3.png (51.94 KiB) Viewed 1396 times

Regards