Notices

I solved it by uninstalling then re-installing Alarmed.

Since the entries made are actually a part of alarmd's setup, they were still there when Alarmed was re-installed.

Just for update: I got rid of tweakr and installed profilesx and camera lens launcher instead as suggested and they seem to work good. I configured similar profiles as I had in tweakr and named them the same, then updated alarmed and ----- alarmed just took the 'new' profiles everywhere I used them. So it was a quite transparent upgrade, given that the configured profiles still exist. Thanks for that!

i finally switched over too, great app !!!!!!!

Well.....everything could be done by editing some config file, this doesn't mean this is the best way for end users

False: I use tweakr with italian profile names and it works good (if you mean using latin characters or strange symbols maybe you're right I never used them so I don't know if they work)

I use alarmed daily and I think it's a very good program (I'm also thinking about donate some money) but the policy to remove support for other programs forcing users to install other tools is not very good IMHO.
Keep up the good work
Bye!

Hunludvig (and alarmed author, if you want to make these suggested edits), here's a tip for range() usage: you can include a 'step' value - you don't need to check every possible value in range(0,59) for modulus-n being 0. Thats like adding 5 by adding 1 five times - which one is better?! Hence line 236 in the alarmed_backend.py post-diff-patch resulting file can be:

instead of
Same for line 256, so it could be:
instead of
Also for line 316 (uses "range(0,6)"). I might be tempted to do other bits of code slightly differently, but this range() usage was something that looked too wasteful to me as a logic and range() usage paradigm.

Faster & less code too.

When the start of the range isn't a multiple of n, its not so simple for the later patch edit at line 296 in the post-patched version (which might yet have changed again since?). That one uses "range(1,12) if not i%n" and is not equal to "range(1,12,n)" - but because "range(0,11,n)" IS equal to "range(0,11) if not i%n", you can change the range and +1 back in after thusly (the new version is):

Hi Jgbreezer,
I didn't know this usage of function range(), it perfectly substitutes the code I wrote, please create a patch and post it here to be merged in the next version.

I don't know if this relates to Alarmed or alarmd:

I have commands that are executed at the top of each hour, in particular a command to play a sound file for clock chimes of that hour (soundfile with 1 chime at 1 o'clock, soundfile with 2 chimes at 2 o'clock, etc.)

Today I noticed that the commands are executing an hour earlier that I put them in last weekend. Looking at the schedule in Alarmed, they show that the command at 1 o'clock is now to play the soundfile with 2 chimes, at 2 o'clock to play the soundfile with 3 chimes, etc.)

The time is correct on my phone, the scheduling in alarmd seems to have changed.

Is this somehow related to the change to daylight savings time this coming weekend?

I have created a wiki.maemo page for Alarmed commands to help make everyones N900 more powerful .... if you have any cool commands please go to the wiki page http://wiki.maemo.org/ALARMED_Commands_List and add them in.

If you dont have a wiki account and cant be bothered to create one please inbox me your code and I will add it in for you.

Hey rotoflex, why not put your commands into the alarmedwiki ... see my signature.

I added play-sound to the alarmedwiki.

If anyone wants them, the sound files I use for clock chimes are at
http://www.sendspace.com/file/pzha6r

I put them all in a new directory in the N900, /home/user/MyDocs/.sound/ClockChimes and have Alarmed call them from there.

They are the "tingtang" clock chimes, which are a short chime format, & they are mixed at 45 dB down per GoldWave so that they will be soft & not blow the speakers. The filesizes seem huge, but I ran out of steam after experimenting with several attenuation levels and blew off trying to make the filesizes smaller. You can use them to turn your N900 into a mantel clock or very expensive pocketwatch.

Schedule tingtang1Q hourly at :15 after, tingtang2Q hourly at :30 after, tingtang3Q hourly at :45 after. The top of the hour (XX:00) is scheduled at that particular time daily by either tingtanghourXX or tangstrkiechordXX. I use tangstrikechordXX for the AM hours, and tingtanghourXX for the PM hours.

It uses almost no battery. Disconnected from the network and running no other programs, one weekend from 5 pm Friday until 6 am Sunday it consumed only a barely perceptible sliver of the battery graph.

The quarters are fast to set up, since they repeat hourly at their time. But all 24 of the top of the hours must be done individually so they take a while. I had hoped to write a command line application to select a soundfile, repeat hourly strikes, & allow volume adjustment, but came up bust with installation of SDK or setting environment for includes on a couple of computers.