AnonymousApril 18, 2009 at 4:02 pmPost count: 256
Thank you all for your patience. The much awaited 2.0 is here for those that do not want to wait for the official release. The expected differences between this build and the final release are:
– Auto-polling of devices: the final release will allow a user-settable parameter for a polling interval of a device status attribute. When the device status is detected to have changed, a “ClusterChanged” report is issued through the socket interface reporting the new value to the client. This is useful for devices such as the thermostat adapter which do not generate events upon changes. This feature will not be noticeable when using the html web interface, but will be a must for the graphical Flash GUI.
– Documentation! updated user manual, quick-guide, release notes, API and API examples..
– Bug fixes: anything you bring to our attention during this period. Your feedback will be very appreciated to make this a solid release. There are many changes we made to the engine and we expect your contribution to be enormous! Please post your comments here, good or bad.
Please also note that the changes made to the server made it impossible to maintain database compatibility. Therefore, it will be necessary to re-install devices, areas, scenes, etc.
AS FOR THE FLASH INTERFACE, WE HAVE FINISHED THE SKINNING PROCESS AND WILL RELEASE IT AS A BETA WITH 3-5 THEMES WITHIN A FEW DAYS..AnonymousApril 20, 2009 at 12:19 amPost count: 69
Thanks for posting the Beta, it’ll be a good excuse for me to mess around with my system…
Quick observations so far:
– Screens seem to open much faster now.
– On the Server Configuration screen, “Browse Files” just shows up as “t”.
– I uploaded the DevClusters file, but I don’t see it when I browse files. Should I?
– I tried to set an EZFlora program, but I don’t think hitting “Write” saved it. When I later “Get Data”, the values are all 0’s — not what I entered.
– The EZIO8T is there now (yay!), but the configure button doesn’t do anything, nor does the “More” button from the Device Control screen.
– When creating a new area, I had to save the empty area before adding anything to it. Not a huge deal, just a little weird.
– Can’t add an EZUIRT.
I’ll post more as I play around… My biggest complaint so far is the EZFlora programming — I used to always just do it in the SHN Utility, but that’s not compatible with 2.0 now…
-DaveAnonymousApril 20, 2009 at 1:06 amPost count: 1001
The DevCluster should be in the list of files. Did you Restart after uploading the DevCluster.xml file? Also, was the upload successful message displayed after the DevCluster upload. I think there are still some issues with the directory structures that can be uploaded from. The comment about the Browse button, when you click on Browse where is the “t” displayed? I think the Browse button invokes the standard Microsoft browse dialog. I suspect the HTML interface access to the EZFlora configuration is not active on V2 at this point. For the same reason the SHN Utility is not supported yet. Not absolutely sure about this. The new Adobe Flash graphical interface should have all the configuration support when it comes online.
Having to Save a new Area name before devices can be added is the same way V1 works. What do you get when you try to add the EZUIRT?
EDIT: I see the issue with the EZUIRT, it is not listed as one of the supported devices. Good catch!
We will need input from Simplehome about the EZFlora configuration support from the HTML interface.AnonymousApril 20, 2009 at 3:17 amPost count: 69
Well then this could be part of my problem. I got no message at all after uploading the DevClusters file. It doesn’t even look like the Upload button does anything. I’ve restarted and tried uploading again many times, but I never see the file in the list. Oh, and I was wrong before: the “List Files” button had turned to a “t”, not the “Browse”. But, after a restart it’s back to normal. I almost took a screenshot for good measure, but got lazy. I’m going to downgrade so I can make an EZFlora change, but I’ll try playing around again after. Thanks, Grif.
-DaveAnonymousApril 20, 2009 at 3:54 amPost count: 69
Umm… I don’t recommend trying to downgrade right now… I think I just horked my EZServe. I did the reverse of the 2.0 upgrade: factory reset, followed by upload of the 1.60 image.bin. After that the EZServe does not respond to the browser, or even a ping. I notice now that the green led by the network port is a solid green — never blinking. I don’t think that’s a good sign. I’ve power cycled it a few times with no change. My router dhcp doesn’t show it, nor does the SHN auto-find find anything.
Any help is appreciated!AnonymousApril 20, 2009 at 7:39 amPost count: 1001
You should be seeing an upload successful message displayed just under the Server Configuration screen title. If that message is not displayed the file is not being uploaded, at least that has been my experience on V1 and V2. Put the xml file in a simpler directory structure, something like c:tempDevClusters.xml and upload again. What browser are you using? If not IE, try bring up EZSrve on IE and doing the upload, if you have that option. There have also been some issues with FireFox 3 but they surfaced back on V1. I just tried FireFox 3.0.3 and cannot upload from c:tempDevClusters.xml, something I have done hundreds of times under IE. Clicking the Upload File button on FireFox 3.0.3 gives the appearance that nothing is happening. Upgraded to FireFox 3.0.8 and still do not get successful upload message. Went back to IE to be sure EZSrve was still working, which it is. Realized that I do not even see the standard popup warning message about uploading invalid xml files. Looks like V2 Upload File is not working on FireFox 3.0.3 or 3.0.8.
The following is what should display under Server Configuration title when upload works.
File upload successfull. Please restart to see the changes once you complete all the uploadsAnonymousApril 20, 2009 at 8:05 amPost count: 1001
Oops. Sorry, I was sitting on your next to last post while trying the various Upload File tests and uploading a new FireFox so I did not see your last post until just now. I did successfully go back to a V1 image from a V2 image several months ago when the 1.60 image was being tested. There was a problem that I had pretty frequently on a test version of 1.60 that development could not recreate so I loaded up 1.60.x on my EZBridge setup I was using for V2 testing because it had a later version of the PLM than my EZSrve (which turned out to make no difference). Development was able to remotely connect to my EZBridge and find the issue running 1.60.x. Once that fix for 1.60 had been tested I reloaded a V2 image.
Sounds like there was a problem loading 1.60. Try unplugging the EZSrve for a few minutes and see what happens from a complete power up.AnonymousApril 20, 2009 at 1:35 pmPost count: 69
Well, the EZServe is still dead as far as I can tell. Even with no ethernet cable plugged in, the green status light stays solid. I tried the reset procedure in this post:
but I have not seen any change.
The white led on the side does blink with insteon traffic, though. I’ll try some more experiments after work today.
Oh, and I was using Firefox 3.08 before with the upload problem.
-DaveAnonymousApril 20, 2009 at 2:43 pmPost count: 256
Lee, thanks for the explanations on the browser issues with Firefox. We don’t know however, how the downgrading could have rendered the module useless, where the 1.6 image won’t boot. This is one test we did without problem.
Meanwhile, Dave, do you have a TFTP setup? Otherwise, give us a call when you can and we can help you set it up.
By the way, the most likely reason you could not configure the EZFlora was that the server did not have “DevClusters.xml” We did not remove that functionality.
AlAnonymousApril 20, 2009 at 3:14 pmPost count: 1001
Just to confirm, you followed the procedure Paul posted. Unplugging module, then after restoring power for 3-4 seconds, pressed the Reset button in the pin hole (not the Set button near the LED) for 15 seconds and after 3-4 minutes the EZServ still not enter DHCP mode and acquire an IP address from the router.
Will you be able to use IE to do the xml file upload after the EZSrve is back in working order?
There is procedure to load the EZSrve image using a TFTP server from SolarWinds (free download). I’ll have to go back through some old emais to see if I still have that information. During V1 testing long ago I got an image that was bad which also prevented the next image upload process from working to go to a good image. There is nothing wrong with either the Beta image or 1.60 but something may have happened during the 1.60 image upload. This process uses the upload capability built into the hardware processor. It requires setting the PC to a specific IP address that the processor was burned in to use and some other things I don’t immediately remember. After doing Paul’s reset procedure see if the router shows the EZSrve with an unfamiliar IP address.
EDIT: Just saw Simplehome post. The TFTP procedure is what I was referring to. Probably best to get that procedure from SHN. As I mentioned in the previous post I have gone from V2 back to V1 (1.60) and then back to V2 with no problem which suggests something happened during the 1.60 upload rather than the process cannot be done.
That is good news about the EZFlora support. Not having the DevClusters.xml file makes sense.AnonymousApril 22, 2009 at 10:28 pmPost count: 30
The Beta+ download link doesn’t work – I get a not found.AnonymousApril 23, 2009 at 12:09 amPost count: 1001
The beta+ image is being updated. Check back in a few hours.AnonymousApril 27, 2009 at 6:16 pmPost count: 20
Did you say a few hours or a few days? 🙂AnonymousApril 27, 2009 at 7:27 pmPost count: 1001
Sure does look like my guesstimate was more than a little off. The first Beta+ user’s results were so severe that I guess they are testing that area extensively before making the next Beta+ image available.AnonymousApril 28, 2009 at 12:28 amPost count: 20
Was attempting to be funny, not critical. Looks like I failed at both. Had downloaded the beta when It first appeared, but have not installed it yet, guessing that the beta was in fact a little too beta when it disappeared so quickly… Thanks for all the great posts. Seems like you are always here helping someone…
- You must be logged in to reply to this topic.