Techman
Members
-
Joined
-
Last visited
Everything posted by Techman
-
The dual band ON/OFF module does not have a sensing circuit.. I got rid off all my appliance modules (now discontinued) and replaced them with the ON/OFF modules
-
You could also use the ON/OFF module which has a relay instead of a triac. This would guarantee you an off regardless on the attached load.
-
A bulb shaped icon represents an Insteon LED bulb. Try deleting the module then reinstalling it.
-
-
-
-
-
You need to clear out your Java Cache including applications, then install the current version of the Administrative Console (4.3.26) for the ISY. You should also remove power from the PLM and the ISY, then power up the PLM, wait about 15 seconds then power up the ISY. Let me know if that helps.
-
-
-
Put all your lights into one scene Trigger the scene at Sunset +2 minutes eliminate the repeat and the waits and you should be good to go.....
-
It could be a timing issue. What type of bulbs are you using other than LED's? Can you post a copy of the program you're using to turn on the lights
-
What type of bulbs are you using, CFL, LED or Incandescent? Some bulbs can create noise, such as CFL's, on the powerline which could interfere with the signals reaching the other devices. You might want to also check the link tables/compare in the devices that you're having a problem with.
-
Be sure to check the exclusions Smarthome.pdf
-
Do you have "trigger reverse" checked on the IOLinc options? If so, uncheck it to see if that makes a difference. It doesn't sound like a communications problem if the query is successful unless the gate motor is creating noise on the powerline. You might want to update to the latest ISY firmware.
-
Do a "Show Device Links Table" then click on compare. The results will show you any mismatched links.
-
Teken, what's the firmware version, and hardware version if you have it, of the MS that you had had false on signals from when the battery voltage got low?
-
There could be a conflict if a device is currently linked to the Hub. Try doing a factory reset on a problem device then try to link it to the ISY. I don't think you can have two controllers controlling a device as the left hand wouldn't know what the right hand is doing. I would suggest removing the Hub and using the ISY.
-
Type in just the device address and use auto discover. If that doesn't work then you may have a communications issue, either interference or poor powerline coupling. What model PLM are you using?
-
So do you think it's a firmware issue with the MS or a compatibility issue with lithium batteries?
-
In my case the node that's falsely triggering is the motion node not the low battery node
-
Is the attached screen what you're using to link new devices?
-
I have several motion sensors, Rev 2.3, firmware v.41, that are using lithium batteries. When the battery voltage drops to about 7.8 volts the motion sensor(s) starts to send continuous false on commands. With one of the sensors the low battery node came on after awhile but the sensor sent false on commands first. I'm not sure if this is an issue with the sensor low battery node treating the lithium battery differently than alkaline batteries or if it's a device firmware issue with the low battery node not being triggered early enough. Has anyone else experienced anything similar?
-
After linking your devices run an ISY "generate topology" report and you'll have a record, with addresses, of all you devices.
-
Gee, when you add the battery operated devices only put one device at a time into the linking mode. After adding to the ISY wait for the device to time out, about 4 minutes, before putting the next device into linking mode. The battery operated devices go into sleep mode when not being used in order to conserve the batteries which is why you're not able to link or query them from the ISY
