AnonymousInactiveMay 18, 2008 at 12:10 amPost count: 10
After loading ver 1.50 and installing 30 devices I encountered a problem. Is anyone experiencing an extremely slow response once the macro screen is picked? At first I thought it was frozen and after reloading the firmware twice I just waited, and waited, and waited. After about two minutes the macro screen appeared. Is it my system or are others having this issue?AnonymousInactiveMay 18, 2008 at 3:21 amPost count: 408
We will check this out immediately.
PaulAnonymousInactiveMay 27, 2008 at 12:02 amPost count: 10
Paul, I wonder if you’ve been able to verify my problem. Since my original inquiry the issues have worsened. After reloading version 1.5 onto my EZSrve I noticed that the macro screen still loaded ever-so-slowly and that I could not install any macros, even if I waited. All the other screens load just fine and the device installations and timers work as expected. I’ve restarted, reset, and reloaded numerous times since but without any luck. To test the system after a reload I first install an INSTEON wall switch which is also configured to send an X10 signal M01. I then install an X10 device configured as M01 to use as a macro trigger. I then try to install a macro that on receipt of an X10 M01 ON signal it sends an OFF command to the INSTEON device after a 1 minute delay. This worked well in version 1.43 but I have yet to get any macro to work in v 1.5 by installing it from the browser screen. After a reset the xml macro files were empty as expected. After numerous attempts to create a macro the xml file still remains empty. Could it be the EZSrve? Any thing you would recommend?AnonymousInactiveMay 29, 2008 at 2:19 pmPost count: 408
This bug will be fixed in version 1.51. Since you are having so much trouble, feel free to email me directly and we can work on having you as a Beta tester for 1.51 to ensure that resolves your problems.
I am sorry for the hassle and the time you have spent on this.AnonymousInactiveJune 29, 2008 at 11:40 amPost count: 10
I think this issue can be closed out. 1.52 clears the issue. Many thank to Simplehomenet.
- You must be logged in to reply to this topic.