Support forum for Cumulus weather station software
https://cumulus.hosiene.co.uk/
External Programs now sets the working directory to the location of the executable/script rather than the Cumulus MX home directory
Thank you for that information. I had read the whole change log but I guess I did not remember that bit of information. That would definitely affect the operation.
That definitely can cause problems. But when looking at the earlier messages, Dador did have the full path to both executable and php file, so in my eyes that really should work. I think we need to summon @mcrossley to this investigation.
This is the bit that is tripping people up - by the script assuming it is running in a certain place on the filesystem and accessing resources relative to that position. It always pays to code absolute paths in your scripts, or to 'cd' to that location within the script.Edit. But when thinking ahead… If you run php from c:\php, and then point to the php file located in CMX directory, the working dir still regardless causes the php script search for the diary.db from c:\php ? So in this specific use case you probably would need to modify the php code so that it points to diary.db with the full path?
Glad to help, usually there is something to learn myself also. Since this change has caused trouble also for CUtils users, this still may turn to Mark reverting the change in future CMX builds… remains to be seen.surban21 wrote: ↑Tue 03 Dec 2024 5:35 pm @SamiS - I located the issue and of course it was on my end inside snowSumData.php script. The issue is fixed and finishing testing then I'll roll out the revised script shortly.
Thank you for you help in trying to isolate the problem. If I had only remembered that change in the CMX 4.2.0 change log I could have saved us all the frustration. LOL.
As the ChangeLog of CMX notes: the 4.2. changes have been reverted to return to the old situation!Dador wrote: ↑Thu 05 Dec 2024 7:36 am To make it funny, recent fixes to the snowSumData.php script code don't work with CMX 4.3.
So I went back to the original code. The script works in the original version.
I was in a hurry to judge. Currently, the script does not work with CMX 4.3 in the old and new versions.
It also doesn't work with Windows Task Scheduler
Maybe there are some changes in diary.db that cause the error?
Steve Urban, I think you need to look into this.
@Dador - the diary.db in CMX 4.3.0 has been restructured so unfortunately the present snow scripts are going to fade away. They will only work on CMX 4.2.xx and below until I decide if I want to rewrite the scripts for the new versions of CMX. Thanks for using them though.
Code: Select all
CREATE VIEW IF NOT EXISTS VDiaryData (Timestamp, entry, snowFalling, snowLying, snowDepth) AS
SELECT datetime(d,t) AS Timestamp, e AS entry, sf AS snowFalling, sl AS snowLying, sh AS snowDepth FROM
(SELECT Date AS d, Time AS t, Entry e,
CASE WHEN Snow24h > 0 THEN 1 ELSE 0 END AS sf,
CASE WHEN SnowDepth > 0 THEN 1 ELSE 0 END AS sl,
Snow24h AS sh FROM DiaryData);
or without Column-Name-List:
CREATE VIEW IF NOT EXISTS VDiaryData AS
SELECT datetime(d,t) AS Timestamp, e AS entry, sf AS snowFalling, sl AS snowLying, sh AS snowDepth FROM
(SELECT Date AS d, Time AS t, Entry e,
CASE WHEN Snow24h > 0 THEN 1 ELSE 0 END AS sf,
CASE WHEN SnowDepth > 0 THEN 1 ELSE 0 END AS sl,
Snow24h AS sh FROM DiaryData);
Code: Select all
/* OLD Schema:*/
sqlite> .open C:\Wetterstation.CumulusMX\datav3\diary.db
sqlite> .schema
CREATE TABLE IF NOT EXISTS "DiaryData"(
"Timestamp" datetime primary key not null ,
"entry" varchar ,
"snowFalling" integer ,
"snowLying" integer ,
"snowDepth" float );
sqlite> select * from DiaryData;
2024-12-09 00:00:00||1|0|0.0
2024-12-06 00:00:00||1|1|1.0
2024-12-07 00:00:00||1|0|1.0
2023-11-01 00:00:00||1|0|2.0
2023-02-01 00:00:00||1|0|2.0
2022-05-01 00:00:00||1|0|2.0
2022-12-01 00:00:00||1|0|2.0
/* NEW Schema: */
sqlite> .open C:\Wetterstation.CumulusMX\data\diary.db
sqlite> .schema
CREATE TABLE IF NOT EXISTS "DiaryData" (
"Date" datetime primary key not null ,
"Time" time not null ,
"Entry" varchar ,
"Snow24h" float ,
"SnowDepth" float );
CREATE TABLE dbversion (ver INTEGER PRIMARY KEY);
CREATE VIEW VDiaryData (Timestamp, entry, snowFalling, snowLying, snowDepth) AS
SELECT datetime(d,t) AS Timstamp, e AS entry, sf AS snowFalling, sl AS snowLying, sh AS snowDepth FROM
(SELECT Date AS d, Time AS t, Entry e,
CASE WHEN Snow24h > 0 THEN 1 ELSE 0 END AS sf,
CASE WHEN SnowDepth > 0 THEN 1 ELSE 0 END AS sl,
Snow24h AS sh FROM DiaryData)
/* VDiaryData(Timestamp,entry,snowFalling,snowLying,snowDepth) */;
sqlite> select * from DiaryData;
2022-05-01|00:00:00|||2.0
2022-12-01|00:00:00|||2.0
2023-02-01|00:00:00|||2.0
2023-11-01|00:00:00|||2.0
2024-12-06|00:00:00|||1.0
2024-12-07|00:00:00|||1.0
2024-12-09|00:00:00|||0.0
2025-01-02|00:00:00||1.0|1.0
sqlite> select * from VDiaryData;
2022-05-01 00:00:00||0|1|
2022-12-01 00:00:00||0|1|
2023-02-01 00:00:00||0|1|
2023-11-01 00:00:00||0|1|
2024-12-06 00:00:00||0|1|
2024-12-07 00:00:00||0|1|
2024-12-09 00:00:00||0|0|
2025-01-02 00:00:00||1|1|1.0