nstein

Hi Michel, I have been having problems for a few releases now using device reported Insteon communication under advanced options. I2, devices will not add in this mode giving an error; New links in this mode don't seem like there added, though I get no errors. I understand this mode is not recommended and most users had problems, but for me it was opposite; It worked good and the speed increase was noticeable also a few times (RemoteLincs) it seemed to work better than I1. A large amount of my devices are I2, as I had lots of LampLincs that died on me and where replaced, also I have many access-points. It still could be communication or other issues but If you could do some quick testing on your end I would appreciate it. Thanks, Nick

Hi Michel, I already have the following link in IsyAjax to install the admin console that has a version number in it. To maintain compatibility, next release couldn't you add a link both with and without the version, that took you to the same file. "http://www.universal-devices.com/99i//admin.jnlp" Thanks, Nick

I am successfully using an older EzSnsRf with a Dakota alert motion sensor , driveway sensor, and a universal transmitter. It has been a long time since I have setup my EzSnsRf; It can be a pain getting it linked. Also I am not sure if all EzSnsRf versions work, I have seen mixed reports, but that could be just the poor linking setup, and/or the noise issues that affect any Insteon device. -Nick

The following new rest commands aren't working from me in 2.7.10, page cannot be found: /rest/batteryPoweredWrites /rest/batteryPoweredWrites/on /rest/batteryPoweredWrites/off Thanks, Nick

Hi Michel, No there where other entries, I checked the logs an half hour after that log entry. Here is bigger section of my log, I have a program that fires at 11 with direct commands changing many devices, and an network command. (Scene Hallway Early and the Thermostat Query are different programs) Outside / Barn / Barn Thermostat B2.0 R2 Status Query° Tue 01/19/2010 10:52:40 PM Program Log Scene:Upstairs Hallway / Hallway Early Off 0 Tue 01/19/2010 11:00:00 PM Program Log 0 Net Mod Tue 01/19/2010 11:00:03 PM System -140005 Main / Above TV Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Above TV Dimmer Off 0 Tue 01/19/2010 11:00:03 PM Program Log Basement / Basement Stairs On 25 Tue 01/19/2010 11:00:03 PM Program Log Upstairs Hallway / Cubby Hole Main Off 0 Tue 01/19/2010 11:00:03 PM Program Log Upstairs Hallway / Cubby Hole Single Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Cupboard Relay Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Deck Inside Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Flower Room Relay Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Front Section Relay Off 0 Tue 01/19/2010 11:00:03 PM Program Log Main / Living Room South Window Off 0 Tue 01/19/2010 11:00:04 PM Program Log Basement / Low Voltage 3V Off 0 Tue 01/19/2010 11:00:04 PM Program Log Main / Micromave Relay In-Line Off 0 Tue 01/19/2010 11:00:04 PM Program Log Upstairs Hallway / Stairway Single On 25 Tue 01/19/2010 11:00:04 PM Program Log Scene:Upstairs Hallway / Hallway Early Off 0 Tue 01/19/2010 11:00:04 PM Program Log Main / Above TV Status 0% Tue 01/19/2010 11:00:04 PM System Log Main / Above TV Dimmer Status 0% Tue 01/19/2010 11:00:05 PM System Log Upstairs Hallway / Cubby Hole Single Status 0% Tue 01/19/2010 11:00:06 PM System Log Main / Flower Room Relay Status 0% Tue 01/19/2010 11:00:06 PM System Log Main / Front Section Relay Status 0% Tue 01/19/2010 11:00:07 PM System Log Main / Living Room South Window Status 0% Tue 01/19/2010 11:00:07 PM System Log Basement / Low Voltage 3V Status 0% Tue 01/19/2010 11:00:08 PM System Log Upstairs Hallway / Stairway Single Status 10% Tue 01/19/2010 11:00:09 PM System Log Scene:Upstairs Hallway / Hallway Early Off 0 Tue 01/19/2010 11:00:10 PM Program Log Scene:Upstairs Hallway / Hallway Early Off 0 Tue 01/19/2010 11:00:10 PM Program Log Outside / Barn / Barn Thermostat B2.0 R2 Status Query° Tue 01/19/2010 11:09:40 PM Program Log Thanks, Nick

Hi Michel, I have the following log entry "Main / Cupboard Relay Off 0 Tue 01/19/2010 11:00:03 PM Program Log", than nothing about that device afterwords. When I checked admin console the device was still on, and ISY listed the status as ON when it should have been turned off. There are no -2s after the above. Thanks, Nick

Since I upgraded from 2.7.6 to 2.7.9, I have noticed some devices aren't turning off, based on there programs; The same program contains many direct command some either aren't firing part of the time or are experiencing sudden noise issues that are bad timing, I haven't had this much problems since ISY was skipping steps in programs a few updates ago. I am not getting any communication errors with these devices when I open the admin console and I can manually query without problems. The logs show the program triggering the device but doesn't update the status, in the log or admin console. Thanks, Nick

Michel, upgrading from 2.7.6 to 2.7.9, I have some scenes where the on level is now set to off, when I try to set it back to where it was in 2.7.6 I get a Request Failed Error; Or some times a [-110022] Couldn't open file [/CONF/FYP.CFG] or [-140005] HTTP client read response failed [Net Module Rule: 2]. One of these scenes is the RL that ISY was not updating the status of the responding LL. (Reported a few days ago with 2.7.8 before I went back to 2.7.6) Also 2.7.9; KP and RL Grouped Devices, only the parent node is colored red as a controller the rest are blue responders. Thanks, Nick

