Timeline for release of 2.8 with variables

[xd40]

Just got my ISY-99 and was shocked to see it doesn't have variables. I saw a thread that 2.8 would support variables. When will 2.8 be released and is support for variables still part of the release?

[Michel Kohanim]

Hello xd40,

 

Unfortunately I cannot give any timelines simply because we are still investigating all the changes to all parts of the code.

 

In the meantime, you can use the status of programs as binary variables.

 

With kind regards,

Michel

 

Just got my ISY-99 and was shocked to see it doesn't have variables. I saw a thread that 2.8 would support variables. When will 2.8 be released and is support for variables still part of the release?

[xd40]

I'll just keep using my 10 year old JDS Time Commander which has variables.

 

Sounds like variables are a long way off.

[Michel Kohanim]

Hi xd40,

 

I am sorry to hear that! I would appreciate it if you could tell me what you wish to accomplish that you cannot already accomplish with the current paradigm. I would sincerely appreciate your feedback.

 

With kind regards,

Michel

[chicharon]

Hello Michel,

 

Add me to the list of customers who are very disappointed in the fact that there is no support for variables in this product. I am also surprised that you question what might be done with them that cannot be done without. How about something as simple as toggling different scenes when an Insteon button is pressed. Sure, that can be done (and I am currently, begrudgingly doing so) by defining dummy programs for a two bit value each but that is just an ugly way to accomplish something that would be clean and easy with variables.

 

Or how about something a bit more complicated like assigning a variable a value based on the type of plants in a watering zone along with the time of year. At the end of each day use the weather module to check temperature, humidity and precipitation and formulate a number based on those factors. Subtract that number from the originally assigned number and when you reach zero, schedule watering at the appropriate time. You would need 8 programs to hold a mere 256 bit value (which would not suffice) and a clunky method to actually do the math given the current paradigm. Who knows, you may sell more weather modules (I'd buy one) if we had a better way to program the ISY.

 

Given it has been nearly 9 months since the last official release and over 4 months since the last beta release and given this does not appear to be a priority I guess it is a pipe dream to think we might get variables anytime in the distant future. Since we cannot seem to get you to commit to a date, can you describe the type of variable support that we may expect if they ever do come available (i.e. size, program and global visibility, statics and not, ability to pass to another program, etc.)

 

Sorry if this sounded like a rant. That was not my intent but I really feel this little box could be so much more than it currently is if basic things used in the simplest of programs started becoming available.

[Xathros]

Add me to the list of those wanting MVars to work with. I have a whole program folder called "Status" that contains kludgy workarounds for the lack of MVars.

 

I agree they are not "Necessary" BUT boy would they make life much easier in the ISY world.

 

-X

[Michel Kohanim]

Chicharon,

 

I understand your disappointment. Sometimes we all lose the sight of the fact that as an organization, we have to first ensure that the company continues to run and operate otherwise we'll be letting down all our customers.

 

I have no choice but to ignore your comments about the release cycles simply because you are not privy to what is actually being done internally. Furthermore, having 100s of beta releases with minor changes is a support nightmare for us.

 

As I mentioned before, changing the way triggers work goes deep into every part of the code. We are currently investigating two approaches one of which is less complicated but less powerful and the other one of which is extremely powerful but extremely complicated.

 

With kind regards,

Michel

[chicharon]

I have no choice but to ignore your comments about the release cycles simply because you are not privy to what is actually being done internally. Furthermore, having 100s of beta releases with minor changes is a support nightmare for us.

 

I would never suggest "100s" or even tens of beta releases (between official releases) nor am I implying criticism here (sorry you took it this way). We are privy to what is targeted for the next beta release and those changes are scheduled to take roughly 4 months from the last beta release. If the changes defined in 2.7.7 take this amount of time and variable support is considered a major change and there is no estimate on when variable support might be implemented then it is difficult to imaging when this feature might be delivered. That was my point IRT releases. I wish it wasn't left up to me to calculate when we might see such a feature but without a roadmap or a statement that includes a possible target date, there is nothing else to go on. This is an enhancement that is important enough that I cannot help but try to determine when it might become a reality.

[Michel Kohanim]

Hi chicharon,

 

I totally understand what you mean and I can assure you that we are doing as much as we possibly can given our resources and constraints.

 

Variables are not like modules or other INSTEON devices for which we can add support. Triggers are like the brain for ISY and, as such, what we have to do is like a brain surgery. We are completely aware how important this feature is and all I can say is that it will shall be done. We just have to schedule such that it will have the least amount of impact and ensure that migration is considered thoroughly.

 

I am really sorry I cannot give you more information as far as timelines.

 

With kind regards,

Michel

 

I have no choice but to ignore your comments about the release cycles simply because you are not privy to what is actually being done internally. Furthermore, having 100s of beta releases with minor changes is a support nightmare for us.

 

I would never suggest "100s" or even tens of beta releases (between official releases) nor am I implying criticism here (sorry you took it this way). We are privy to what is targeted for the next beta release and those changes are scheduled to take roughly 4 months from the last beta release. If the changes defined in 2.7.7 take this amount of time and variable support is considered a major change and there is no estimate on when variable support might be implemented then it is difficult to imaging when this feature might be delivered. That was my point IRT releases. I wish it wasn't left up to me to calculate when we might see such a feature but without a roadmap or a statement that includes a possible target date, there is nothing else to go on. This is an enhancement that is important enough that I cannot help but try to determine when it might become a reality.