MWareman

That’s probably a symptom of the device you are controlling not telling ISY that the device has changed state (as it was put to market before the patent that protected the idea expired). Before the patent expired, devices used various workarounds and not all of the workarounds work anymore. Best way is probably to modify your spoken to drive a program in ISY (instead of the device directly) and have the program turn the fan on or off. That way (since the ISY is controlling the fan) it will update the status.

Unfortunately, one of the limitations (of Ring) is that you cannot directly get an image from the camera. There is a functionality request formerly submitted to their team to add this functionality - but it's not there yet. I have a separate Foscam that looks out the sidelight of my front door. This resource I reference is a network resource that calls a .php script on my internal server. This .php script obtains a snapshot from the Foscam camera and sends it as an attachment to my Pushover account.

On Windows machines, you can add a secondary IP address to the network stack - so your computer can communicate on either IP network. Then, use the old IP to access the ISY with the Admin Console, then logon and Change the IP of ISY.

That almost always causes issues. If you have not disabled the 3am “Query All”, you will get the state reversing at this time. This is because trigger reverse causes notifications from the sensor triggering to be reversed, but the answer to a query will not be reversed. Of course, you can disable the 3am query. But then devices can get out of sync and will not get get synced up until the device is triggered.

The Ring devices that use the hub were purchased by Rng and use a different protocol. They modified things to have them work with the same app but likely work very differently to the Ring native spotlights and floodlights that don’t need the hub. How to they show up in the PGC log?

That’s awesome. Especially if a javascript function can be pushed down to th google home devices to process spoken commands locally and make relevant api calls directly to the ISY. That way, if the Internet connection goes down the Google Home integrations will still function - at least those driving ISY devices, scenes and programs.

@TomL - you would need to start by posting the log from the nodeserver so it can be seen how the devices differ (during setup). Further - when motion events are detected there will also be log activity. Those events would be needed as well. I cannot speak to @bmercier's time commitments though...

I don’t have any of the devices that use the bridge, but recently worked with Benoit to add lighting support to the Ring nodeserver for the native Ring devices that have lights (the Floodlight and Spotlight cams). If you have the devices, why don’t you give it a go?

