Guy Lavoie

That's known. For ssh, try ssh admin@<ipaddress>

For anyone trying to log in with ssh, the usual "ssh admin@eisy.local" doesn't work (gives can't resolve error), but I got in by doing "ssh admin@<ip address>"

Wait, there's more! I got in by doing "ssh admin@192.168.0.137" (the IP address)

You can't fault their support, though I did report a bug last April and it hasn't been fixed. Maybe they're waiting to incorporate a fix into their next update. The bug is that if you have an external temperature sensor and set the thermostat to use it as it's operating sensor, the thermostat works fine. But if you ask Alexa what the temperature is, it gives you the temperature of the thermostat's internal sensor.

Same here (I upgraded my test Polisy, I'll do my eisy once the new version kinks are worked out), but the admin console logs in fine. I now see the new "Matter" heading, after turning Matter support On in Configuration. My Polisy has the zmatter board in it.

Now that it's officially out, lets discuss our observations and questions. My question is about this in the release posting: - Matter Initial support for light bulbs and plugin modules: -- WiFi direct. -- WiFi through a Border Router such as Google Nest Hub or Apple HomePod. -- Thread through a Border Router. Where does that leave the Zmatter dongle? Not functional yet, something else?

The mention of 5.9.1 has popped up a few times recently, so having UDI work directly on your system is probably the reason. The last missing piece is probably just days away.

If the old one is a ISY994i, it might be worth trying the SD card contact clean and reseating procedure. Getting the old device list would certainly be a huge timesaver.

I just tried upgrading packages and firmware on my test controller (Polisy) and it still says OS13.1 and IoX 5.8.4. Maybe you requested to be part of a test group?

What IoX version are you seeing?

It's out? (here comes the storm!) Well it was mentioned in the announcement that adding devices could be done from the mobile application. Maybe that's the only way (for now?).

From the first post, I get a sense that the previous controller wasn't a UDI controller at all.

No, I meant an incrementing variable. Simply because that's the type I was used to, and how timers worked in the Ocelot controller. They can be made to work both ways. In your sample program, you're only really replacing a Wait statement. The things I use timers for are more for timings between programs, or actions. Things that a single program can't do. I'll give two examples, in pseudo code to keep it short. 1- Implement a "fast on" functionality for a device that doesn't have that built in. I'd do this with X-10 switches on the Ocelot. If you turn the switch on again within 3 seconds, do a secondary function: If Control Switch ON And Timer > 0 Then do secondary function Then Timer = 0 If Control Switch ON And Timer = 0 Then Timer = 1 (start the timer) If Timer > 3 Then Timer = 0 Now the problem with IoX is that you don't know what order the programs are executed in, so if the second program above is actually executed before the first one, then secondary function will trigger every time, because the timer was just set to greater than zero by the program executed previous to it, so additional code could be needed. 2- A more concrete example is the good ole bathroom fan timer application. I actually have this programmed in my eisy, so I'll post the actual code (minus the empty Else statements). It's four programs: G2 toilette 1 fan debut - [ID 0010][Parent 0016] If 'T2 Toilette Fan' Status is On And 'Timers / t0_toilette' raw data 0 is 0 Then $iT2_toilette_temps = 600 Set 'Timers / t0_toilette' Raw value 1 G2 toilette 2 fan ajout temps - [ID 0007][Parent 0016] If 'T2 Toilette Fan' is switched On And 'Timers / t0_toilette' raw data 0 > 0 And $iT2_toilette_temps < 1080 Then $iT2_toilette_temps += 240 G2 toilette 3 fan fin - [ID 0008][Parent 0016] If 'Timers / t0_toilette' raw data 0 > '$iT2_toilette_temps Raw' Then Set 'Timers / t0_toilette' Raw value 0 $iT2_toilette_temps = 0 Set 'T2 Toilette Fan' Off G2 toilette 4 fan off manuel - [ID 0006][Parent 0016] If 'T2 Toilette Fan' Status is Off Then $iT2_toilette_temps = 0 Set 'Timers / t0_toilette' Raw value 0 The names are in French but I think it's easy enough to see what it does. Prog 1: Turning on the bathroom fan the first time starts the timer, and sets the desired time variable to a default 600 seconds (10 minutes). Prog 2: Pressing the On switch again while the timer is running adds another 4 minutes (240 seconds) and you can do that twice (for those big bathroom jobs...) for a maximum for 18 minutes. Prog 3: stops the fan when the timer finally exceeds the desired value, and resets the timer and variable. Prog 4: resets the timer and variable if the fan is turned off manually. The "Timers / t0_toilette' raw data:" statements look like that because my timers are actually a plugin (my first plugin!) so there is no program to do an auto incrementing variable like in my first post. The nodes look like this in IoX If I want to make a self stopping timer, I can set it to a negative number (eg: -5) and it then increments towards 0 and stops on it's own. One tricky thing with the timers is that they're "clock aligned", so they increment when the clock rolls over to the next second. This makes the first count vary in length from almost nothing to almost one second. Good to know if programming very short timings.

Last spring, Venstar actually shipped me a SD card to perform updates on my three T7900s, for free. The online updates don't seem to be functional anymore.

I think he meant keypads in a general sense (wall switches and/or keypadlincs. He says 60 to 75 total Insteon devices in his initial post.

The device itself is a MeLE Mini PC. So did you look at your router's device table and it doesn't appear? Have you tried more than one network cable and router port?

I think it's just a variable that's named "Timer", and is being used to set a light level percentage in this case. There is no built-in timer function. You can cycle through the "Set" command options by clicking on the "Click to specify" triangle below the device name. That said, there is a way to make such a timer, using a simple program. I just created a state variable called Timer, and made this program: If $Timer > 0 Then Wait 1 second $Timer += 1 Now, if you set this variable to a value other than 0, it will increment once per second. You can use this to have one program trigger another one later, or test for a time interval between two triggering events., or measure the time between them. An additional advantage is that it won't die if the triggering program becomes false, like a "Wait" does, if that is what you need.

If you see several keypadlincs in the home, it would be best to link those first (and selecting "Add devices found in links and keep existing links"). Keypadlincs are there to control several other devices, and often the less obvious ones like fanlincs and other devices with no local buttons. No on;y that, but you'll be able to visually correlate the individual buttons with what they actually control, and match them up with the imported devices.

Ouch, sounds like quite a project. You will need two things: patience...and more patience.

Interesting that of all the switches you mention, only the ones controlling fans are acting up. If you turn them on and off from the admin console (or better yet, from UD mobile in those rooms if you have that) do they miss commands?

Well, there is one more test you could try to see if the timeserver process might be involved. It's to kill the ntpd process. No worries, I tried this on my spare Polisy that I use for testing. A reboot will restart it normally. Again, ssh to the Polisy and do this: ps -aux | grep ntp (that vertical bar is the pipe character, usually over the backslash on your keybpard) You should get two lines of output. One of them will start with ntpd and the next field is a number, the process id. Lets say for example that it's 1125 (what I see on mine) Then you do: sudo kill 1125 (use your actual process id...) You will be prompted for a password. Enter the admin password. This stops ntpd (network time protocol daemon) Confirm that it's not running by redoing the ps -aux... command above. Once that is done, redo your networking tests that would cause IoX to restart and see if it still happens. Then reboot your Polisy to put it back to normal. Tell us if anything changes.

I see, it's an amplifier specifically designed for thermocouples. The output is SPI serial. I've done SPI with a 8051 microcontroller (showing my age!).

Are the switches dual band or powerline only? Also, when a fan is running, do the communications for other devices also seem less reliable? Motors can cause electrical noise, which doesn't help.

So what exactly are you reading with the amplifier, a voltage? What is the voltage range? I imagine that the output impedance of a thermocouple is pretty high, so a very high input impedance is needed for the amplifier. And the Raspberry pi is providing an analog to digital input? A description and/or block diagram would be interesting.