MWareman

Benoit, It's still hanging for me at the same place. So that you know, this is just Chrome on Android - nothing exotic. Michael.

Benoit, Success at attaching a debug session (didn't know you could do that!). However, there are no javascript errors... After I click 'Login' I see a 'POST' from XMLHttpRequest to /api/login containing my username and password as form data. The ISY responds simply with a '200 OK' response. Then XMLHttpRequest makes a GET to /api/domains with a basic Authorization header (my encoded username and password). I get back '304 Not Modified'. Next - the browser (from within portal.css) issues a GET to /images/refresh_white.png. Portal responds with '304 Not Modified'. Then there is a request by XMLHttpRequest to /api/isys?domain=xxxx&subaccounts=false (again with a basic authorization header with my username and password). The Portal never responds.. It just shows 'Pending'. The browser just 'spins' and the processor get's warm.. I've attached a screen image. Michael.

Apologies, I didn't get time to setup the debug session today. I'll try again tonight at home. Michael.

Benoit, What Android version are you using to test? I'm on a Nexus 9, 6.0.1. I'll setup the remote debugger when I get to the office (traveling now...) Also, a poster above reported an access issue with his iPad mini - don't know if its the same issue though. (Edit: Just tried Safari and Chrome on my iPad 9.0.2 and it worked fine in both). Michael.

The 5050 RGBWW is what I have, and I find I need to 'cool' the warm white a little with a dim blue color mix. The warm white is just too yellow otherwise. In my case though I have pulled wires down to my basement and the power brick is down there - keeps the kitchen clean. Did it the same time I tiled the back splash in my kitchen.

On 2, many do not seem to be 'initiated' by the PLM, but the collision occurs and the devices themselves see a corrupted packet that they interpret as an 'ALL-ON'. The PLM has no knowledge this occurred, even though a signal it sent was the cause. This may be why the ISY never sees it. Given that the ISY is never aware of this (according to overwelming evidence), programs will not trigger. This is good. Finally, if you are going to hook control up to the Elk, why wouldn't you hook the sensor up to Elk as well on a zone (point 6) - and benefit from the garage door triggering the Entry 2 entry delay (which can be longer that your front door entry delay). That way, anyone using the hook 'trick' (or other forced entry) to open your garage door by releasing the emergency lever will still trigger the alarm? In my case, my night arm scenes will trigger immediately, no entry delay at all.

I've also been using the milight stuff - also fairly reliable, but having the controller being separate from the WiFi bridge is just kind of annoying me. I'm eagerly awaiting zwave multi-channel and I'm switching over to a Fibaro controller. Still the same LED strios, just a zwave interface to ISY.

This. No reason not to! It's *so much better* to say 'Alexa, turn on the kitchen light' and get 'OK' back instead of 'Alexa, tell Izzy to turn on the kitchen light' and maybe it will work, but have it respond 20% of the time that it couldn't find the device due to the Izzy not being heard properly and the request getting misrouted. Much, much better now!

From memory... For the Elk, I wired the mag sensor to an alarm zone - configured as an 'Entry 2' zone (I think... in my case). I have a longer entry time associated with this (when I arrive home and open the door, a longer entry delay starts. When you open the door to the house, the entry delay sharply shortens). With the Elk module on ISY, I trigger the garage light from the door being opened, and turn it off 2 mins after the door is closed. To control, I have an output wired to a remote button (I have a Chamberlain MyQ enabled door and then smart button - I cannot wire directly to the GDO). Basically, you wire the output in the same way the IOLinc was wired to the GDO. I configured a rule on the Elk - when output 65 turns on, turn on output 3, wait 1 second, turn off output three, turn off output 65. On ISY, all I need to do is turn on Elk output 3 to open or close the door.

Glad to see I'm not the only one. I've confirmed I'm not blocking JavaScript from executing on the portal.

Of course you can have a program (ProgA) with a 'RunIf' (ProgB) clause in the 'Then' section. Assign a spoken name to 'ProgA' and when you 'turn on ProgA' the 'if' clause of ProgB will be executed. Not ideal and messy - but possible. Personally, for 'If' program triggering I would stick with the skill. This may be a use case for virtual devices. Assign a spoken name to a virtual device and use them in a 'If' statement to trigger it. I'm not sure if UDI is any closer to implementing virtual devices though. Also, does Portal recognise nodes from node servers external to ISY (and let you assign spoken names)? I don't have this going yet, but am interested in knowing.

If you want to use local HTTP, create a second profile in Mobilinc. Don't configure the HTTP settings in the same profile that the portal is configured.

Don't do that anymore. For Alexa, all spoken words are managed in the portal, and the portal spoken words do not sync with the ISY spoken words. When managing in the portal, a sync is unnecessary. I also had the error about linking when I first added the connected home module. I logged out and back in to the portal and have not had it since. Michael.

Mines a Nexus 9 running Android 6.

Same here on my Android tablet (with Chrome). Hangs as the screenshot after authentication...

It's been a while - I hope I get this right.... In this case, 'is on' will trigger 'Then' when 'on' is pressed and 'not off' will trigger the 'Else' to run if the switch is turned off. Without the second clause, the 'Else' will never run when the light is switched off - only the 'Then' when the switch is turned on - which makes the program useless for status. Michael.

That may be why my fanlinc programs are not working... I wonder why this is? Can I set the device and call a scene (so the kpl gets updated)? More experiments to do tonight...

Very impressed so far. Very fast. Alexa simply responds 'OK' - usually after the desired action has taken place. I've created some device groups in Alexa - looks like that can be used to create aliases that Alexa will understand - since a group can contain one object. Michael.

Yeah, you'll need that to utilize that built in function. Otherwise you can send emails and write an email parser, but I suspect the network module will be much better for your need, and it will open up all kinds of additional capability to you.

Just found out you can discover from the app. Who knew! My devices discovered - even a program I have a spoken name attached to. I'll give them a try tonight. For the poster that asked for an easy list, once the ISY is connected you get a list of all devices (with their spoken name attribute) right in the Alexa app after they are discovered. Nice!

Woot! Thank you Michel and Benoit. Awesome job! Got my account all linked up, and ISY is showing up in my Alexa connected home settings. I just need to get home now to do a device discovery. Only one thing, I love the ! In the description....

Thank-you!! I also like the new button layout when added spoken names. Very slick. Michael.

Correct. In order to do a cloud to device notification to be consumed by the Mobilinc application, UDI would need access to the private application keys for Mobilinc's Apple server connection. Mobilinc would have to provide UDI an API that the ISY portal could connect to to securely send a notification. I doubt that's going to happen any time soon, but I could be wrong...

Also, there 5.x is early beta. I wouldn't recommend it yet for production use unless your willing to tolerate caveats for a while.

It could indicate a going-bad PLM missing link records. Try right-clicking the PLM (in the Admin Console) and clicking 'Restore'. That will put back any missing records. You can then test (the web interface is fairly authoritative). If that was the problem, plan to replace (or repair) your PLM shortly. How old is it?