XTension 907

[Ryan McLean]

create a unit with the housecode a period and the words "dim" or "bri" as the address and those units will not receive any dim/bright commands for the housecode the remotes are set for.


I am going to go out on a limb and assume you meant "now receive"

-----
Ryan
Sent by Thumbs

_____________________________
From: James Sentman <james at sentman.com<mailto:james at sentman.com>>
Sent: Friday, November 13, 2015 1:29 PM
Subject: XTension 907
To: XTension Discussion List <xtensionlist at machomeautomation.com<mailto:xtensionlist at machomeautomation.com>>


* Preliminary support for My Sensors
* XTension can now connect directly to a serial or wifi mySensors gateway.
* Units are created in XTension as they are received from the sensors. The addressing convention is the nodeID and child ID as 2 bytes hex each and then a period followed by a descriptive suffix of what the variable they are reporting is. The address and suffix will be placed in the name of a new unit created, after that you can change the name in XTension to something more descriptive and useful.
* XTension will respond to requests for the time/date.
* At this moment XTension always responds to a configuration request with a response to set the format to "Imperial" units as opposed to metric. I'll add an interface to that in the next version.
* Any child device that reports multiple variables will create multiple units in XTension with different suffixes in the address.
* sending data to and receiving data from most devices are supported with the exception of the ones that I couldn't quite make sense of why they were broken up into separate variable types. In this release the scene on/off and window covering devices may not work. There may be problems with RGB and RGBW devices as I haven't yet tested what data format they send in.
* The Query verb is supported to send a get data request to the mySensors device and if they support replying to it the unit value in XTension will be updated when they respond.
* This should be considered development level software, not even beta yet.


The mySensors stuff looks really nice for those that have some experience with DIY. I wouldn't recommend anyone who isn't already proficient in such things to jump in yet at this point.


* Made a change to the handling of DIM/BRIGHT commands from wireless X10 receivers such as the RFX and W800:
* the dim/bri buttons on X10 remotes are of little usefulness in a busy wireless environment since they do not encode a unit but only a housecode. They apply themselves to whatever unit was last received. You press the ON button for a device and then hit the dim button to control it. Now with so many motion sensors and such out there if another device sends a signal after you select a unit it will change which device the dim/brights are sent to causing great confusion. Most of my remotes that have these buttons I now never use at all because they just aren't reliable.
* You can now create a unit with the housecode a period and the words "dim" or "bri" as the address and those units will not receive any dim/bright commands for the housecode the remotes are set for. It behaves similarly to the all units on and off handlers. So all remotes set to housecode A will be sent to a unit with the address of "A.dim" a bright command will send it an ON command, a dim command will send it an OFF. So you can now use those buttons for something and with a little planning you can break your remotes up by housecode to make those buttons useful again.


http://machomeautomation.com/doku.php/beta

Thanks,
James


James Sentman http://sentman.com http://MacHomeAutomation.com<http://machomeautomation.com>



_______________________________________________
XTensionList mailing list
XTensionList at machomeautomation.com<mailto:XTensionList at machomeautomation.com>
http://mail.machomeautomation.com/mailman/listinfo/xtensionlist


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20151113/f68a3b9f/attachment.html>