larryllix

The controller is the correct one. When you hook up the cable to the RGBWW terminals you may find R-G reversed. The last batch I got had those terminal reversed...or OTOH the firmware inside reversed. It's very easy to swap two wires on the cable when you wire them. Due to the delicacy of the wires, I stripped them longer, tinned them, and terminated them. then I folded the power and RGBWW cable back past the controller and white vinyl taped it to the case. The wall panel looks like it would do the trick and dual purpose for DMX serial connections also. More study would be required on that one. I just use the MagicHouse app on my Android phone for setup. The only time I really used the app is, after a factory rest on the devices they throw out their own SSID. You connect to that, run the app and set your house SSID and password into it, Then the SSID goes away and the app connects via your house SSID. I run my house RGBWW strips (I have 4 partials and 1 whole 5m over/under cabinets) from one Insteon SwichLinc dimmer via ISY. Mostly white 100%, bright, medium, dim. The colours get used for parties and mode setting for occasions and movies late at nights. Right now I have 10 reels of RGBWW on those controllers on a board for a furture pinwheel animation. I have written most of the code for them on a RPi3. Started on my RPi1 but that functions as a Node Server for ISY and I kept bugging it. I have most of my animations written and working and now just making mood lists to supervise the animation sequences. It runs from a 4 key mini-remote and also a duplicate screen from Tasker on any android machine. My suggestion. Order one from amazon, at their high price, and see if you can do anything with it using NR and then order a bunch on ebay for a much cheaper price. You have to really look around. Once they became ppopular the price went from $9 to $40 for some vendors. You should be able to see a list of parts in another thread I posted. What part of the world are you in?

It was an attempt at a pundle. I thought you would be right on top of V5. Have a look as this usage for the repeat while.... http://forum.universal-devices.com/topic/18921-v5-averaging-using-only-the-best-values/

Oh yeah. I am buried knee deep in lights and controllers here. Building a 23 strip animation controller for a tent ceiling. There are a few threads on this but the MagicHouse UFO = 4 channel, Scott is expereimenting with a 3 channel version right now. The ones I have found the best is the LEDenet 5 channel, (look for music controller). This is the same company as the ones above. They have RGBWW/CW outputs and can mix white with colours. Most can't like MiLights. I have bunch of them too. I woud avoid them. The Network Module inside ISY can control them without any other hardware. I have written python3 software for my RPi 1 I call NR bridge that can act as a bridge to do more things but it still takes the NR module to command it. The best part is the LEDenet (MagicHouse) brand is WiFi and no hub is required. MiLights demand a hub that can only control four "groups" FYI: The RGBWW 5050 strips run about $15, controllers $11-35 , then you need a PS 12v @ 3-5A $10, barrel plug adapter cable $1.50, 5 pin adapter cable to wire into the controllers = 10/$5. Oh yeah. Don't try to sticky a run of lights upside down. They just fall off every time. get the silicone clamps and tiny screws every 12" or less. 100/$5 All prices are Canadian and aproximate. NR, software and help all available here on the forum. This summer and fall I will have a surplus of these things I may want to get rid of.

Sure, but I am waiting for logic line enable trigger options first, well at least for a repeating while

Add an "end" to the pulldown menu list of times was suggested before. Repeat X times ...do something Repeat End Like any other language you have to learn the syntax and then use it.

Just your old fashioned "repeat until" loop that's been around for many years. Fairly standard, only with a few different words. The until is just repeat 1 (once). Totally intuitive, but intuitive is only relative to your experience. We weren't born programming via a keyboard. QWERTY? Really? I have used many different styles of languages. There is no "intuitive". There is no standard style of repeat. The admin console even indents the contents for you so you now where it begins and ends (even without those words Mr. Pascal). That is way past where I started programming. Now for the syntax quirk. You should love this one. ..."Repeat 1 times" doesn't repeat the loop at all. It only executes it once. Have a good one!

