upstatemike

I don't have any coupon codes but I do want to remind you that you can use the plugin for 30 days before deciding to buy. Maybe a coupon code will come out during the 30 day trial.

it works well because i am going through the phone system instead of open air microphones. yes I'm using stargate relays to direct the announcements but may change that to Elk relays or some other strategy. The stargate integration let's me read or populate Stargate variables from Homeseer. Example: the WinEVM event that announces the thermostat settings and furnace runtimes for the day also speaks the outside temp and humidity. These values come from my weather station and are populated into Stargate variables by Homeseer. House pre-dates electricity so it was not built around the wiring. Some things just require the reliability of hardwiring ie thermostats, network music players, smoke sensors, etc.

Not sure I understand the question... Homeseer is software so it is always PC based. I use the Hometroller which is a fanless PC preconfigured to run the Homeseer software. I am running HSPro with the ISY plugin. I also use HSPhone which lets me use any of my 21 speakerphones to control my lights via voice command. I use a PA amp to distribute TTS announcenements to various places. Not as stable as my Stargate (which is also connected to Homeseer) but Stargate really only does Thermostats and and caller ID snd hardwired monitoring of some remote lights in the attic and basement, and logging furnace run times. Key point about Stargate is response time since it polls the status of every input at least 3 times per second. Allows things like real-time voice confirmation of any change in thermostat settings whether manual or system based (not possible with Insteon based thermostats) etc. I eventually might be able to phase out the Stargate by moving the serial themostats and hardwired monitoring to my Elk M1 and letting Homeseer do caller ID and furnace run-time logging. It is just so much easier to do these things with Stargate that I have been slow to migrate.

I am using Homeseer which gives me both TTS and voice control. If I want to speak a phrase whenever an Insteon button or switch is pressed it will do that. I can also tell it "Media room lights 50 percent" and it will do that too.

First, the scenario you suggest is valid but not common. Normally you would make the switches with the loads controllers of the scene as well as the "no-load" switch so that operating any one of them would control all. (Remember "contoller" really means "controller and responder") Second, the status of the scene is only affected by controllers of that scene. If the "no-load" switch is the only controller then it is the only thing that controls the scene status. Operating the switches configured as responders would have no impact on the status of the scene (even though the state of devices in the scene has obviously changed.) The controller device in this case Does have a state but it is in relation to the load of that switch. Just because you do not have anything connected to the load wires does not mean the load output does not operate. If all the switches are set as controllers then turning on any one of the will turn them all on including the one with no physical load connected. If a switch is set as a responder only then turning it on will only affect the load of that switch and not the others in the scene. There is also a GUI anaomly in that Controlinc and RemoteLinc buttons are shown as devices that are "managed " in a scene but of course this is not really the case. There is no reason for a ControLinc button to know about other ControLinc buttons in a scene since there is no load to turn on or off when the scene is activated or deactivated. I think it would be cleaner to show a Controlinc button managing the loads in a scene without suggesting that anything is managing it. (ie, a ControLinc button can never be a responder)

My experience was just the opposite. I was never able to play the violin prior to 2.7.12 and now I can.

Just edited that post because I got it to work after several attempts. (The compare, not the ramp rate setting)

The dimmer had 9 extra links and the remotelinc had 16 extra links. I restored both and now they match ISY. Restarted admin console but still get "request failed" if I try to change the ramp rate. Going to leave it for now and take a fresh look next week.

Nope, no green 1010 icons. Device 00.1A.5A is a SwitchLinc Dimmer v.22 and has been in the scene for years. Nothing has changed in this scene. The only change made was to add new LampLincs to button 2 on a RemoteLinc. Button 1 on this same RemoteLinc is a controller for the problem scene. It was after changing that button 2 scene that the button 1 scene lost its level and ramp settings. Maybe I need to delete and reinstall the remoteLinc?

Not sure what you mean by the correct url? I use a fixed IP address so my url is always 192.168.0.7/admin The event viewer does not register anything when i attempt the ramp rate change and get the "request failed" error. On the same device I do get acvtivity when I try to move the level from 0% (where it is stuck) to 100% and get a "request failed" error... I can send you that log. Also note I do not have either Flex Your Power or Auto Open ADR enabled.

Unfortunately neither 2.7.11 nor 2.7.12 fixed this. I still get this error if I try to change the ramp rate from 9min to 2 sec: [-110022] couldn't open file [/CONF/FYP.CFG] [-110022] couldn't open file [/CONF/ADR.CFG] After this error displays once any further attempt just results in "request failed"

I thought that the limited memory in the 2413S made it a non-starter? Also what about the lack of power... does this mean going back to an external wall wart?

I get this sometimes and can usually clear it by clicking the batch icon twice. One switch is still stuck that way and I assume it is just a communications issue. Was planning to stick an access point close to it to see if that helps.

So your scene sends a group command and your backup sends individual direct commands?

Sorry if this is covered someplace but I couldn't find it. I am on 2.7.8 and I just added two new Dual -Band Lamp-lincs. Since this version des not support replace for these devices, I just added them to the scene they need to be in and configured them to match the old ones. The RemoteLinc controlling the scene using button 2 works fine but the scene on button 1 (which I did not edit) somehow got it's ramp rate changed to 9 minutes. If I try to change it back to 2 seconds I get an error that says "request failed" or "cannot open file xxxx - I can't remember the path and can't get it to repeat). Tried clearing Java cache, tried rebooting ISY. Any ideas what else I can try?

I can understand how an X-10 address can cause unexpected operation of a single module but how was it triggering a scene?

My link count is 754 so yours does not seem out of line.

OK, Thanks. I'll migrate to the next non-alpha rev that comes out.

The module I wanted to replace was a 24456D2 2-pin V.24 lamp module but when I right clicked on it and selected "replace module with", the new Dual-Band LampLinc that I had just added to my ISY did not appear in the dropdown. (It only offered SocketLincs and other 2-pin lamp modules). The new module is a B24572 lampLinc BiPhy v.3A and I went ahead and added it to the scenes manually instead of using replace. I suggest any lamp module should be able to select any other lamp module type (2-pin, 3-pin, or Dual Band) as well as the SocketLinc as a potential replacement.

Just got a Dual-Band Lamplinc to test out and went to replace an existing Lamplinc only to discover my new device is not listed in the replace dropdown. I'm using FW 2.7.8 Is this normal? Do I have to maunually delete the old Lamplinc and add the dual-band to all of the related scenes?

I don't think deleting and recreating a scene will guarantee a new memory register in the PLM. It will probably just put the new one into the hole just created by the deletion. I suggest leaving the existing scene in the PLM without any controllers to ensure the suspect memory location is not reused. This will force the new scene to be created in a new PLM memory register.

I wonder what would happen if you added 1 togglelinc back to the scene as a responder only (so the scene still exists in the same memory location of the PLM) and then created a new scene configured with the same controllers and responders as the original? If the new scene triggers it must be caused by a device in the scene. If just the one togglelinc triggers it would point to the PLM memory location. While X-10 can trigger individual modules I don'y see how it could be responsible for triggering a scene.

Just curious ... is there a ControLinc button included in the scene?

I just replaced 8 Switchlinc relays due to paddle problems and I see the new ones are all v35. What exactly is the issue with this rev and how can I test to see if mine have the problem? Am I going to have to swap these all out again?

I am running 2.7.8 and since upgrading have swapped a large number of devices due to paddle problems and also manually renamed and assigned folders to all 440 of my devices, scenes and programs. Am I going to lose all of this work?