AnonymousInactiveJune 29, 2009 at 1:18 amPost count: 29
A glutton for punishment, I decided to upgrade to version 2.0. I can add devices fine, and EZSrve is able to retrieve the devices’ links and display them correctly. I can also turn devices on and off, using both the web interface and the new xml commands.
But, EZSrve seems to be unable to obtain the status for any devices. On the Device View/Control web page, it shows all devices as “off”, even after I use the very same screen to successfully turn them on. Also, when I use an xml SendInsteon command to query a devices status, I get back
. This happens for all devices I try. Below is the command I’m using. (The device being polled is a lamplinc.)
Is it possible the PLM attached to my EZSrve needs upgrading? It’s running firmware version 52.AnonymousInactiveJune 29, 2009 at 3:07 amPost count: 256
Mark, it sounds like a missing or faulty “DevClusters.xml”. This is the “methods” file that EZSrve uses to know what to do about the various device types.
Please use the just posted Java applet to reupgrade your EZSrve. This loads the DevClusters file in addition to the main firmware. If you get error after that, then you’ll need to clean the Devices.xml file.
V52 of the PLM was OK, but there were some issues with concurrent X10 and Insteon messaging. If you wish it reflashed, you’d have to wait until the next batch of reflashing is scheduled with Smarthome (about 3-4 weeks from now as we just did one) We are currently getting V85 from Smarthome.AnonymousInactiveJune 29, 2009 at 2:30 pmPost count: 1001
Mark, if you are running with the correct DevClusters xml file, the Device View/Control not showing device status may be separate from the results you see when you Query a device with SendInsteon. If you have IE available try that browser. If you have IE and it is version 8, set the Compatibility View option before running EZSrve. My Device View/Control display shows the correct device status on IE 8 even though I also see the Status=Failure you are seeing when I issue a SendInsteon Query with xml. The SendInsteon Query works on an ICON Switch but fails with an ApplicanceLinc and a LampLinc. Both of those devices are responder only devices which may explain why the Query does not post as successful even though the actual Query command is issued with a good response from the device.AnonymousInactiveJune 29, 2009 at 2:49 pmPost count: 29
It looks like my DevClusters.xml is busted. I used the xml Read command to try to read the file, and got this:
I was able to read other files fine.
So, I’ll try re-upgrading the EZSrve. I used the discover.jar app to do my first upgrade to 2.0. I figured I’d download the latest copy of the jar file before trying again, but right now the web server is reporting 404 Not Found when I try to get it from the downloads page. Not sure what’s up with that.AnonymousInactiveJune 29, 2009 at 3:05 pmPost count: 1001
The old version of Discovery did not upload the DevClusters file. Until the link to the V2 Discovery tool is fixed, you can download the V2 package .zip file from the Downloads section, unzip the package and then upload the DevClusters.xml file using the EZSrve Server Administration screen. I sent a note to Simplehome early this morning (EDT) about the broken link.AnonymousInactiveJune 30, 2009 at 12:45 pmPost count: 29
Hmm. The discovery.jar file still isn’t available. So I tried uploading DevClusters.xml using the web UI admin Upload function. It appeared to work, in that no errors were reported. I also restarted the EZSrve. But, the List Files button still doesn’t show the file, and the EZSrve still doesn’t report device status, either on the web UI or via xml commands. Also, attempting to read the file via the xml interface still yields an error. So, I’m guessing that the upload function didn’t work.AnonymousInactiveJune 30, 2009 at 12:56 pmPost count: 69
Just a possibility, but I’ve not been able to upload with Firefox. I still had to use IE.AnonymousInactiveJune 30, 2009 at 1:37 pmPost count: 1001
I don’t think uploads are working under FireFox. That has been a problem with FireFox even under V1. Just below the RESET button you should see a message saying “Upload in progress” when you click on the UPLOAD FILE button. After the upload completes the following message “File upload successfull. Please restart to see the changes once you complete all the uploads” is displayed just below the screen title Server Configuration. I don’t think you are seeing those messages and I don’t think the upload is working. You will have to use IE to do the uploads or the V2 Java Discover tool (link has been fixed).AnonymousInactiveJune 30, 2009 at 2:07 pmPost count: 29
I was able to use IE to upload DevClusters.xml. But, somewhat amusingly, the List Files command doesn’t seem to work in IE 8. All I got was a blank screen. It does work in firefox, and shows that DevClusters is indeed present. I was also able to use the xml interface to download the file. Finally, I restarted the device.
BUT, EZSrve still does not report device status. For example, I am able to use the web UI to turn a lamp on and off, but the UI always shows the lamp as off. (I tried it with both IE and firefox.) Also, the xml interface is still reporting errors when I try to query a device status:
Is it possible that it’s not working because I added devices when DevClusters was not present? Do I need to delete all devices and start over?AnonymousInactiveJune 30, 2009 at 2:38 pmPost count: 1001
It is possible that the devices are not correct if the DevClusters.xml file was not correct at the time the devices were added. It is the DevClusters file that provides the correct model for the device characteristics. If the DevClusters file was not correct I would delete and add one or two devices and see if that resolves the GUI not showing correct device status for those devices. You might try clicking on the Refresh button before doing that to see if the status is known, just not being displayed.
However, even though my GUI display is showing the correct device status after an On, I see the same thing here you are seeing with a SendInsteon xml command and my DevClusters.xml file is correct and was when my devices were added. The SendInsteon command to an ICON Switch works, but to an ApplicanceLinc and a LampLinc it fails. Both the ApplicanceLinc and the LampLinc are responder only devices which may explain why they fail and the ICON Switch works. The Query command is actually being issued and ACKed but incorrectly posted as failed in the xml response. I sent a note to Simplehome yesterday documenting what we both are seeing regarding the SendInsteon xml command. I was able to get the LIST FILES on IE8 to work by setting the Compatibility View option for all applications.AnonymousInactiveJune 30, 2009 at 3:06 pmPost count: 29
Deleting a device and re-adding it seems to get the web UI to report its status. The device I tried is a lamplinc.
Interestingly, immediately after I re-added it, I tried polling it with xml and got a valid status response back. But, when I tried it a second (and third) time, I got the “did not respond” error.AnonymousInactiveJune 30, 2009 at 4:44 pmPost count: 1001
Mark, glad to hear GUI is now working. That was the DevcClusters not being there or at the wrong level. Simplehome looked at the DevClusters for the SendInsteon problem, DevClusters is okay but suggested trying the device ID= in upper case and that corrected the problem here. Give it a try on your system. The actual command being issued on the powerline has the ID in upper case regardless of the case on the SendInsteon xml and the device does ACK the Query, even when the xml response says Failure. Must be something in EZSrve that is not capping ID before checking something. Let us know if capping the ID= value works for you.
*** COMMAND ***
*** COMMAND ***
*** COMMAND ***
*** COMMAND ***AnonymousInactiveJune 30, 2009 at 5:03 pmPost count: 29
Thanks! Sending the ID in upper case does indeed fix the problem. Even works with a lamplinc.AnonymousInactiveJuly 1, 2009 at 9:58 pmPost count: 29
Lest y’all think I do nothing but complain, I just wanted to report that everything is working well with the 2.0 xml interface — monitoring and controlling keypladincs and other devices.
- You must be logged in to reply to this topic.