upstatemike

I have guests now so I can't do any more testing for a few days. I have no trouble programming the switch, linking the switch, doing a query on the switch, etc. It is only local control that is an issue. In a few days I will set up a test with the switch plus a new appliance module plugged directly into the PLM. I will add these to the ISY, link them, veryify that local control of the switch correctly operates the linked appliancelinc, and review the link table per Michel's directions above.

v2.5 date code 0738

I'm glad you don't have any problems. I don't understand why it works fine for you while I have switches that don't register in ISY when operated locally.

Scenes and programming would not be an issue, just local control tracking. I tried a 4.0 and got nothing. I tried two 2.5s and one worked and one did not. 2.2s always seem to work. (I am using relays not dimmers) What is the version of your PLM? Mine is v63.

ISY not able to track local operation of the switch.

OK, I'll do some testing. I think switches labeled V2.2 are reliable but I'll try to confirm it.

So do we know what the last reliable (all I1) switch version was? Maybe I can find enough on the used market to finish my house.

This is of course a concern for those of us with way too much I1 stuff to replace it all. I only see two possiblities: 1- Have a way to manually identify what table to use for a given device since you can't depend on the firmware version that it reports to tell you which commands to use. Of course you still have to figure out what manual setting to pick. 2- Come up with a way to overwrite the firmware on out of warranty devices with something that will work reliably. SH will not be pleased with this approach but in the absence of an official solution...

I use option number 2 and use a really good X-10 repeater to get the X-10 signal to the ISY. So far it has worked pretty well.

This one works great... but how do you exit? ctrl C?

I tried the new one but had the same problem. I checked the .net 3.0 settings and saw that 2 items were not checked by default. I checked those items and Windows installed those elements but it didn't solve the issue.

MORE ERROR INFO FROM THE SYSTEM PROMPT WINDOW (IP and user / password edited for this post) C:\Users\Michael>isylogger XX.XX.XX.XX ***** ***** ISYLogger version 1.0 Copyright© 2008 Robert Paauwe Created service client. Set ClientCredentials. Get ISY Config. Get Nodes Config. Unhandled Exception: System.ServiceModel.CommunicationException: The maximum mes sage size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding eleme nt. ---> System.ServiceModel.QuotaExceededException: The maximum message size qu ota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpInput.ThrowMaxReceivedMessageSizeExceeded () at System.ServiceModel.Channels.HttpInput.GetMessageBuffer() at System.ServiceModel.Channels.HttpInput.ReadBufferedMessage(Stream inputStr eam) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(Exception& req uestException) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpCha nnelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeS pan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message messag e, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on eway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan tim eout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on eway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCall Message methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage req Msg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgDa ta, Int32 type) at ISYLogger.UDISYServices.UDIServices_PortType.GetNodesConfig(GetNodesConfig Request request) at ISYLogger.UDISYServices.UDIServices_PortTypeClient.ISYLogger.UDISYServices .UDIServices_PortType.GetNodesConfig(GetNodesConfigRequest request) at ISYLogger.Program.Main(String[] args) C:\Users\Michael>

I gave it a try but got this error: Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: isylogger.exe Problem Signature 02: 1.0.0.0 Problem Signature 03: 491119c0 Problem Signature 04: mscorlib Problem Signature 05: 2.0.0.0 Problem Signature 06: 47577b16 Problem Signature 07: 416b Problem Signature 08: 27 Problem Signature 09: 2M52EXV2C4QV0UEVRPJP1P2VVUBSMIVE OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 1033

OK.. What does that mean exactly? Is it something like subscribing to an online magazine?

Anything that shows simple "log style" events in real time.

Will this have an option to echo the log out the serial port in real time so that other devices can trigger things off of the status changes tracked by the ISY? Will there be an option to construct custom ascii out strings sent from programs? For example: will I be able to have a program trigger on a dimming level cahnge of a switch and send an ascii string out to a TTS program on a PC that will speak the new dim level? Code: Living Room Lamp Level If Status 'Living Room Lamp' is changed Then Serial Out "speak.exe The Living Room Lamp is now set to %'Living Room Lamp Status' percent" Else - No Actions - (To add one, press 'Action') Where speak.exe is some TTS program on a PC and %Living Room Lamp Status is a variable that holds the current state of device Living Room Lamp.