I also have one sitting in the box, waiting on ISY support and some implementation difficulties. -Nick

Hi jbwood1, It sounds like ISY isn't getting the messages from EzSnsRf, if you haven't already, can you try plugging the EzSnsRf into or right next to the ISY PLM? You can also open event viewer in the ISY admin console and see if it is receiving any messages from EzSnsRf address. -Nick

Hi Michel, Yes the other RL buttons worked liked expected, ISY updated the status of both the RL and the linked device. Thanks, Nick

I am also having problems with my EzSnsRf, was working fine in 2.7.6. Event viewer level 3 shows ISY is receiving the messages but not updating the status of the device, on any of my 3 sensors. I also have a RemoteLinc button where ISY was updating the status for the RemoteLinc button but not the controlled device; other buttons on the same RemoteLinc was updating both like expected. Downgraded back to 2.7.6, restored backup, both the above are back to working like expected. -Nick

I should have added, even though I am getting communication errors, my programs are triggering reliably, at least 95% if not 99% of the time. One exception, is when I had a motion sensor triggering right before my driveway sensor, causing colliding signals to be lost. Mine goes ON and OFF real quickly, at least with the I/OLinc and driveway sensor, not sure about the motion sensor. I tried setting a delay but my firmware has a bug causing it to lock up with a delay set. I don't know the firmware offhand, and can't check right now. The only way to upgrade the firmware it to send it back to SimpleHomeNet, I done this once when I first received it last year; I had lockup problems, probably the delay bug that wasn't discovered till later, and I didn't re-set a delay on the replacement unit until recently. On adding if you already had another sensor added make sure the code is different, that caused me problems. I found that triggering my new sensor triggered a device already added in ISY. -Nick

I added my EzSnsRf to ISY around a year ago, using the Add Sensor to EzSnsRf method. I can't remember the exact steps, just that it took a couple of tries; I believe after linking to ISY, the EzSnsRf is still waiting for a timeout to be set but it is already linked. Yes I have been using programs, recently I tried to add EzSnsRf to a scene to find it was only a responder; Yet I remember linking it as a controller in the distant past; Maybe something happened in one of the firmware updates. On a side note I am also getting a lot of communication errors with the device, just with normal operation not when editing links; but query seems to do nothing, and I don't know why ISY would try sending commands to it. -Nick

Hi Michel, Mine is 7.5.0.0 Thanks, Nick

I also have an EzSnsRf, that is added as a responder, it is color coded blue not red; I can't add it to any scenes as a controller, and is not already a controller for any scenes. Thanks, Nick

Hi Michel, I wasn't suggesting to read/write to the motion sensor every time it sends a command. Just after a user requests status or a change, and if you want to check it, just to make sure limit it to once every x hours/weeks or times tripped. The settings we have now shouldn't be changing by themselves so checking them every time the motion sensor turns on would be wasteful and needlessly add to traffic. This could change if/when Smarthome creates an updated motion sensor with new features. On way of implementing; A user request settings/link update or change, instead of doing the programing now ISY puts it in a query and checks the query every time it receives a command from the motion sensor; So the next time motion is sensed it makes the changes and removes it from the query, if the query is empty it does nothing. On the down side it is going to be more work to program, sorry . Thanks, Nick

Hi Michel, No I am not certain but, it looks like what they are doing. With the current released version I don't think HL2 uses any commands/features ISY doesn't. What feature is missing from ISY and revision 1.x motion sensors that HL2 supports other than needing to enter linking mode? The only thing ISY would have to do is query/delay a request or change to happen the next time motion is detected, or a command is received from the motion sensor. I just done a quick test; I told ISY to read the settings, clicked OK but didn't put the motion sensor into linking mode, instead I just triggered motion and ISY was able to read the settings. But this only worked once of a couple tries, I might have got lucky, plus it was with a beta version I had handy. -Nick

I don't think they are doing anything secret. You just have a very limited time window, as soon as HL2 receives an on command it sends a command to the motion sensor retrying if needed. Everytime the motion sensor sends or recieves a command it will stay awake for a second or two.

I will let someone else confirm or correct, but I believe ... In 2.7 the rest interface is only available with the Web/Network module. In one of the later 2.7.? beta's, rest was included without needing to buy a module. So you would either have to upgrade to the beta release or buy the Web/Network module. -Nick

I have a 1.0B with a GP super alkaline battery, it came with, that gave me a low battery warning. Even though the battery didn't last as long as I would like or as long as my other motion sensors (another 1.0B, and one 1.1), it lasted a lot longer than the beta unit which was exchanged by Smartlabs. -Nick

Try setting the set-point in ISY, it might be out of range. -Nick

No, The network module is only for sending, at least at this point. It doesn't even process the response. If you have control over what is sent, you can control devices and programs using the rest HTML interface. -Nick

Sorry, from my experience, the Dual-bright motion sensors are incompatible with the In-LineLinc w Sense, only motion sensors with relays in them work. -Nick

This is a known problem in 2.7.3 and is fixed in 2.7.4 by making encoding optional. If you need the fix sooner, e-mail support. (support@universal-devices.com) See http://forum.universal-devices.com/viewtopic.php?t=2684 for more information. -Nick