So if I read you correctly, the hardware at each end ie. PLM / ISY is wired differently to accomodate a cable, with identical pin numbers wired together. Is that not what you are calling "straight-through"? This is the way the original Ethernet hubs and switches were wired, but the cables would never be able to connect two hubs together, or two computers together. That was the "other" cable required with Tx wired to Rx. It was a mess for a while, and I think this has been since straightened out, similar to RS232 cables. Tx and Rx are always crossed or all connectors have auto crossover capabilities. As much as I have wired a few thousand RJ45 connectors, by hand for a fibre WAN system, I really have never studied the connection purposes of the pinouts.

Are the signal levels RS232 or logic levels? That would determine the capability of the signals. We know you can't connect Tx to Tx so something has to switch the connections. This means a straight through cable isn't going to work the same way as a real RS232 cable always needs pins 2 and 3 cross wired. (Tx to Rx, both directions) Sent from a tiny keyboard. Response may be brief.

Interesting. Although I have had a few Insteon comm failures, I have no repeaters, phase couplers, filters, or other devices that are not directly being used. I have two OutBack inverters running at all times with some Insteon running from their supplies, and my PLM plugged in right beside them.

I have found all decent Zwave devices are much more expensive than Insteon devices. People do their own bait and switch though. They look at the cheap Zwave devices that don't support status reporting or repeat etc., get enthused, and then upsell themselves the expensive ones because they are actually useful in a HA system. Next thing is a grid of repeater devices due to the RF only range. All looked good in the sales flyers when they sold off the bottom end devices.

I think B on both ends would twist the signals. To be straight through IIRC it takes B on one end and A on the other. ISY Tx = PLM Rx ISY Rx = PLM Tx B to B may connect Tx to Tx and Rx to Rx Since serial ports don't usually auto change connection function, like many Ethernet ports now, it probably shouldn't work.

If the heat pump is new I would ask the company to come back and tell them it is causing electrical noise on your system. They may have some simple fixes for it like.. Re-tighten some connections they did Install some toroids on the feeding conductors. Install MOVs across the feeding circuits. Install a whole 240v filter on the 240v and/or 120v. Use a disturbance/harmonic analyser to actually analyse the problem. My guess is this will cause you more problems down the road and may be combined with another newer noise maker and then it will get really hard to fix.

Just another thought.... I figure you know this, but the mechanical heat pump stats had two contacts, and the heat pump was set the highest temperature. A few degrees lower the back up heat contact would cut in, and usually some had an option to stop the heat-pump when the backup ran, or run both simultaneously. The two contact outputs are not confusing the issue of reporting differential I hope. This seems a little out-of-whack for a AC run stat. It's not like they need to save the batteries by reporting too often.

Some of us spent all our money earlier and aren't so lucky to have the latest units. It would be interesting to find out if the large reporting exception rule applies from the last update after a query. IOW: If the last temperature sent to ISY was 72F and you query it and it sends 74F, will the next report be at 76F (72+4) or 78F (74+4)? That would seem that a query before critical usage would be necessary each time. Trouble with that logic is that you don't know the time is critical until the stat reports in. duh! Another thought: Is there a time period report that the stat reports whatever it has every X minute/hours, regardless, or from the last report? Surely, SH would have gained some high level protocol intelligence by now.

If you are referring to the 2441(Z)TH Insteon thermostats, mine report in about every 1.5 degrees C.The local operation works on the resolution you see on the screen (0.5c) You cannot query the temperature from the stats. everything else, but not the temp. On just batteries you can't query anything IIRC.

