asbril

In the launch App (start) you have the option of the Dashboard or the Administrative Console.

Maybe it has something to do with the changed graphics of this forum that I noticed yesterday. But I have not checked Tapatalk.

Pushover gets to my phone probably 1 or 2 seconds earlier than the ISY email. It puzzles me a bit because with the same motion sensor it takes a couple of seconds longer to switch ON a lamp and same for Alexa announcement.

I use both the notification built into ISY and Pushover. I believe that Pushover is slightly faster but there is not a big difference. For the built-in notification I use my phone nr xxx.xxxx@tmomail.com (Tmobile).

When I moved from 5.0.16 to 5.2 I did not have that issue. It was pretty smooth.

The Kasa device hat I added earlier today has the green "writing" in permanence, but the event viewer shows no activity for the device, other than 100 when ON and 0 when OFF.

After reading the above posts I purchased a $ 9 Kasa plug, installed the Kasa Nodeserver and I am surprised how well this works. It took me while to connect the plug to the Kasa App (IOS) because my Google Wifi router defaults to 5 ghz, but got it working after a few tries. This seems to be a decent alternative for those wanting to save a few $$.

Thanks. Generally my Zwave network ( more than 70 devices, a few 3, most 5 series) works fine with 5.2 and the 500 dongle. Since the 5.2 upgrade I get more communication error messages, but in fact the devices continue to work.

Thanks @blueman2 but does this not assume that all the devices must be Gen5 ?

How do you do that ? I don't see the heal network anymore.

I have created some programs and this is my view of the Ilumin bulb by Inovelli. First a big positive is that you do not need a nodeserver..... There are 4 basic colors (white, red, green and blue). White is either 'warm' or 'cold'. You can "mix" the colors but less practical and efficient than my Lifx bulbs. I wanted to use the Ilumin bulb in a program reacting to motion in sensors; a series of ON and OFF in blue acting on sensor 1 and in red acting on sensor 2. However, it takes a couple of seconds to go ON and because OFF comes with fading I was unable to create the flash effect that I wanted. So instead of the flashing effect (repeated ON/OFF) I just set the bulb ON for 20 seconds when activated by a sensor. In conclusion, the Lifx bulbs are more colorful (pun intended....), but for the Ilumin you don't need a nodeserver. The Ilumin are cheaper than Lifx.

I just received the ilumin bulb (discounted without packaging) and it seems to work great with colors. Tomorrow I am going to include it in a program and will keep you posted on performance.

The question I have is about the new nodes created by 5.2 . It created more than new 100 nodes for my more than Zwave devices. I have ISY Pro but may these new nodes make me exceed the maximum nr of nodes ?

@blueman2 This is pretty similar to what I have been posting / asking about. I used to distinguish between STATUS and CONTROL (switch) in my programs. If I use in IF Status, then the THEN acts whether I manually click on the switch or when the switch is activated in the Administrative Console. On the other hand when using CONTROL in IF in a program, the THEN only works when manually activated on the switch. This worked great before 5.2, but no longer. @Chris Jahn suggested to use the Custom Button node, but that works partially and can mess up a program. It would really be nice if 5.3 can bring back the previous operation of CONTROL.

remember how Apple was almost on the brink, before the return of Steve Jobs and the Iphone, when their superior MAC lost to Windows because of their closed OS ?

Please allow me a "side-track" question on wifi plugs. A family member has a secondary home near me where they don't go very often. They have a Foscam camera to monitor the home remotely but occasionally the camera logs off and then they ask me to go there and power cycle the camera for it to get wifi again. I am wondering if I put the camera on a wifi plug, can they then (with an App) power cycle the camera remotely. If that works, what wifi plug would you recommend?

I think that you are right, except maybe for the speed. You have pointed out in past comments that Insteon devices react faster to each other. And indeed in some instances it can take a couple of seconds for a light to react to a sensor. Maybe that would improve with 700.

Yes they are...... Great for those starting Zwave from scratch, a bit frustrating for those already with many Zwave devices. Should I wait for 900 ??

If people follow this advise then there is no reason not to go to 5.X

I respect your viewpoint and I understand your use is professional, which is different. However, I can not imagine myself not using 5.X until final version and losing out on the nodeservers that have made a huge difference for me.

Respectfully, I am surprised by comments like this. 5.0.X has been performing well for me almost from the beginning and usually an upgrade just brings new features. A few times an update with new features actually created some issues which were then addressed in the following update. In fact for me 5.1.0 did not work and I went back to 5.0.16 before installing 5.2.0 which works great. As someone else commented, for most of us 5.1.0 and 5.2.0 are like 5.0.17 and 5.0.18 . It is not about the numbers but about the ISY working fine. What I am trying to say is that it is not worth waiting for the final release before updating your ISY. Assuming, just to make the point, that 5.3 is the final release, I doubt that you will find major differences, while staying on 4.X and waiting for final release of 5 means losing out on major features that have been working fine since the early stages of 5.0.X

I have a ton of these and I moved them to a folders that I named "phantom nodes"

I remember that when I received the 500 dongle, it came with instructions.

Earlier tonight I posted something in 'create a 3 way' where I wrote about a program not working with IF X is switched ON; THEN set Y ON. I noted that it does work when using IF Status X is ON instead of Switch (Control). I just realized that one of my programs was no longer working and it does indeed have IF Control X and not Status. This worked fine before and now I wonder whether something was changed in 5.2 which makes it that Control (Switch) no longer works. I apologize if I get it wrong, but could there be a bug here ?

Yes you can. Right click on device; 'Zwave'; 'Show Information in Event Viewer'.; 'Node Details' . In the Event Viewer ('Tools'; 'Diagnostics') scroll up and you see either Zwave Basic or Zwave Plus. In some cases there is neither, but I am pretty sure that those are not Zwave Plus.