-
AuthorPosts
-
Anonymous
InactiveJuly 21, 2009 at 12:56 pmPost count: 131I have upgraded to 2.03 using the Discovery tool and it seems to have worked without any problems. I decided to add all of my devices again since I am only using X10 devices (20 or so) and have limited number of Macros.
The upgrade appeared to go well and I was able to access the HTML screen to do the work. I then went to the Flash interface (I like many of the new features) and was able to get that working well.
PROBLEM #1:
I then started testing the X10 devices, no commands work. No ON or OFF or DIM. Am I missing anything on this?PROBLEM #2:
In the Flash interface I noticed that the timezone information was wrong. I tried to find the settings/configuration page but found that there was not one in the Flash interface. So I went to go and fix it in the HTML interface and now I can not log on. I am using the same userid/password as before and the same credentials work in the Flash interface but I can not get into the HTML interface any more.What I have tried:
I have rebooted (via Discovery tool) the device a few times. I have closed all browsers and tried it again fresh.Any thoughts? Thanks in advance.
SteveInactiveJuly 21, 2009 at 5:38 pmPost count: 1001Did you load the 02.03 image after Sunday night.
Can you post one of the Actions that does not trigger from an X10 command, either a screen capture of the Condition and Actions screens or the information you have entered into each field.
Try unplugging the EZSrve for 30 seconds. Watch the yellow and green LEDs at the Ethernet jack and let me know what they do. There is an expected pattern where both will be On after a few seconds of applying power, then the yellow will go out for a few seconds and when the yellow LED comes on again the green LED will flash several times as the router information is obtained and perhaps the date/time information.
If you installed 02.03 after Sunday night, the default values for time settings are Manual and Local. It is necessary to set the appropriate time zone and probably the NTP option through the HTML interface. I don’t think the Beta Flex client has implemented the time configuration yet.
InactiveJuly 21, 2009 at 6:23 pmPost count: 131@grif091 wrote:
Did you load the 02.03 image after Sunday night.
Can you post one of the Actions that does not trigger from an X10 command, either a screen capture of the Condition and Actions screens or the information you have entered into each field.I’m sorry, I may not have been clear on that part. It is not the Actions that are causing the problem. No X10 transmissions are occurring at all. If I go to the main page and click ON for any X10 device nothing happens. In 1.6, a second after pushing the button the X10 “CLICK!!!!” would be heard and the light would go on. Now, nothing 😥
In terms of unplugging and starting it up again, I unplugged it and the light sequence was exactly what you said. Amber for a few seconds, then green flash, then Amber solid until I hit it with a web browser. However, I am still unable to log into it via the HTML interface (to set the timezone). I can log into the Flash interface but not the HTML one.
Any ideas? Thanks,
SteveInactiveJuly 21, 2009 at 7:01 pmPost count: 27Just a suggestion based on my personal experience:
Try logging in with the default username/password.
I had issues when trying the Flash interface where the password to log into the Flash was the default while the web interface was my personal.
My experience was with 2.01/2.02.
Good Luck.
InactiveJuly 21, 2009 at 7:07 pmPost count: 131Good suggestion. I have tried that and it didn’t work either.
InactiveJuly 21, 2009 at 7:13 pmPost count: 1001The login process through the Flex client is boiler plate. The password in EZSrve could be anything, including something other than the default, and the Flex client would access EZSrve anyway.
I just tested the Flex client, clicking an X10 device ON and OFF and the appropriate X10 messages are being generated. I have an X10 signal analyzer which displays the X10 messages. In addition I have two Actions which are being triggered by the X10 ON. This certainly does not mean you don’t have a problem. Only that the basic X10 function through the Flex client is working this afternoon.
I am concerned that the Beta Flex client may have done something that has lead to your results. After you uploaded 02.03 you were able to login to the HTML interface and add your X10 devices. Then you ran the Flex client and after that you have not been able to login to the HTML interface. Is that an accurate description of the sequence of events? When you enter the IP address of EZSrve into the browser to go to the HTML do you get the login popup requesting the name/password of EZSrve. If so are any messages issued that name or password is invalid.
EDIT: what happens to the LEDs when you attempt to login to the HTMl?
InactiveJuly 21, 2009 at 7:22 pmPost count: 27Regarding X10:
After migrating to 2.0x, I also have not been able to get X10 commands to work with my EZServe…Prior to the upgrades, everything worked flawlessly with X10.
I installed a replacement (UDI ISY-99i-Pro) and all X10 commands work as defined so it’s not noise or signal issues with my devices.
Perhaps it’s a PLM/2.0x compatibility issue (my version is 63).
I realize tha Grif may not have issues with his EZServe, but I have not been able to make 2.0x work.
InactiveJuly 21, 2009 at 7:56 pmPost count: 131@grif091 wrote:
I am concerned that the Beta Flex client may have done something that has lead to your results. After you uploaded 02.03 you were able to login to the HTML interface and add your X10 devices. Then you ran the Flex client and after that you have not been able to login to the HTML interface. Is that an accurate description of the sequence of events? When you enter the IP address of EZSrve into the browser to go to the HTML do you get the login popup requesting the name/password of EZSrve. If so are any messages issued that name or password is invalid.
EDIT: what happens to the LEDs when you attempt to login to the HTMl?
1. Yes, that is accurate description of the sequence of events.
2. Yes, when I enter the IP address in the browser I get an “Authentication Required” screen that states: “The server 10.0.1.8 at NA-HTTP AWS Realm requires a username and password.” I have tried the default EZServe/Simplehomenet and my normal password, same results.
3. I don’t know. My computer and the device are pretty far apart (downstairs). It would be hard for me to tell you exactly what is happening at that moment.Thanks,
SteveInactiveJuly 21, 2009 at 7:58 pmPost count: 1001Gene, I did not realize you had tried 02.03. I thought your problems were getting the earlier images to run rather than not being able to use X10. Could be a PLM level but I would have thought 1.60 would have had the same problem since it is the same hardware.
InactiveJuly 21, 2009 at 8:07 pmPost count: 131FYI… I am on version 63 as well (according to Flash interface).
InactiveJuly 21, 2009 at 8:14 pmPost count: 1001Does the 1.1 Discovery tool show EZSrve and at 02.03? I’ll do some research and testing to see if there is away to set the password through the XML interface. Do you have the SHN Utility installed and if so can you connect to the EZSrve. The 1.81 level of the Utility cannot do functional things to Insteon devices but you should be able to “Connect”. The XML can be issued through the Control tab which may give an option to set the password to something known. The Utility lower left message will still say Not Connected as that message is overlaid with the level of the EZSrve which has a different format in V2 but the lower right message should say Connected to EZBridge.
InactiveJuly 21, 2009 at 8:15 pmPost count: 27Grif, your are correct, my problems were with 2.01 and 2.02.
InactiveJuly 21, 2009 at 8:16 pmPost count: 55newmans_99:
I ran into a similar scenario (EZServe does not recognize default username/password) at least twice during my EZSrve 2.0X adventures over the past few weeks. If I remember correctly I had to use both the TFTP solution (make sure you turn off Windows firewall) to reimage the firmware AND a hard reset to restore the FLASH defaults after that, but you might try a hard reset (i.e. paperclip in the reset hole on the EZSrve) first as my guess is username/password information is stored in the FLASH memory.
With regard to X10 devices, I have been able to make X10 devices work in both directions using the 2.03 firmware (i.e. as a device trigger in a condition and as a responder in an effect). The important thing is to use the X10 hex codes for device status in the status fields (i.e. 0x02 for on, 0x03 for off, etc.)
I haven’t tried turning an X10 device on/off directly through the HTML interface but will do that when I get home tonight.
InactiveJuly 21, 2009 at 8:27 pmPost count: 131Yes, the Discovery and Upgrade tool v1.1 does show 2.03.
I do not have the SHN Utlity installed, but I will get it done now so when you find the commands I can get them executed.
InactiveJuly 21, 2009 at 8:30 pmPost count: 1001Issue the following command through the Control tab of the SHN Utility. I used 1.81 to do this.
The expected results are
I changed the password to simplehomenet (lower case s) and confirmed that I had to use a lower case s to login. Changed it back to S and then did login with default password. If more than the password was damaged then Stuarts suggestion about reset may be the only option.
-
AuthorPosts
- You must be logged in to reply to this topic.