The connectors on one end may be the wrong polarity style (A or . Most Ethernet will work with either cable style but serial won't.

Call UDI support. They will get you going.

My Venstar T7900 runs my humidifier in another room. When I built my house many people told me with such a tightly sealed house a humifier would never be necessary. I didn't leave enough room on my air-handler to accomodate a humidifier after-the-fact. Sure I discovered I don't need a humidifier if I don't mind dying in my sleep from fumes and lack of oxygen. HRV's bring in extremely dry air in the winter here. It's hard to get out of bed in the morning when the static on your hair is too strong to lift your head off the pillow, each morning. ISY's your friend.

IIRC there has been a few users that have adopted links using the "absorb" method and then they had a hard time getting the links to a non-existent Hub type device out of their ISY / PLM link tables. Now the devices are doing multiple retries to get an Insteon ACK from a device that will never respond.

I would be factory reseting each device and adding them to ISY. Once a process has been set up it doesn't take that long except for battery devices somewhat. This way you know you have a clean slate for each device. They can tend to act strangely if not cleaned out first, especially from the factory. I think you will enjoy the power of your ISY so much more, being able to do compound logic programs instead of just timer events or extension of device controls. I bought two hubs and once I saw what they could do I sent one back for a refund and gave the other one away. Welcome to the forum!

Two of my son's have Nest thermostats for the last year or more. Almost every feature it has has been disabled at one time or another. The Nest "learning mode" sets a new temperature for every time somebody fiddles with the dial. After about a year you have 20-40 temperature settings at random times of each day and you need to go and delete all the "learning without intelligence". Most Nests are reported to be way out of calibration by 3-6 degrees and from forum readings nobody thinks they can be adjusted to fix. IIRC tech support told users to leave them along as they are all calibrated at the factory and don't need any further calibration". Classic know nothing electronic toy company thinking and probably most of the reason it has to memorise so many temperature adjustments. My conclusion: Not for HA enthusiasts. We are control freaks and like things our own way, not the way google tells us "Don't worry! You will love this stat. Never mind what it does." "Would you like fries / Chrome with that stat?"

You may have to quote Stu's text to get his attention like I just did to you.

All the date/time functions are there but they can't be used in the logic. If they were, the ISY engine would have to evaluate every second or minute. Something to be noted: Dates spanning the end of the year must use OR logic. Dates spanning inside the year must use AND logic. I've been caught too many times on this so I thought I should mention it. (examples already in my second program) The decimal was just for looks.

I see you have v5 installed. I use this variable creator to access dates without year restrictions (wild card). I use time program kickers to ensure it gets updated after power failures and other glitches. Set MM.DD - [ID 00B8][Parent 0006] If Time is 12:00:01AM Or Time is 3:00:01AM Or Time is 6:00:01AM Then $sISY.DayOfWeek = [Current Day of Week] $sISY.DayOfMonth = [Current Day of Month] $ISY_Date.scratchpad = [Current Day of Month] $ISY_Date.scratchpad /= 100 $ISY_Date.scratchpad += [Current Month (Jan=1, Feb=2, etc.)] $sISY.MM.DD = $ISY_Date.scratchpad Else - No Actions - (To add one, press 'Action') Then programming around dates is quite easy and permanent. No yearly changes required. Foyer Christmas Tree - [ID 00BA][Parent 00C0] If ( ( Time is Sunset - 30 minutes And ( $sISY.MM.DD >= 11.15 Or $sISY.MM.DD <= 1.06 ) ) Or ( Time is 5:00:00AM And $sISY.MM.DD >= 12.24 And $sISY.MM.DD <= 12.26 ) Or 'Master Bedroom / MBR KeyPad.C' is switched On ) And 'Master Bedroom / MBR KeyPad.C' is not switched Off Then Wait 1 second Set 'Foyer / Foyer Christmas Tree' On Wait 8 hours Run Program 'Foyer Christmas Tree' (Else Path) Else Wait 1 second Set 'Foyer / Foyer Christmas Tree' Off

The delete all links doesn't seem to do it for me and that is only incurred when linking a device not known to ISY. The factory reset (Paul's advice) of each device and restore is quick and easy and the factory reset clears out locked up program routines and data in the devices. No unassociation required in ISY.