Archived Forum

Not the clearest guide, but...
https://github.com/emoncms/event/blob/master/README.md

Paul

Blindingly fast response Paul - many thanks!

You're right - its not that obvious.  I've suggested a few extra lines of help in the readme.  In the meantime for anyone else interested in restoring this feature:

Login to your Pi as normal.

cd /var/www/emoncms/Modules

sudo git clone https://github.com/emoncms/event.git

Then log into your EmonCMS server and you should find "Event" under the new menu "Extras"

From the Admin Menu click "Update & Check" to add new columns for increased functionality (MQTT).

EmonCMS will confirm complete.  

Update Event settings by Clicking "Event Settings" from the Extras->Event screen (top right)

Now add events by adding new lines in Events module (Extras->Events)

Thanks again Paul for the pointer.

Mike

Hopefully Trystan will merge your changes, as it makes the installation process clearer.

Paul

Hello,

I could not find who created the event Module , but thanks to who created it especially the emaiI feature ;)

For it to function as required, I needed to change a couple of things:

1.) event_model.php in line 40 UPDATE    emoncms.event should be UPDATE event (now you can edit and also correctly test your email send feature, @XaroRSA your indication in the forum link#2738 helped me reason as to why the db did not have the setemail correctly :)

2.) event_list.php

Lines 319 - 320 Workaround to get default insertion into the db as without changing the selection for "set email" the #not-email is not available and hence email is not inserted into the db May not be the correct way but code in lines 307 to 315 adjusts the input blocks accordingly to the selected "action", however "email" being the first selected one value="0" the document keeps it hidden even though we call .show(), hence the workaround to prepare the document with a clean call to

$("#not-email").show();

$("#not-value").hide();

Line 85, added this to help show clearly who is the result of the triggered email

<td><?php if ($item['action']==0) echo $item['setemail']; ?></td>

With this we can :: insert a triggered task to send an email to a particular user, test it and even edit it after insertion, all this also depends on the capability of your outgoing SMTP mail server.

good luck,

aniston.

Aniston, I created the event module. Glad you like it :)

I'm no longer running OEM, as I need to figure out a better way of storing the data. Awaiting the new Raspberry Pi, which means I may look into this all again, running the db on an external drive.

Hello Nick, nice to know you made the energy module, I should have noted that you authored https://github.com/emoncms/event but i've seen that only now , sorry.

I created 2 pull requests on https://github.com/emoncms/event can you give tham a look when you have your new setup ready.

Also I've been looking into the feasibility of what it would take to integrate "Telegram" (similar to the whatsApp messenger).

Telegram has a client API for Developers (only the client side) as for now telegram is still free and without ad's, they have working webside clients but no PHP-scriptable examples, only some javascript and a fully working Terminal CLI. I still do not have a clear idea as to how and where to look into integration but the javascript client "webogram" looks interesting, but is fully integrated with Angular.js. It is not clear what happens if the client pre-registered with a cell phone number and an access token later looses the AUTH ? i guess another access token will have to be acquired and this will break the process and sadly require user intervention.

regards,

aniston