Agreed on the IOLinc. That's a neat device where the device you are monitoring produces audio. Personally - I'd still prefer hardwired for safety of life systems (I have devices wired to my Elk generally as non-alarm zones - but setup to call my phone if violated). What I couldn't remember earlier was the zwave product I'm using with much greater success (compared to IOLinc devices) in some places in my home - the Fortrezz Mimo2 (https://www.amazon.com/FortrezZ-Z-WavePlus-MiMO2-Interface-Module/dp/B008D5066C/ref=sr_1_10).

There are some gas leak detectors out there with dry contact outputs (like this one: https://www.amazon.com/dp/B07Q3567DZ/ref=cm_sw_r_cp_tai_Sv7hDb0WVCYHX). You could hook the dry contact output up to an iolinc or zwave equivalent to connect to the ISY - or connect to a zone on an Elk panel.

I do not know about any devices outside of the devices I have. None are battery powered, not do I have any of the first gen stick-up cams. I suspect they would be fine. If not, the nodeserver log will contain the details necessary for the events to be captured.

After installing the nodeserver - you should get a blue notification in PolyGlot Cloud prompting you to authenticate to your ring account to provide access. It asks for 'Read' access - but this is all that's needed for the nodeserver to send commands. The really important thing to know is: When authenticating to your Ring account - you *MUST* use your primary Ring account username and password. Secondary accounts (or devices shared to you from another account) will show as nodes - but will NOT receive events. This is a limitation of the Ring API I am told. The nodeserver does NOT see or store your Ring password. The integration uses a technology called 'oAuth 2' to authenticate - which keeps your Ring password safe. After linking - your Ring nodes are pulled in: The 'Front Door' device is the doorbell. It has two nodes - a 'Motion' node and a 'Ding' node. Flood and Spot lights show two nodes and the newer stick up cams show one (they have no light). You can then create a program and use these two events to trigger it.. Here is one for the 'Ding' (bell-push): and one for motion events: For Ring light control (the flood and spot lights), I have a micro-module behind a conventional switch that is used to drive the outdoor lights at the rear of my house. I added controlling the Ring lights to this with the following two programs. The first tracks the state of the switch - turning the Ring lights on if switched on, and off when switched off. It also updates a variable used to track what state I want the Ring lights in.. The second program triggers on the variable being set to 1 - and repeats as long as the variable is 1: This is to override the ring behavior that turns the light off after a couple of minutes when I want the lights to stay on.. Michael.

Well - the latest I have is the issue I was having is solved - it appears to be working to the capability of the API... ISY can easily drive programs based on dings or motion events. Additionally, you can turn Ring Flood or Spot lights on or off (but not tell their current state). I'm in the process of migrating some of my programs over (I currently use some motion sensors outside in some areas that I'm going to replace with Ring motion detect events) and so far I'm getting programs triggering a second or two faster than triggering from motion sensor events. Pretty slick! The only downside - the Ring API does not provide details of which motion zone the motion was detected in. So - to automate from events you are going to need to reduce the detection zones to limit the number of events generated. Otherwise - you'll be triggering events whenever a car passes on the street... Might just be worth a try now!

It’s not as black and white as that. It’s as secure as your username/password is. Use a strong, high entropy password and it’s very secure and safe to expose. Most don’t want to do that (prefer the convenience of a shorter or easier to remember password) and against this no system is secure. Use the same password as any other password you ever used on other sites, then it’s possibly compromised if that other site gets compromised. The other element to consider - exposing directly allows remote users to try to access the device. Without authentication it will fail - but all those attempts show up in the error log.

True that. People seem to forget that $35 U.S. only buys the Pi itself. No case, no power supply, slow networking (fixed in the Pi 4), no storage (and very slow storage after you provide your own). Polisy is better in every measurable way...

Yep. I just logged onto the web - see it now. Perhaps that's why the response rate is low...

There is a poll?

The differing codes are inserted by your cell company - so that if you reply to the text it goes back to the reply email address. No way to control that. If you want to control sending texts fully (including the apparent from number) you will need to use API driven services like Twilio - and they all have costs associated with them.

I’ve just got back from a few days away - and @Benoit emailed me to say some things were fixed. I have not had a chance to test (that’s tonight’s job!). It’s certainly not breaking anything - but for me it wasn’t receiving the callbacks from Ring. So, no programs were firing. I’d probably advise waiting until it’s known to work before diving in - currently upgrading may mean removing, rebooting etc...

FWIW - UDI has Ring integration in advanced development status in PolyGlotCloud.... I’ve been working with Benoit to add floodlight control to it over the last couple of weeks... (must get latest testing done!) You don’t get better native integration than that....

Retro gaming? https://retropie.org.uk

If they already integrate with Alexa, then get an ISY Portal subscription (If you don’t already) and then use Alexa Routines to tie them together. You’ll be able to have variables on ISY trigger the WiFi plugs to turn on or off and use the value of the variable to determine the current state. The down side is this will require Internet to function. The benefit - no additional hardware (like a Rpi or similar). I’m using this method to integrate my Ring cameras to ISY (to receive and act on motion alerts). I think I’m almost there in getting ISY to be able to drive the flood and spotlights via this method as well....

You DON'T need the network module on ISY to be able to receive inbound API requests to 'trigger programs' or 'change variables'. This is base functionality in ISY. For details of the REST API that ISY has, see https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface 1.6 documents programs, and 1.8 documents variables. You ONLY need the ISY Network module if you want the ISY to initiate outbound network messages to other systems...

Also, CAI Webcontrol Board, a Raspberry Pi or Arduino boards can all talk to the ISY via its API (with a little code) and can have digital IO lines connected. You only need the network module on ISY if you want ISY to send network commands to such devices.

Insteon devices are 255 = Full On and 0 = Off. This is a single 8 bit byte and defined by the Insteon spec. Zwave devices use 100 = On though. So, the number represents a percentage. In both cases, sending simply ‘On’ sakes the device to turn on. When that means is set in the device as the default on level. For both that’s usually 100% (255 for Insteon or 100 for zwave).