Unable to create a property in a RFXCOM Unit

[James Sentman]

on first glance (meaning that I haven't tried it and didn't really scan it in detail for scripting errors ;) this looks like it would work fine. There is no advantage of one technique over another as far as the system or XTension is concerned, both will work.

I mostly use pseudos because then I have a second indication of an alarm condition and  I can look and see that Oh... fridge overtemp alert is on, thats something I should look at. In addition I can see those pseudos from web remote and elsewhere. I've also put them in a group who's on GroupMemberChanged event turns on a "master alarm" pseudo and sets the xOnLabel to the name of the pseudo. I have a display in webRemote that shows the status of that master alarm pseudo and as long as it's green and says "clear" I know all is well :) But if it's red, it also displays the name of the alert unit that turned it on. 

So there is no technical reason, but there is more you can do with a pseudo. 


On Oct 10, 2013, at 9:10 AM, Hendrik van Eeden <hvaneeden at comcast.net> wrote:

> This is the script that I am using.  It is the ON script for the temperature sensor.
> 
> if (future value of (thisUnit)) < 6 then
> 	Set Unit Property "timer" to 0 in unit (thisUnit)
> else
> 	if (Get Unit Property "timer" from unit (thisUnit)) is equal to 0 then
> 		Set Unit Property "timer" to (current date) in unit (thisUnit)
> 	else
> 		if (current date) - (Get Unit Property "timer" from unit (thisUnit)) > 50 * minutes then
> 			set description of the "Reporting Unit" to thisUnit
> 			turnon "Reporting Unit"
> 		end if
> 	end if
> end if
> 
> The reporting unit sends SMS's for this condition and others.
> It seems to work OK.  Why do you suggest a pseudo unit over a property? Are there advantage/disadvantages pseudo over property?

Thanks,
 	James


James Sentman                       http://sentman.com		http://MacHomeAutomation.com