Deprecated Calls

[mark_anderson_us]

Hi Guys

Just shelled out $40 for AC-RF2 and shocked to find loads of log entries reading this:

8/6/2011 10:38:39 PM  - Warning - 'status' property on device  ACRF2 Plugin ACRF2 Device Monitor was accessed - this property has been deprecated and should not be used.

What the heck. For a $40 plug-in, I expect to get something properly developed and supported???

[mfisher]

The ACRF plugin was properly developed, is rock solid and definietly worth the price. I've been using it for years and it's been a set it and forget it proposition. A recent version of Homeseer depricated the status property for all plugins, so you may see this warning for others as well. I get this for the ACRF and RCS-X10 stat plugins. Not to worry though as you should only get these on HS startup, nothing is broken and all functionality is still there.

[Wadenut]

On the HS2 main configuration page there is an option to
"Disable obsolete API procedure warning messages"
Set this to YES and you won't see the log warnings.
Rick provided this some time ago as an interim solution until all the plugins catch up. Presumably this option will disappear by the time HS3 is released.

ACRF2 is, as Mark said, rock solid and is definitely well supported.

[mark_anderson_us]

It does work as advertised. just concerned that an upgrade to HS is gonna break it, if it's using depracated calls

Regards

mark

[tenholde]

The concern is that the author is no longer maintaining and updating this plugin. It certainly would be straight forward to fix it, and it has been an issue (albeit a minor one) for awhile. What if something more serious is broken by the next HS release? Is there anyone there to fix it?

tenholde

[mark_anderson_us]

I wasn't aware it wasn't being maintained. Wouldn't have forked out $40 for an obsolete product had I known

[Wadenut]

So far as I know, Jon does support the plugin. You may need to email him directly (per the instructions in the Doc) as I don't think he regularly checks the board.

[Uncle Michael]

The concern is that the author is no longer maintaining and updating this plugin. It certainly would be straight forward to fix it, and it has been an issue (albeit a minor one) for awhile. What if something more serious is broken by the next HS release? Is there anyone there to fix it?

From my experience, Jon is one of the most reliable plug-in authors. He appears to avoid version releases that have only minor changes, but when he does release a new version it is very thoroughly tested. This issue has no effect on the performance of the current plug-in, so I'm betting that he sees no need to release a new version just to make the nagging messages from HST go away, especially since you can turn it off if you want to.