| Author |
|
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: December 23 2009 at 12:05 | IP Logged
|
|
|
I am really looking forward to getting rid of the syntax error in my logs and some CC improvements that help show light status easier... Thanks.
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 23 2009 at 15:13 | IP Logged
|
|
|
Perhaps you already know this but you can suppress the syntax error event log message with the Event Log logging options. It is useful when debugging new formulas, then turning the option off when things are stable.
__________________
Lee G
|
| Back to Top |
|
| |
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: December 30 2009 at 16:11 | IP Logged
|
|
|
Any plans for a new release coming out and what it may have new? I am really hoping for some new features with the control center. Thanks.
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: December 30 2009 at 16:31 | IP Logged
|
|
|
Sounds like Dave is getting close but he didn’t indicate when…
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: December 30 2009 at 18:18 | IP Logged
|
|
|
Any indication of what may be included in the next upgrade?
BeachBum wrote:
| Sounds like Dave is getting close but he didn’t indicate when… |
|
|
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: December 30 2009 at 19:23 | IP Logged
|
|
|
This is all I have seen from part of an earlier post by Dave:
“Since the new PowerBuilder version of the upcoming beta (11.5) allows for these toolbar tips quite easily, this is an open call to anyone who would like a toolbar tip added to PowerHome.
Just post them to this thread and I'll do my best to add as many of them as I can. Be as explicit as possible on what the tip should say and where it appears and I'll get it done.
Thanks,
Dave.”
EDIT: I might add this came from http://www.power-home.com/forum/forum_posts.asp?TID=2428&PN= 1
Edited by BeachBum - December 30 2009 at 19:25
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: January 05 2010 at 11:17 | IP Logged
|
|
|
Dave, I am wanting to start work on my control center screens again, but was hoping to see if I should wait for the next upgrade. At one time you mentioned you were making it easier for a CC button to know the status of a light.
Do you know when the next release will be out and/or what you are looking at including? Thanks for your help.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 06 2010 at 15:22 | IP Logged
|
|
|
Hopefully not too much longer. Ive added the support for new controllers and am currently working on some support for Insteon Extended commands. After the extended commands are done, I'll then start on the Control Center enhancements. Rather than hold up the next beta longer by adding all of the planned CC enhancements, I'll probably add just a few initially. As such, I expect it to be about 1 more month before the beta is online for download.
Some of the CC enhancements should include a new Device button that reflects the current status of the device (and controls it) as well as Static text that will automatically update with a device status. Also will be a graphic that will update based upon the device status. Theres more planned but these should initially make real time (codeless) update of the CC based upon Device status easier.
Dave.
|
| Back to Top |
|
| |
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: January 06 2010 at 17:12 | IP Logged
|
|
|
Thanks for the update Dave... I am really excited for the CC enhancements... appreciate it.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: January 06 2010 at 20:04 | IP Logged
|
|
|
Nice! 
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: January 09 2010 at 15:00 | IP Logged
|
|
|
Hi - will the next upgrade treat any of these....?
http://www.myx10.com/forum/forum_posts.asp?TID=1534
http://www.myx10.com/forum/forum_posts.asp?TID=1550
http://www.myx10.com/forum/forum_posts.asp?TID=1552
Edited by jeffw_00 - January 09 2010 at 15:01
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 14 2010 at 20:43 | IP Logged
|
|
|
Jeff,
Item 1534 (PowerHome Explorer Grouping)...almost. The next beta includes a completely new tree control (I had to create one from scratch using a PowerBuilder datawindow) in preparation for setting up the grouping. I started the group code but the existing treeview control was not near fast enough to re-render everytime the group changed. The new treeview (you'll recognize it as new instantly) allows me to proceed with the grouping code.
Item 1550, SubItem 1 (Restore minimized windows)...Yes
Item 1550, SubItem 2 (Right-click in treeview of Explorer)...partially. Right-click now will not minimize the treeview and works equivalent to left clicking. I started to add code for the menuing system thinking I could share the menu in the detail but discovered that it had to be a completely new, separate menu so Ive temporarily yanked it out. Depending upon time, I might try to get some rudimentary menu in.
Item 1550, SubItem 3 (Formula errors posted to log)...This is already in version 2.1b. In the next beta, it actually differentiates between an actual error and a formula that evaluates to "!"
Item 1550, SubItem 4 (Post macro parameters to log). Not yet, but it should be fairly easy to do. Keep in mind that a log entry is limited to 1024 characters. First question is what do you consider to be parameters? [LOCAL] vars? [TEMP] vars? Both? If you're wanting local and temp vars (these are the only things I can think of other than LOCAL1 thru LOCAL5 in the ph_macroparm function, do you want the full length of ear var or would it be best to limit each var to a certain number of characters? Say the first LOCAL1 has the URL of a webpage you want to parse and its 8K of data, you would only get the data contained in LOCAL1 and none of the others. Give me some details on what you think would work best (anyone can chime in) and I'll try to fit it in.
Item 1552 (PH push "believed" state to devices)...I guess I missed this so never really thought about it. I see a post from you to push the state and a second post to retrieve a list of controllers from a device. I assume you're inquiring about your post. With the second post, a SQL statement will give a list of controllers of a device. Concerning your request, Im thinking what it would be would be a ph_ function that would pull a list of every device in PH and them try to make the database state the actual state via controller commands. This could of course take quite awhile depending upon the number of devices. Also, should this also work for digital outputs and analog output devices? X10? Should there be a way to limit it to certain devices? Give me a few more details of what/how this should work and I'll do some thinking on it.
Dave.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: January 14 2010 at 21:06 | IP Logged
|
|
|
Hi Dave - thanks for replying. The Grouping would be really nice - I have many dozens of macros, events and triggers and it's relatively hard to sift through them.
Re 1550
1) great
2) minor usuability flaw. fix it only if it's easy
3) yup - thanks!
4) see #2, can be faked with User messages when debugging a particular problem. (sorry, should have qualified my request post).
Re 1552: This is another attempt at a 'recovery' mechanism similar to the "roll back to a particular time" that we had discussed in a different thread.
Here's what I'm trying to solve:
PH got hung up for some reason (lost contact with controller, etc.), but kept marching forward and updated its internal view of state-of-the-world.
I -know- that the internal database is the way I want the world to be, but the "world" isn't up to date. So push the (good) internal state out to the "world" and all is well.
It's a nice to have, so I'm cool with however you prioritize this compared to other requests.
Finally, while i have your attention 8-}. When I write software, I always like to 'diff' my new code against my old before I put it aside, to make sure I agree with all my changes. I wish there was some way to do this in PH. I'm willing to do a bit of perl scripting, but can there be a way, to like, write out all the macros (and maybe even triggers and timed events) to a file in a reasonably parsable format, so I can write them out before and after, and (perhaps with some post processing) use a unix tkdiff -like script to check my changes?
The problem with the PH interface is that the moment you change a field, all history of what was there before is lost. Again - not a killer, but definitely a couldn't-hurt-to-ask nice-to-have. 8-}
Best regards
/j
Edited by jeffw_00 - January 14 2010 at 21:10
|
| Back to Top |
|
| |
tbeckman
Senior Member
Joined: December 30 2007
Location: United States
Online Status: Offline
Posts: 149
|
| Posted: February 12 2010 at 15:26 | IP Logged
|
|
|
Our we close to beta release... I can't stand the anticipation any longer 
|
| Back to Top |
|
| |
scottmi1
Groupie
Joined: July 11 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 16 2010 at 09:11 | IP Logged
|
|
|
Any further updates on what new features will be included or when we'll see a beta?
Thanks,
Mike..
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 16 2010 at 22:51 | IP Logged
|
|
|
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.
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: March 16 2010 at 23:07 | IP Logged
|
|
|
WOW!!!! 
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
scottmi1
Groupie
Joined: July 11 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 17 2010 at 06:37 | IP Logged
|
|
|
Yeah, what he said - WOW! Thanks for the detailed overview Dave. I'm definitely looking forward to this new release!
Mike..
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: March 17 2010 at 10:38 | IP Logged
|
|
|
Great news Dave. I look forward to it. Still, I gotta ask... 8-}
What about (in order of decreasing importance) extended commands..
http://www.myx10.com/forum/forum_posts.asp?TID=2515&PN=1
comment fields
http://www.power-home.com/forum/forum_posts.asp?TID=1681
or for the ability for a macro to return a value (other than through a global)?
http://www.power-home.com/forum/forum_posts.asp?TID=1589
I mean, you're definitely doing a -lot- of work, and it's well appreciated, but I figured it can't hurt to ask about these?
Thanks!
/j
Edited by jeffw_00 - March 17 2010 at 10:51
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 17 2010 at 19:04 | IP Logged
|
|
|
Extended Insteon commands are partially implemented in the next beta. Ive got a couple of extra functions dedicated to sending Extended commands and PowerHome is receiving them. Im still integrating the automatic use of extended commands into PowerHome background processes. First is the determination of which devices actually support the Insteon commands (usually firmware dependant based upon device) but can also depend upon distance (it supports extended commands but is too far away for them to be reliable) or it supports extended commands but is on an opposite leg with no phase coupler that supports extended commands (say no access points and only the older signalincs). Full extended command support is high on the list and will be coming soon but the next beta will only have partial support. My goal is to have dedicated (device dependant) configuration screens under the Devices tab of the Insteon Explorer for device specific operations such as setting the beep settings and dim levels of LED's and lightbars, settings specific to motion detectors, etc.
Comment fields on macro detail are in this beta...just did not have the list updated.
You should be able to return a value from a macro already (unless I misunderstand the goal). The ph_macroparmret function allows you to call a macro (and pass parameters) and will return a function specified value (place the value to be returned by the macro in [LOCAL1] before terminating the macro) without using a global. Not sure if this is what you're looking for but is what I use when I want to execute a macro and return a specific value from that macro.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: When is the next upgrade?
