HOME › Forums › Input/Output › EZIOxx › simplehomenet utility will not change stored settings
-
AuthorPosts
-
Anonymous
August 5, 2007 at 10:31 pmPost count: 1#39751 |I can’t seem to get the new version of the EZIO utility program to successfully change the Output timer. Possibly I am not understanding the process correctly. I want the timer to allow the output to stay on only for 3 seconds, to open my entrance gate via Insteon control.
If I read the EZIO2x4 setting under the “Input and Output Configuration” panel, Output 1 is set for 255, and Output 2 is set for 30. I then change the settings to 3, and 3. I then click “write”. I then go to the “Configuration” panel, and select “set output timer in seconds”. I then click on “write”, and click the option to make all changes permanent.
However, if I immediately go back to the “Input and Output Configuration” panel and read the stored settings, it reads 255, and 30 again. I tried a factory reset prior to all the saves, with no benefit.
What am I missing?
Anonymous
August 8, 2007 at 2:55 amPost count: 408This has been confirmed. We will be having a release shortly next day or two, and will post a bug fix.
Thanks for the catch, and we will let you know when it is fixed!
Anonymous
October 17, 2007 at 7:03 pmPost count: 1I have a similar problem in that I am unable to save to the “Settings for Insteon ALL_Link Group Commands” part of the utility. I am using version 1.3 and am trying to write to a EZIO 2X4. I can write to the other areas just not that one. Am I missing something?
Anonymous
October 27, 2007 at 5:01 pmPost count: 15It seems that there are lots of bugs
– can write settings in the eeprom
– Progress bar totaly useless, stop in the middle or does not moveplease advise if there is a more stable version, I need to install a few of these modules at customer sites ASAP
Thanks
Dan
Anonymous
October 27, 2007 at 7:30 pmPost count: 408We found and duplicated a problem with the inputs on the EZIO section – we are working on resolving that – target Sun.
Anonymous
October 31, 2007 at 9:52 amPost count: 15Did you come up with a solution ?
If not any new ETA?
We need a working solution asap, otherwise I need to start lookig for an alternative to offer to our customers.
Regards
Dan
Anonymous
October 31, 2007 at 2:39 pmPost count: 408sorry – should have posted on this thread as well, v1.4 addresses this bug and is available for download as of Mon Evening.
the bug was found in the read and write of the inputs section for the EZIO utility. if there are other outstanding bugs, please let me know and I will target a one day turnaround.
Anonymous
November 1, 2007 at 10:36 amPost count: 15Paul, the setting of insteon commands for the inputs appears to work fine.
Now I have a major stabillity issue even if I make no changes to the state of the inputs I get all inputs on or all inputs off whenever I request their state via your software. (below is the log of communications)
I tried putting all the inputs + and – to ground except I1 to make sure it wasn’t a floating issue but the problem remains there, it seems to be more stable when I1 is on (+12v applied to I1+) but it goes bezerk when I1 is off…
2007-11-01 06:28:46.625: sendinsteonraw=True
2007-11-01 06:28:47.031: eventraw=04
2007-11-01 06:28:47.078: receiveinsteonraw=04 08 21 10 07 FC D5 2F 49 00
2007-11-01 06:28:47.093: eventraw=03
2007-11-01 06:28:47.109: eventraw=03
2007-11-01 06:28:47.203: eventraw=03
2007-11-01 06:28:49.328: sentinsteon=00 00 00 08 21 10 0F 49 00
2007-11-01 06:28:49.625: sendinsteonraw=True
2007-11-01 06:28:49.937: eventraw=04
2007-11-01 06:28:50.093: receiveinsteonraw=04 08 21 10 07 FC D5 2F 49 FF
2007-11-01 06:28:50.109: eventraw=03
2007-11-01 06:28:50.109: eventraw=03
2007-11-01 06:28:50.125: eventraw=03
2007-11-01 06:28:53.156: sentinsteon=00 00 00 08 21 10 0F 49 00
2007-11-01 06:28:53.359: sendinsteonraw=True
2007-11-01 06:28:53.578: eventraw=03
2007-11-01 06:28:53.781: eventraw=04
2007-11-01 06:28:53.843: receiveinsteonraw=04 08 21 10 07 FC D5 2F 49 00
2007-11-01 06:28:53.859: eventraw=03
2007-11-01 06:28:53.875: eventraw=03
2007-11-01 06:28:54.000: eventraw=03
2007-11-01 06:28:56.625: sentinsteon=00 00 00 08 21 10 0F 49 00
2007-11-01 06:28:56.937: sendinsteonraw=True
2007-11-01 06:28:57.250: eventraw=04
2007-11-01 06:28:57.406: receiveinsteonraw=04 08 21 10 07 FC D5 2F 49 FFRegards
Dan
Anonymous
November 1, 2007 at 10:56 amPost count: 15Hello Paul after running some more test, the module keeps getting back to its original settings group: 1 cmd1:11 cmd2:0 cmd1:13 cmd2:0 …
I managed to stabilise the input behaviour from my previous post by setting putting input 1 to on and then playing only with input 2… altought it is not vrey practical to lose an input!
Please keep me posted of your progress
Dan
Anonymous
November 5, 2007 at 1:15 amPost count: 256Dan, how are you using the inputs? Just placing a voltage on either side of the input is the same as having it float. Are you just using the broadcast messages or is the device linked to other units?
Al
Anonymous
November 5, 2007 at 12:16 pmPost count: 15As I mentionned in my previous post, I have tried several different scenarios.
The latest one is connecting all inputs -‘s to GND and +’s are left floating exept for DI1+ which is connected to +12V, both AN1 and AN2 are also connected to GND. This set-up works ok when working with inputs 2,3 and 4. The minute I unplug DI1+ from +12V, all inputs show alternatively as ON or OFF using the Simplehomenet Utility “Input status”. Note that all inputs show the same status either ON or OFF. I have tried putting DI1+ to GND without any success.
My biggest problem now is that the device won’t keep it’s “Settings for Insteon All_Link Group Commands”, it either gets reset to it’s initial values or set to very strange values.
This is the sent log when I set Input 1 to Group:1,CMD1:13,CMD2:0,CMD1:11,CMD2:0
To ID:08.21.10 flags:0F cmd1:28 cmd2:0
To ID:08.21.10 flags:0F cmd1:2B cmd2:1A
To ID:08.21.10 flags:0F cmd1:29 cmd2:0
To ID:08.21.10 flags:0F cmd1:2B cmd2:58
To ID:08.21.10 flags:0F cmd1:29 cmd2:0
To ID:08.21.10 flags:0F cmd1:2B cmd2:40
To ID:08.21.10 flags:0F cmd1:29 cmd2:1
To ID:08.21.10 flags:0F cmd1:2B cmd2:20
To ID:08.21.10 flags:0F cmd1:29 cmd2:13
To ID:08.21.10 flags:0F cmd1:2B cmd2:21
To ID:08.21.10 flags:0F cmd1:29 cmd2:0
To ID:08.21.10 flags:0F cmd1:2B cmd2:22
To ID:08.21.10 flags:0F cmd1:29 cmd2:11
To ID:08.21.10 flags:0F cmd1:2B cmd2:23
To ID:08.21.10 flags:0F cmd1:29 cmd2:0If I very them immediately using the “read” command, everything is fine.
Once I trigger Input 1, nothing gets sent and I read the setting, this is what I get:
from ID:08.21.10 flags:2F cmd1:28 cmd2:0
from ID:08.21.10 flags:2F cmd1:2B cmd2:0
from ID:08.21.10 flags:2F cmd1:2B cmd2:0
from ID:08.21.10 flags:2F cmd1:2B cmd2:0
from ID:08.21.10 flags:2F cmd1:2B cmd2:11
from ID:08.21.10 flags:2F cmd1:2B cmd2:0
from ID:08.21.10 flags:2F cmd1:2B cmd2:13
from ID:08.21.10 flags:2F cmd1:2B cmd2:0As if the module resets….?
Note: I use the internal supply provided by the PLM, could that be the source of the problem?Anonymous
November 8, 2007 at 4:21 amPost count: 256Daniel, a very fundamental question is whether you have a solid communciation with your module. Simply go to the section of the utility for the EZIOxx, enter the ID and see what version ofthe firmware is returned under the ID box. When not connected it says “not connected”, then it shows “Connected to EZxx VXX” where xx is the firware version number. If thisi not solid, then there is another issue and there is no point trying anything else with the utility. If this happens, there may nbe an issue in your Insteon network such as a noise suppressing outlet strip or UPS or whatever swamping the Insteon signal.
Al
Anonymous
November 8, 2007 at 10:36 amPost count: 15Has you concluded from the email that I sent you with a video of the behaviour of the LED, the module resets after sending a packet. So the problem is not with the Insteon communications.
PLM version 3407Firm52 REV 2.4
EZIO8SA version 17 -
AuthorPosts
- You must be logged in to reply to this topic.