AnonymousJuly 21, 2009 at 8:40 pmPost count: 131
WOW Thanks! Issue #1 done. the password is reset and I was able to get into the HTML interface.
I see all of my devices and have set the timezone information to NTP, EST, and Daylight Savings. I also set my location information.
Now, what do you think that I need to do about the X10 issues?
As an FYI… Here is what my Devices look like in my devices.xml (now that I can see them). Anything look wrong?AnonymousJuly 21, 2009 at 8:50 pmPost count: 131
Well scratch that. From the HTML side I can turn devices ON / OFF.
Let me try using the Flash next.AnonymousJuly 21, 2009 at 8:52 pmPost count: 1001
Try issuing this command through the same Control tab. I also did this with the 1.81 code. You can of course change the House and Unit code to whatever you need them to be.
Expected responseAnonymousJuly 21, 2009 at 9:06 pmPost count: 131
This is frustrating… Now I can not get into the Flash interface. I exited all of my browsers and went to the compacta.org site with my server name and now it states “Server Is not Responding.. Please try again Later!”. The HTML interface is working fine and even after getting this message in the Flash interface I am able to enter the HTML interface without problems.
SteveAnonymousJuly 21, 2009 at 9:14 pmPost count: 1001
I just tried the compacta server and I get to my EZSrve. I think that message is saying it cannot get to your EZSrve. See if you can use the Discovery tool to discover and show the current image level of your EZSrve. I think I asked this before but don’t remember the answer, when did you get the 02.03 image (the day). It is important as there is more than one 02.03 image.AnonymousJuly 21, 2009 at 9:19 pmPost count: 131
I got the 2.03 image yesterday.
I can’t get the discovery tool to find it. Interesting that my broswer can hit the server (HTML interface) without trouble.AnonymousJuly 21, 2009 at 9:37 pmPost count: 1001
The 02.03 image available on Monday morning is the latest image. The HTML interface does not use the same access as the Flex client, Discovery tool, SHN Utility, etc. I expect the Discovery tool shows the IP address because the HTML interface is working but not the version of the image because the XML interface is not. Try doing a Restart (not RESET) and see if that gets the Discovery tool showing the image level.AnonymousJuly 21, 2009 at 9:56 pmPost count: 131
I was not able to attach via Discovery so I simply unplugged it and plugged it back in.
Now I can access Flash interface and the HTML interface.
Now, back to the X10 issue from the Flash interface. I can now control all X10 devices from the HTML interface without problem. Matter of fact, when I select ON or OFF from the HTML interface the Flash interface changes (COOL!).
The problem that I am left with is that when I try to turn a device ON or OFF from Flash, I get the little clock spinning and nothing happens. The Flash interface changes (light turns on) but no “CLICK” from the physical X10 device.
Any thoughts on this? Thanks.AnonymousJuly 21, 2009 at 10:19 pmPost count: 1001
When V2 changes the status of a device it sends a response XML to the application connected using the XML interface (Flex client in this case) that the device status has changed. That is why you see the Flex client display change when you change the device status through the HTML.
The rotating clock normally means a response has not yet been received. The fact that the actual X10 device does not respond (no click heard at device) tells me the X10 command did not get executed for some unknown reason at this point. There is an earlier post that has a SendX10 for an X10 device. Try issuing that through the SHN Utility, just like you did the SetPassword command. That is the same command the Flex client is using to control an X10 device (I think).
I have this nagging concern that something happened to the image/flash memory that not only corrupted the password but may have done other damage. You can reload the 02.03 image with the Discovery tool but it may require a Reset with the paper clip on the internal Reset button to completely clear the flash and that will also erase your configuration. Let’s see what the XML SendX10 through the Utility Control tab tells us first.AnonymousJuly 22, 2009 at 1:19 amPost count: 131
I was able to execute the Command through SHN Utility without any problems (device turned ON/OFF appropriately). I assumed that would be the case since it works 100% when going through the HTML interface.
Since the device works correctly (HTML interface) I would assume it has something to do with the Flash interface to the device. Anyway to test this?
SteveAnonymousJuly 22, 2009 at 1:36 amPost count: 1001
I’ll look into it and see what I can come up with. There is no secret internal interface between the Flex client and V2 EZSrve. The XML interface that is documented in the two downloadable pdf files is what the Flex client has to work with. I was not expecting the XML command to work when issued through the SHN Utility as that is the same command I believe the Flex client is using. What browser and at what level are you using when running the Flex client? I am running IE 8 with Compatibility View mode ON for all applications. Don’t know if that makes any difference.
At least we know the PLM revision 63 does work with X10. Now I think we have to determine why the Flex client is either not issuing that SendX10 XML command or not issuing the correct command. This may take a day or two to figure out how to trace the interface between the Flex client and EZSrve.
Thanks for all your help thus far.AnonymousJuly 22, 2009 at 1:47 amPost count: 131
I have tested on the following browsers:
IE6.0.2, Chrome2.0.172, Firefox3.5, and Safari4.0.2 – all on Windows XP
All of the exhibit the same behavior.
Thanks for all of your help and patience in working with me. Please let me know if you need anything else tested.
SteveAnonymousJuly 22, 2009 at 2:05 amPost count: 1001
Thanks for the offer to help. There is one thing that I think should not be possible at 02.03 but can you make sure you have a DevClusters.xml on the EZSrve. The 02.01 image was changed to automatically download that xml file so I think it is not possible for that file not to exist on EZSrve anymore but it is worth checking. There were some symptoms that surfaced early related to Insteon devices not being correctly interfaced with because devices were added to ESrve without the DevClusters file being there. The device characteristics are taken from the DevClusters file when a device is added. This is one of those Zebra ideas.AnonymousJuly 22, 2009 at 2:26 amPost count: 55
It isn’t clear from this thread whether you suspect that the Flex client isn’t sending X10 commands appropriately or whether you suspect something specific with Steve’s setup.
I can verify that the Flex client works with X10 devices in my setup (I also have PLM revision 63) using IE8 in compatibility mode. On/Off/Bright/Dim all work.
It looks like the Flex client uses Adobe Flash. My IE reports version 10,0,22,87. The one thought I had was to make sure the Flash version is up to date.
StuartAnonymousJuly 22, 2009 at 2:56 amPost count: 1001
Stuart, the Flex client does use Adobe Flash. Great idea to know the Flash level. On my IE8 the Flash level is 10.0.22.87. On my FIreFox 3.0.8 which also controls the X10 device correctly, the Flash level is 10.0.12.36. I was originally thinking the problem was going to be in EZSrve image or flash memory, related to whatever corrupted the password. When the SendX10 XML command worked through the Utility my thinking changed to something back in the browser which as you so correctly pointed out, there is a dependency on the Adobe Flash level as well. The IE6 is so far back that it would not surprise me for that not to work but FireFox 3.5 seems very current. The DevClusters file not being there could also cause this but I don’t see how that could be missing at 02.03.
Steve, do a right click on the background of the Flex client screen and it should have an option to display the level of the Adobe Flash.
- You must be logged in to reply to this topic.