carealtor

And if I'm honest, I'm feeling rather duped for buying a Polisy. Had I known there was any question whatsoever about it supporting Insteon, I never would have been an early adopter. As it is, I've had the Polisy for over 8 months waiting for the changeover. I had Polyglot happily running on a VM, but I was excited about the prospect of everything in one box (some day) and I wanted to support UD, so I purchased the Polisy. Now, as I already said, I'm feeling a bit duped, but I will continue to wait, and now hope. In fairness to Michel, I will say, I didn't realize until this thread that there was no support from Smartlabs, and that the Insteon integration was reverse engineered. What a pain that has to be. Grateful to Michel and crew for all the work over the years.

@jmwhite5 What kind of range are you getting from the Bond (to the Somfy blinds)? I might go this route. Just doing a little research, it seems z-wave is pretty popular for blinds. But I have no z-wave so I know I will be in a nightmare situation trying to get a z-wave blind to work.

@Michel Kohanim Of course, your company, your choice, but I really hope you continue supporting Insteon.

I'm trying to set up Occupancy on ISY Portal. I can only get as far as Configure Connection and I get a window that only says "HTTP error 400".

No, it doesn't connect. But it sure seems like it should (layman's opinion), since the Home Assistant Emulated Hue connects easily.

No. Seems everyone is too busy to look into this for us.

I'm on 5.3.0 and don't have this issue. Just sayin'

Since he referred to "default" he must be trying to use Adjust Scene, which probably is indeed not what he wants. I've always wondered what the use case is for Adjust Scene? If you want a group of lights to do different things, wouldn't/shouldn't you create multiple scenes instead of trying to "adjust" the one scene?

You don't need to (and probably don't want to) enable program B in order to run it. Just make a call to run it while still disabled.

That just sent a chill down my spine. Guess what project I've been working on of late.

Hue Emulator will do exactly this, but only for "Home Control" buttons on your remote. You didn't say what remote you have, but I know this will work for the Elite and newer Companion remotes. To map to the the rest of the buttons is entirely different problem. I've seen other home automation systems where someone has written a "Roku Emulator" that will do this, but I haven't really played with any of them. Someone would have to write a "Roku Emulator" nodeserver for ISY, but nobody has yet.

I've gotten my last couple of PLMs from SmartEnit. They are functionally equivalent to the old 2412S. Con is that it's not dual band. Pro is you can power your ISY through it, thus no need for a wall wart. I don't know if they are still in stock, but I didn't see any out of stock notice on their website.

Does this mean Mobilinc and Agave are obsolete now?

Just to close the loop... I fired it up again, it asked if I wanted to sync, I said yes. No errors this time and everything looks right at quick glance. Great work on this! Thanks!

I think I'm going to wait and let it mature a little bit before diving into it any more. Thanks for the work on this.

Tons of error messages. It never did finish sync and I ended up canceling the sync. Just providing feedback. Not complaining.

I'm in no way disagreeing with you, but I am curious what capability you are referring to? I want for (almost) nothing in my system, but maybe I'm missing out on something.

I'm in the same boat. I went ahead and upgraded to 5.3 just because I like my stuff to be up to date. There are no issues with doing so. I still have the 300 board and it isn't causing a problem.

@Retrofit There is no issue with setting the LED Brightness via the ISY with programs. The bug discussed here is with displaying the current value in the ISY admin console. Also, the bug still has not been fixed.

@gzahar I'm on the latest and greatest version of everything. I just did some testing with rebooting ISY and there does indeed seem to be an issue there. My false-positive shows up whenever I reboot the ISY. What I can't say for sure is if this is the only time it shows up. What I am also noticing is that the Sonos Nodeserver is not showing any Status (it is blank) for this player after ISY reboot. Yet the condition "is Playing" is returning true.

@Michel Kohanim I just had the same thing happen again. The program had a green strip even though the condition(s) were all false. I manually "Run(If) and it stayed green. I highlighted a line in the program and hit "Update" (without making any changes), and then hit "Save Changes". Now it will show red (correctly) and "Run(If)" turns off the WHA. I believe it has something to do with the Sonos nodeserver as this is the only program that is giving me this issue.

I set up 3 programs to separate the 3 conditions in my "real" program so I could see which one was causing the problem. The problem exists both in my "real" program, and when I manually Run(If) the disabled program. What is so interesting, as I said in the first post, is that forcing the program to re-save will fix the problem.

I'm really surprised that nobody finds it interesting that there is a very obvious logic flaw here.

I'm not sure if this is an ISY issue or an issue with the Sonos (not cloud SonosController) Polyglot. It only happens with this one program and it involves the Sonos Polyglot. I have it set up so the whole house amplifier (WHA) turns on if Sonos is playing. It works, but every several days I notice the WHA is on when it shouldn't be. As you can see, the player is Stopped, but the program shows as green. If I "Run(If)", it still shows green. What ends up fixing it is to resave the program by picking any line in the program, hitting "Update" (without making any changes), and then hitting "Save Changes". Now it will show red (correctly) and "Run(If)" will turn off the WHA.

I upgraded to 5.2.0 with an old Z-Wave module and everything is fine. I have zero Z-Wave modules, so, YMMV.