Author |
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: August 26 2010 at 13:23 | IP Logged
|
|
|
I (like others) eagerly await the next release of PH. I am hoping that the new mail functionality (see below) might allow for "instantaneous" type text message/push e-mail control.
I am looking for ideas and thoughts as how to have PH
1) Trigger when new mail (or a text message) arrives. Pushed (vs polling) has the more "instantaneous" reponse.
2) How to get at, and pass the txt/email information into PH so that it can be acted upon.
It would be great if a person could TXT MSG their PH system, and have PH act on or say (via TTS) the txt or push e-mail message (via their cell phone).
dhoward wrote:
Well definitely not moving as fast as I had hoped but Im on the final stages. Currently in the middle of working the Control Center enhancements. After this is complete, I'll need to update the Database Upgrade Utility and then we should be good to go. I hate to give a date because I always miss them . Below are some of the changes that will be included in the next beta:
Added support for the X10 CM15A controller (both PLC and RF). This support uses the ActiveHome SDK so any limitations are limitations of the SDK itself.
Added support for the Global Cache GC-IRL Infrared Learner.
Added support for the Global Cache GC-IRE Infrared Extender.
Modified most serial based controllers so that they can also be connected to the serial ports of a Global Cache. Controller setup modified to support either a local serial port or the remote serial port of the Global Cache.
Fixed bugs associated with Virtual Insteon devices (Insteon devices whose address starts with V?.??.??). For both PLC and PLM, poll status commands were being performed against virtuals. This is now fixed. For PLM, creating a virtual would result in a critical error as well as a critical error whenever the status was polled. This has been fixed as well.
Changes made to Insteon group status functionality. When receiving incoming Insteon group commands, if PLC/PLM is a member of the group, the appropriate PLC/PLM group status will be updated. Also fixed bug on updating PLC/PLM group status when broadcasting commands to group 255.
Added new "No Control" column to Insteon Types maintenance. Previous versions would not show "Control" buttons in the Device Status screen if the Responder Groups column was 0. The appearance of the "Control" buttons is now determined by the "No Control" column.
Added new "Dont Display" column to Insteon Groups maintenance. Placing a check in this column will cause the Insteon Group to not appear in the Device Status screen.
Rewrote ph_sendsmtpemail and ph_sendsmtpemailfile functions to use a new SMTP email control. Both functions now operate in a separate thread and performance is vastly improved.
New function ph_number (similar to existing number function). This function will convert a string to a number (long, integer, or double depending upon string). It will also properly convert negative numbers even if spaces exist around the negative sign. The number function will fail if one or more spaces exist between the sign and the number.
Modified IR triggers so that key description as well as incoming/outgoing code is passed in the TEMP variables. Also standardized all IR triggers so that the key number will be in the same TEMP var.
Modified PowerHome Shutdown routines so PowerHome will play nice with Windows Shutdowns and Logoffs. New ph_shutdown function to cleanly shut PowerHome down.
Updated Elk/Insteon M1XSP programming tab in Insteon Explorer to include support for newer M1XSP firmwares supporting Insteon PLM controllers.
Completely replaced all references to Microsoft Winsock control and Catalyst 3.6 Socket control with latest version of Catalyst Secure Socket tools.
PNG SUPPORT....FINALLY!
Webserver rewritten to use Catalyst Internet Server control. Webserver now supports SSL. Support for a new authentication routine using cookies also implemented.
Major facelift on PowerHome Explorer. New treeview control allows for better functionality and icons. New control will also enable the requested "grouping" functionality.
PowerHome code base upgraded to PowerBuilder version 11.5. This is the most current version of PowerBuilder.
Added support for new encrypted SQL routines. Now certain database actions can be accomplished without having to send in your database using a special encrypted SQL.
Device status screen has been updated for better touchscreen support. No more buttons for On, Off, and ADim. These have been replaced with a single dropdown list for control. Older styles still available though.
Rewrote both the PLC and PLM Insteon controller modules. Code has been aligned to share the same code base. Efficiency has been improved and new error detection algorithms implemented eliminating "echoed" commands and further improving speed. New routines also prevent lockups associated with controllers losing power.
PLC and PLM Insteon controller routines now only attempt to restart up to 5 times before timing out. Restart routines are now more intelligent.
Insteon communication reports rewritten to be more accurate using new underlying Insteon routines. Terms have been clarifed between NAK and Timeout along with support for ACK, NAK, and Timeout.
Modified Insteon PLM controller wizard (serial and USB) so PH will now attempt to automatically locate your attached PLM controller.
New Insteon Problem Links report. Comprehensive report that shows all potential problems concerning the Insteon network.
USB to Serial drivers for Insteon PLM and UPB PIM are automatically installed with PowerHome.
Removed Device ID and Network Password from UPB controller setup. PIM device ID and network password will instead be read directly from PIM registers (previously set by UpStart).
New trigger that is fired when an Insteon device is flagged as COMM Failed.
New triggers for controller connect, disconnect, restart, and failure.
Fixed bug in ph_sendsocketdata1 function where including a value of 4 in the flags parameter resulted in all of the data being returned as a string of \000.
Fixed ph_getglobal_n, ph_getvar_n, ph_sql_n, ph_formulabtn_n so that they properly interpret negative numbers with spaces around the negative sign.
Fixed major bug where a number of ph.??? Windows Script Host functions would not properly handle negative numeric parameters. All functions should now properly handle negatives.
Fixed bug where a legitimate formula evaluation result of "!" does not fire the Syntax error trigger and log entry. Only an actual syntax error will do this now.
Fixed bug where certain macro commands (Insteon, Insteon Group, Insteon Raw Group, UPB, UBP Link) could trigger a Formula Syntax error when none actually exists.
Fixed bug where an Insteon "Stop Manual Change" command could possibly trigger a status request to the connected PLC/PLM controller ultimately resulting in the controller being flagged as COMM Failed.
Fixed major bug where multi-channel UPB devices could not be controlled properly (all channels would be controlled together). Also fixed other minor UPB bugs.
Fixed critical error when attempting to Print Preview the Device Status screen. Print and Print Preview of PowerHome Explorer was enabled in 2.1b and inadvertantly enabled the Print and Print Preview options for the Device Status screen. The menu options remain enabled for Device Status and print and preview now work properly.
Fixed critical error (line 26 of f_executeph of w_formula) that occurs when evaluating a formula with a runtime error from the Formula builder window and the window is closed before the evaluation or the runtime error is complete.
Fixed critical error (line 26 of f_executeph of w_wshedit) that occurs when evaluating a formula with a runtime error from a PowerHome Multi-editor window and the window is closed before the evaluation or the runtime error is complete.
Fixed critical error (Invalid DataWindow row/column specified at line 10 in function f_id of object w_devicecontrol).
Fixed critical error (Null object reference at line 1 in function f_setmenu of object w_tabdesign).
Fixed critical error (Invalid DataWindow row/column specified at line 8 in itemchanged event of object dw_1 of uo_insteontypes).
Fixed critical error (Invalid DataWindow row/column specified at line 509 in itemchanged event of object dw_detail of w_explorer).
Changed the last of all X-10 references to X10.
New Functions:
ph_getlasterrorstring,ph_number,ph_sendsmtpemailasync,ph_sen dsmtpemailfileasync,ph_encrypt,ph_decrypt,ph_getmd5hash,ph_g etmtret,ph_runasuser1,ph_runsync1,ph_shutdown,ph_convertir,p h_ctlrcontrol,ph_getdeviceval,ph_setdeviceval
Changed Functions:
ph_geturl,ph_geturlviaproxy,ph_runasuser,ph_saveurl,ph_saveu rlviaproxy,ph_webds
Removed Functions:
ph_rr2topronto,ph_rr3topronto,ph_prontotogc,ph_prontotorr2,p h_connect,ph_disconnect
Hope this helps,
Dave.
|
|
|
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: August 27 2010 at 12:16 | IP Logged
|
|
|
Not sure if you missed it, but, there is currently support for inbound email (SMS, too) control.
|
Back to Top |
|
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: August 27 2010 at 16:46 | IP Logged
|
|
|
TonyNo wrote:
Not sure if you missed it, but, there is currently support for inbound email (SMS, too) control. |
|
|
Tony,
Tell me if I am missing something.....as I understand it, you have to set up a PH "timed event" to have PH poll for MAPI based "control" e-mails (I have not yet done this...it is just what I have read).
My thinking is that because you are relying on a timed event rather than a tigger to process the control e-mail, controlling PH this way would be rather sluggish.
You mentioned SMS. When I think of SMS, I think of rather instantaneous response. Can you elaborate more on this email control topic?
Thanks,
Steve
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: August 28 2010 at 11:13 | IP Logged
|
|
|
Yes, you need to poll email. I had my system checking every few minutes w/o any sluggishness.
Check the Users Manual for more info. Also, this excerpt is from page 67...
The Control Email is recognized from non-control email via the subject. Valid subjects for Control Email must be one of the following: Sendkeys, Formula, or Macro. Case is not important for the subject. If the subject does not match one of the previous cases, then the email is not processed as a control email. The subjects are self-explanatory and the body of the email will be processed appropriately. In the case of a Sendkeys control message, the body is considered a formula and is evaluated. The result of the formula will then be processed as a sendkeys. A Formula control message will have the body of the message evaluated and the result discarded. A macro control message expects the ID of a single macro to be executed.
|
Back to Top |
|
|
kemporama Senior Member
Joined: November 21 2008
Online Status: Offline Posts: 102
|
Posted: January 26 2011 at 00:10 | IP Logged
|
|
|
I just set up the email control checking tonight, and it seems to actually be working properly.
One thing I can't figure out how to do though is to run the process mail macro say every 5 minutes. It looks like the shortest a timed event can be is an hour. Is there a way to modify a timed event to make it run more frequently (rather than having say a macro running constantly with waits)?
Thanks!
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 26 2011 at 15:56 | IP Logged
|
|
|
Just type the number 5 .
Dave.
|
Back to Top |
|
|
kemporama Senior Member
Joined: November 21 2008
Online Status: Offline Posts: 102
|
Posted: January 26 2011 at 17:21 | IP Logged
|
|
|
I put a 5 in the frequency spot? I just tried that and it doesn't work. Which column should it go in, and do I need to set the timing or other columns to something specific on the line?
Thanks.
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 26 2011 at 19:30 | IP Logged
|
|
|
Hmmm...not sure why it wouldnt work. The "Frequency" column is in minutes and the dropdown values are just substituted (an hour actually puts 60 in the column). All the other timing values can just be left at their default.
When you say it didnt work, did the column not accept the value or did it accept and the timed event didnt fire in 5 minutes? The time the Timed Event actually fires is controlled by the "Reference Time" column. The "Frequency" is how many minutes from the time it fires till the next reference time.
Dave.
|
Back to Top |
|
|
kemporama Senior Member
Joined: November 21 2008
Online Status: Offline Posts: 102
|
Posted: January 26 2011 at 23:11 | IP Logged
|
|
|
I deleted the timed event and recreated it putting the # in the frequency column and it works this time. The first time I had it in nothing would fire, it would just sit.
Working now, all that matters. Thanks!
|
Back to Top |
|
|
Gadgets Senior Member
Joined: January 28 2008 Location: Canada
Online Status: Offline Posts: 178
|
Posted: March 16 2011 at 21:29 | IP Logged
|
|
|
Question regarding this. Last time I was following email control it relied on an installed email program (Outlook) and if Outlook locked up, so would PH. Has this changed now?
__________________ Friends, don't let friends install Norton Products
|
Back to Top |
|
|
|
|