The EZSrve won’t let me override the OTHER device type.

Tried that. Once it finishes the installation it sets the type to OTHER no matter what I set the type to be.

1) I stepped back to the v1.56 EZSrve f/w. I didn’t like the way the timers are done on 2.6. However when I upgraded I don’t believe the tool upgraded me to 2.6 but I might be mistaken on that.
2) I am using the HTML interface
3) No other warnings, popups, etc. when I’m performing this operation

–Don

OK so I guess I need to upgrade. When I upgraded and then downgraded again over the weekend I was not able to save and reload the timers, macros and devices. This was true going from 1.56 to 2.x but was also true when I downgraded back to 1.56. Here is what I did:

1) Saved the xml files from 1.56 from inside the HTML interface on the EZSrve
2) Upgraded
3) Tried to reload the xml files using IE which was unbelievably slow and after hours of trying still did not work
4) Downgraded the EZSrve firmware back to 1.56
5) Tried to reload the xml files from IE which still didn’t work. No errors, etc., just no data loaded
6) Manually rebuilt the whole system (more hours)

I also used the Discovery utility to try to reload the files but that also didn’t work. Same problem, executed OK with no errors or response but nothing was loaded. Is there a trick or process that needs to be followed? Will xml files from 1.56 work on 2.6?

OK so I upgraded my EZSrve firmware last night. Numerous issues:

1) I used the upgrade utility to upgrade and I selected it to install 2.06.16. On the utility it is listed as a “Beta”; is it a Beta?
2) The EZServe identifies it’s firmware as 2.06.10, PLM version 63
3) The Icon dimmer still installs as device type OTHER (sigh …)
4) The Location Configuration does not respond to just a zip code, or a city, I had to load the latitude and longitude manually
5) If you don’t set the Date and Time to use an NTP then it doesn’t keep the correct time (it is off by hours)
6) I have an Action (ID=0) that I used for testing but now will not delete (other Actions delete OK)
7) If I have 2 Effects, each separated by 3 minutes, the first Effect works fine but the second effect only lasts a matter of seconds

So in general I’m not happy. This has been a lot of work and I still don’t have a functioning Icon dimmer. On a positive note, once I figured out how the Conditions/Actions stuff worked it is pretty cool.

Suggestions on any/all of these points?

–Don

1. OK
2. OK
3. I didn’t specify a device type, I let the system decide by querying the dimmer
4. OK, but a pain
5. I didn’t realize that I had not set NTP last night when I upgraded. That was at around midnight. This morning when I was looking to see why all the overnight timers had failed I looked at the time to see if it was set correctly. That was at 7:30 AM but the EZSrve thought it was 8:41 PM. I set NTP and now it seems to be running fine.
6. The test Action does not display correctly. If I select the test Action (named “Office”) the Action is Disabled without a condition checked and the Condition is empty. The Action screen shows Attribute= “Select Attribute” and Value=”undefined” for Effect 1. However the XML looks like this:

–
–

–

7. I set up a test Action that had 3 effects: turn light on to 0xFF; turn light on to 0x9A with 3 minute delay; turn light off (0x00) with 3 minute delay. What happened was the light turned ON at the correct time (set by the Condition); 3 minutes later the light turned to 0x9A brightness for just a few seconds and then turned off.

–Don