Michel Kohanim

@simplextech, It seems that those apps are not including the uom. The solution in UDAjax was to always pass the uom (4 or 17). Any app that will use rest commands to change setpoints without specifying the uom will see this behavior, which currently includes HAD, Agave and eKeypad. With kind regards, Michel

@sperok, Unfortunately drag/drop will not work on OSX. With kind regards, Michel

@dsstrainer, 1. You should NOT use the button grouping 2. I suspect a step was missed here: Medium Scene Select the Medium Scene in the network tree Using the sliders in the panel, set the levels for each button and the FL - Motor for this scene Medium Button – 100 Fanlinc - Med All other buttons – 0 Select the Scene Controller button in the Medium scene. This entry will be red. Click on Copy Scene Attributes from Medium With kind regards, Michel

@dsstrainer, I was never good in anthropology so I missed it . Your first assumption is false. The beauty of ISY is that it creates all these manual links for you so that a) you don't have to do it and b) ISY will know the status of things. If you remove ISY, you KPL and FanLinc will continue to work as is. In short - let me see if I can give you an anthropomorphic analogy - ISY is not like a traffic cop directing traffic. With kind regards, Michel

@dsstrainer, I am glad it worked but, as @mwester eloquently described, when PLM is involved, things are different. Furthermore, I am worried that - in the future - if you decide to do something with status of devices, nothing is going to work and then we'll be back to your philosophical analogies. As such, may I humbly suggest you follow the instructions here? With kind regards, Michel

Hi @johnnyt, Currently, no. But since you have 5.0.x, you can use the brilliant node servers for weather in which case, you can assign values to variables (they are nodes not modules). With kind regards, Michel

Hi Orest, The highlighted program is disabled. With kind regards, Michel

@johnnyt, You firmware and UI are correct. Please upgrade to 5.0.15A and, if you still problems (you need to save), please send your backup to support@universal-devices.com. With kind regards, Michel

@johnnyt, Usually there are two cases: 1. You are not using the correct UI. You need to make sure you are using the ISY Launcher 2. If there are errors, you will see the issue in the comment section You can save one at a time. There are no CLIs. With kind regards, Michel

@johnnyt, It will not crash but you will lose your Z-Wave menu. With kind regards, Michel

@starmanj, I do not think MobiLinc is trying to compete and, regardless, competition is good for the customer! There's also Agave. With kind regards, Michel

@rlanza1054, Only the Z-Wave enabled units come with 5.0.x firmware. With kind regards, Michel

@johnnyt, You always have 30 days money back guarantee so you can return it. Alternatively, the following is pretty safe: 1. Take a Z-Wave | Tools | Backup | Full 2. Take an ISY backup (File | Backup ISY) 3. Replace 300 series with 500 series 4. Reboot with a different SD Card (just to be 100000% safe that you an get back) 5. Install 5.0.15A 6. Restore the backup from 2 (all your Z-Wave nodes will disappear) 7. Z-Wave | Tools | Restore | All … this will take Z-Wave nodes from the 300 and restores it into 500 If all fails, then: i. Factory reset ii. Install 4.7.3 iii. Either replace the SD Card with the original or restore your backup from 2 above With kind regards, Michel

@johnnyt, Unfortunately you cannot. 500 series is filled with things that we could not put in 4.7.x without breaking everything. With kind regards, Michel

@johnnyt, Just to be clear, no difference between ISY with Z-Wave out of the box and adding it yourself. Please note that ONLY the ZW series come with 5.0.x firmware. With kind regards, Michel

Hi Orest, The most important features are: 1. Support for node servers: https://forum.universal-devices.com/forum/131-polyglot-node-servers/ 2. Support for device variables. i.e. store the state of a device into a variable and back The rest are outlined in each release. With kind regards, Michel

@oskrypuch, 1. This is not going to work (change it to Or): Time is 12:00:00AM And Time is 6:00:00AM And Time is 12:00:00PM And Time is 6:00:00PM 2. As @larryllix mentioned, all those notifications for specific temps should be changed to variables 3. Way too many programs calling other programs (very difficult to debug) With kind regards, Michel

@mdecou, I sent a link to this post to MobiLinc support. With kind regards, Michel

@oskrypuch, I definitely think it has to do with your thermostat programs. With kind regards, Michel

@BigMoose, Yes of course. Here's the full instruction: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:Migrating_To_Your_ISY-994i With kind regards, Michel

@oskrypuch, That's what I was worried about. ISY hardware failure rate (at 5 years) is still less than 0.01%. And, the majority of that is the SD Card. I would go back and look at programs that might be in an infinite loop. With kind regards, Michel

@mitch236, If your ISY is Z-Wave enabled, these are pretty good. Also, there are many others on Amazon. With kind regards, Michel

Hi @oskrypuch, Thanks so very much for the update and I am so very sorry you had to go through this exercise. With kind regards, Michel

@oskrypuch, Isn't the new ISY rebooting? With kind regards, Michel

Hi Orest, Thank you. Based on your logs, I think you have runaway programs (perhaps seasonal). If you can reboot with the PLM and disable all your programs, then I think you can resolve this by figuring out which programs are doing this: thermostats / MAIN - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:58:06 PM Program Log thermostats / MAIN - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:58:07 PM Program Log thermostats / MAIN - tstat - 2.2 - Heat Setpoint 21° Sat 2019/04/20 07:58:08 PM Program Log thermostats / Master - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:58:08 PM Program Log thermostats / Master - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:58:09 PM Program Log thermostats / Master - tstat - 2.2 - Heat Setpoint 21° Sat 2019/04/20 07:58:10 PM Program Log thermostats / UpStrs - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:58:11 PM Program Log thermostats / UpStrs - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:58:12 PM Program Log thermostats / UpStrs - tstat - 2.2 - Heat Setpoint 20° Sat 2019/04/20 07:58:12 PM Program Log thermostats / SLRM - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:58:13 PM Program Log thermostats / SLRM - tstat - 2.2 - Cool Setpoint 24° Sat 2019/04/20 07:58:14 PM Program Log thermostats / SLRM - tstat - 2.2 - Heat Setpoint 21° Sat 2019 then again ... thermostats / MAIN - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:59:20 PM Program Log thermostats / MAIN - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:59:21 PM Program Log thermostats / MAIN - tstat - 2.2 - Heat Setpoint 21° Sat 2019/04/20 07:59:21 PM Program Log thermostats / Master - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:59:22 PM Program Log thermostats / Master - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:59:23 PM Program Log thermostats / Master - tstat - 2.2 - Heat Setpoint 21° Sat 2019/04/20 07:59:24 PM Program Log thermostats / UpStrs - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:59:25 PM Program Log thermostats / UpStrs - tstat - 2.2 - Cool Setpoint 22° Sat 2019/04/20 07:59:25 PM Program Log thermostats / UpStrs - tstat - 2.2 - Heat Setpoint 20° Sat 2019/04/20 07:59:26 PM Program Log thermostats / SLRM - tstat - 2.2 - Thermostat Mode Auto Sat 2019/04/20 07:59:27 PM Program Log thermostats / SLRM - tstat - 2.2 - Cool Setpoint 24° Sat 2019/04/20 07:59:28 PM Program Log thermostats / SLRM - tstat - 2.2 - Heat Setpoint 21° Sat 2019/04/20 07:59:29 PM Program Log As you can see, a program keeps setting the set points to the same things; repeatedly and in succession. Something is wrong. With kind regards, Michel