upstatemike

I am still having a lot of trouble with switches not reporting their status. These are mostly 3 year old rev1 Icons, not newer I2 stuff. They work in all other respects... linking, control from the ISY gui, etc, but will not report local operation. My PLM is 2.75 hardware with .63 firmware. I have another 2.75 PLM that I could try (left over from the old verson IES touch screen) but I am not sure if it is worth trying it? The hardware rev is the same and maybe its not worth trying unless I get something newer? My concern is writing new links to every single device in my system. Status takes over 10 minutes on startup... I wonder how long a PLM swap will take? Hours and hours? I'm thinking there is a lot of risk in making a swap like this with not much chance of improvement. Is this valid or should I just go for it? (I should add that my family will make life very unpleasant for me if there is any significant outage or other impact to the lighting system as a result of trying this).

Tried it and I am getting the same result. Do you want me to send you the switch so you can observe it first hand?

OK I upgraded to 2.6.9 and ran the tests again. All functions continue to work properly from the gui. Turning the switch On or Off still operates the linked appliacelinc 100% of the time and I can see signal activity (flashing Isteon LEDs) whenever the paddle is pressed so the switch always transmits something. The On paddle never updates the ISY on the first press. If I press the upper paddle repeatedly the status will eventually change in the ISY gui. When it does, the Appliancelinc goes to On and the switch goes to 1% (IT IS A RELAY SWITCH!) The Off paddle never updates the ISY on the first press. If I press the lower paddle repeatedly the status will eventually change in the ISY gui. When it does, the Appliancelinc goes to Off and the switch goes to Off.

The link count says 567. Not sure if it is decimal or hex? Set event viewer to level 2 and there are no entries when I operate the switch. If I control it from the gui I see entries in the event viewer. I would say the switch is not sending anything out except that the linked appliancelinc operates with every switch press... no misses at all. Maybe the wacky Insteon security model that makes the PLM block signals from devices without links to it is messed up and is blocking messages from a valid address?

Ok the link count is 567 (1383?) PLM address is 09.37.DC The switch has a link E2 01 09.37.DC 00 00 01 The switch address is 09.FA.C7 The PLM has a link A2 01 09.FA.C7 02 0A 2C

I have set up the test switch and test appliancelinc with both plugged into the feedthrough on the PLM. I made the switch a controller for scene "TEST" and the appliancelinc is a reponder. Operating the switch causes the linked appliancelinc to operate 100% with no misses (Not a microswitch issue). Neither the switch nor the appliancelinc update in the ISY gui. Both can be queried from the gui and will then update. Switch = 2.5 on the sticker and v.2c in the gui Appliancelinc = 4.1 on the sticker and v.32 in the gui

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.