MWareman

Uses the same spokens as Alexa. Initial tests look good, except that I assigned all devices near my family room to the 'Family Room' room. I had a device with a spoken of 'Family Room'. When I asked Home to turn on 'Family Room' she replied 'ok, turning on 14 devices in family Room'. Ouch.. a self inflicted regional-on... Renaming the device with the same name as the room solved this... Congratulations to all at UDI!

Universal Devices in the Gogle Home home control selections. Woot!!

Woot! It's alive!! Just link your Google Home app to your ISY Portao account and you are good to go. I see that Mobilinc Connect is approved as well, so whatever flavor of portal you have should work. Sweet!

Seems overkill for the need. Why not remove your 'responder' kpl buttons from their scenes and re-add them as 'controllers'. That way, whenever they are pressed they will control the scene, causing the other scene member kpls to be directly updated?

Other thing I note. This is RGB, not RGBW or RGBWW. Do you know of the same thing with 4 or 5 channels? Sent from my iPad using Tapatalk

Interesting. Do you have a link to the firmware needed to enable this?

Today I preordered the weatherflow weather station.... its time for some hyper-local weather... Sent from my iPad using Tapatalk

Well, a solid zwave network should start with two or three non-battery devices, ideally devices not in a grounded electrical box that also support encryption and beaming. Even if you don't need noise makers, the Aeotec Siren makes a really good network builder. Then start adding other devices.... Also to note, the central scene support in ISY is very new (5.x)... Sent from my iPad using Tapatalk

The homeseer dimmer supports the central scene class, and has double and triple tap scenes that can drive different events... Sent from my iPad using Tapatalk

The Android and IOS locative apps are open source.... So their use should not be impacted at all... Sent from my iPad using Tapatalk

It was reported that the portal does not yet support it, and if you are a portal user chunked encoding should not be enabled yet.

I guess I should have seen this in in the other thread. Anyway, it deserves its own either way...

On my way home to rest this. Anyone able to try it yet? https://blog.google/products/assistant/tomato-tomahto-google-home-now-supports-multiple-users/ Supposedly, you train our voice into a neural net, and it uses that to recognise who is speaking. Pretty sweet if it works!

With Gmail, not be not do you need an app specific password - but you also need to enable 'less secure' apps. Otherwise, authentication won't work. https://support.google.com/accounts/answer/6010255?hl=en

ISY was was tested for verification without an external antenna. All an external antenna will do is make the signal more directional - which may help in some situations for some people, but for most people is makes things worse. I'm another one that had several Aeon repeaters. Utter trash. Didn't help at all. The Aeon siren on the other hand works as an flawless repeater. I highly recomend using the Siren instead of Repeater.

Run a level 3 log, and perform a test. The next most possible issues is either a DNS or crypto issue. The log should say more...

A common problem is not having something in both the subject AND the body. If either have no string in them the email won't get sent.

Possibly one of these? http://www.smarthome.com/insteon-2342-222-mini-remote-8-scene.html Anyway, if the OP would say the flavor of 'smart phone' I'm sure we could have better advise. IOS, Mobilinc for sure. Android, look at Agave. Windows Phone, I'm sorry. Got nothin'. Edit: DYAC

Reading the post, it seems to me that OP may have manually created links by cross linking switches, and not performing all the needed cross-links. If this is the case, a scene should he created in ISY and then a restore performed on the devices. Devices should not be manually linked when an ISY is in control...

Nice! Had my Mavic for a couple of months now. It's awesome! Just don't forget to let it hover for 30 seconds after taking off (to properly image the takeoff point for an accurate RTH) and make sure you sent the RTH minimum height to clear all surrounding obstacles. Oh, don't forget FAA registration and attach the registration ID...

If you buy the network module before buying the portal, once the portal subscription expires you will still have the network module. If you didn't (and got the network module with a portal subscription), then the network module will stop working when the portal subscription expires. You should be able to just buy the network module independently then. There were some users who had purchased the network module before the portal was available who were offered trading in the module for (I believe) an extra year of portal Anyone that took up that offer converted to a subscription tied network module. It also would expire on an expired portal subscription.

Not currently. I'm using concatenations of built in phrases that Elk supports. It works for the most part.

Welcome to the Pi club! I just replaced all my 5 year old Atom systems (with Nvidia chipsets) running my MythTV front ends with Raspberry Pi systems doing same. What cost me $300/tv 5 years ago was replaced for $60/tv, including a neat vesa case/mount. It's nice to have systems that are fanless, silent and with *much* lower power consumption..... and (finally) have my MythTV frontends be able to talk CEC to the tv.... I believe I'm now up to 12 Pis running on my network...

Just to confirm from our PM discussion. I only got 404 when testing not from a browser because I was issuing a GET. Portal requires a POST. The actual error was something else (5xx) and it looks oks like this was caused by my ISY being offline (dns issues). A reboot of the ISY solved the issue. What was odd was my extensive Pushover notifications were all working fine, so it took a while before I thought to look presentable n the dns client direction. Seems ISY was able to generally resolve DNS, just couldn't resolve the Portals address... Not sure why... So, issue resolved by rebooting ISY...

Yeah, I know what 404 mans. It's just that the rule was working for a couple of months f months, stopped working (with 404) for a few days, then started working again - all without changing the URL at all. So, something must have changed portal side...