Actually, the log is already in this format and I guess I could do my tests and then review it in Excel. I'm just suggesting that it would be handy to have an event viewer view that shows the log entries in real time. Or is there already a way to do this in the GUI?

Is there a way to set the event viewer to provide a less detailed view? I'm looking for something that uses the assigned names rather than the Insteon addresses and just show changes as in: Device "Kitchen Lights" ON Device "Front Hall" Fast OFF Scene "Evening" ON X-10 L4 OFF etc. The way I want to use it is to walk around testing a bunch of stuff and then scan down the list of actions in the event viewer to verify which actions registered correctly. The detailed events in showing raw Insteon traffic are great for looking at a small number of commands in detail but for larger lists of commands the simple format would be much more readable.

I don't know if you are interested in a full weather station but I use one and it lets me trigger programs not only on outside temperature but also on wind gust, humidity, etc. I use a RainWise weather station (but any popular brand should work) which logs data to a simple .csv file using a program called Virtual Weather Station. I use my Stargate Home Automation controller to trigger a simple 1 line batch file to parse the values I want from the .csv file and populate variables within the Stargate controller. The Stargate then uses simple X-10 to trigger actions in the ISY. You could easily substitute Homeseer for the Stargate or even create your own application to pull values from the .csv file and communicate directly with the ISY over the network. I doubt if you will see an Insteon based outdoor temperature sensor any time soon. Thermostats and temperature sensors based on lighting protocols (Insteon, Z-Wave, etc.) have been very disappointing because they generally do not report changes often/quickly enough to be useful and in the case of thermostats, some do not even report manual setting changes. If you want to trigger something based on temperature or HVAC settings you will be much better served with a weather station or serial based sensors.

This would certainly be helpful. Even the ability to just be able to see the unkown links would go a long way towards helping with troubleshooting.

The very best answer would be to use a Logitech Squeezecenter music server which has an open and robust network interface that could easily be supported by a product like the ISY. If all you need is to play a short wav file you might look into using an Elk voice announcement module triggered from a wall wart transformer plugged into an appliance module.

Yes, there will be a Homeseer plugin for the ISY and this will open up a number of new possibilities for Insteon integration. While it is true that some hardwire IO, thermostat control, and security functions can be achieved with existing integrations with Elk M1, EZIO modules, etc, Homeseer will bring some truly unique functionality to the table including: TTS based voice prompts for Insteon actions ("party scene activated") Insteon control via voice recognition Insteon control based on home weather station input Insteon control via telephone etc. An ISY + Elk M1 + Homseer Hometroller 2 + Way2Call modem would be and incredibly flexible automation platform.

This is an interesting point to consider. In any other automation device I have used the If section acts as a trigger, and once triggered the Then section completes execution regardless of whether the trigger remains true or not. The idea of a trigger needing to stay triggered thoughout execution is definitely a different paradigm for a lot of folks.

I don't know your specific situation but two things I have found to be helpful if you haven't already tried it. 1- Make sure you have a static IP address set. Then you have one less variable to deal with when troubleshooting connectivity issues. Does the ISY respond to a ping so you know it is online? 2- Unplug the PLM for at least 10 seconds so everything re-initializes before trying to connect. Most of my connectivity errors have been from something getting stuck in an odd state and this always clears it.

I'm not sure I understand what you are asking but I want to be sure you are clear that the ISY is MANAGING links not CONTROLLING them (unless you set up some programs to do control). I did the same thing as you because I had so much stuff to keep track of that starting from scratch would have taken too long, so I left the existing links in place. This caused problems in some areas so once I got everything arranged the way I wanted, I started deleting and re-adding devices one to a time. When I re-added them I chose the option to clear the existing links in order to ensure all the junk was cleared out of the modules link table. If you don't do this then any junk that was in the link table will not be reflected in the ISY gui but WILL be faithfully restored any time you do a restore on the module. There is currently no way to see what that junk might be so you have a potential troubleshooting nightmare if you don't let ISY get rid of everything it does not manage.