EricBarish

I have the ring mailbox connected to alexa, and alexa can then set a varaible using ISY portal when motion is detected. Alexa plays a message and polisy sends me a text/email or what ever you want when mail is delivered. Need a portal account for this to work. Biggest problem is range on ring mailbox is not great.

Another option is Tailwind IQ3, it can control up to three garage doors with one unit. Has a lot of home control connectivity. Would have to interface through Alexa to ISY using motion sensor variables to pass information. https://gotailwind.com/

fixed mine. polling 20/60 thanks

I have the Polisy running Polyglot v3 with the latest updates. The NodeLink is still on a RPI3. Nodelink running fine in V3 with no problems. Install was striaght forward same as for old V2 version of polyglot.

Only problem I had was it dropped my old Nodelink nodeserver that was in slot 2. Reinstalled and now working fine.

I see Mr Bill replied in the same. I also brought mine in close to the polisy when I de/reincluded.

Transfered all my zwave last week to the zmater on my polisy. Did have to exclude and then re- include this one and one of my repeaters. All others added correctly. My Model number for the tilt is TILT-ZWAVE2-ECO 5 nodes added basic control access control wakeup power alarm tamper alarm home security alarm only strange thing i have seen is access control node reports "window/door open" (when in open position) and "idle" when in closed postion, when looking at status in a program says "window/door closed" and "window/door open". It does work correctly in my programs.

Does these mean we will have a seperate update going forward for PG3 for Polisy and one for Eisy ?

Simple fix, when back in and reinstalled the skill for Isy V3. Entered passwords and all devices started working again. Not sure why I had to do this, portal email and password had not changed. But it worked! Thanks all for the help

I can find the devices in the Alexa App. Thats where it is showing the server error. Devices not working in the app or by the Alexa ipod. Will let it sit a while and see what happens.

Did not fix alexa that still does not work. Figured out portal web access just before your reply

I figured it out. From portal web acess I can control the devices

I can control the devices by starting ISP Polisy using the cloud interface if that is what you mean ? I can control the devices using ud mobile also Not sure what you mean by isy web access

Alexa has stopped responding to commands for ISY device controls this morning. Have any error meassage saying "Server is Unresponsive". Checked, my Portal licience is up todate Alexa repsonds to non Isy commands Do I need to update my information/permission for the Isy on Alexa? I see it was done in a 2018 post. Thanks

sometimes it can take a while for the devices to show up (24 hrs) and need to tell alexa to find devices inthe app. I'm running IoP and alexa devices working fine, if you have the alexa phone app should be able to see under devices. Just setup some variables with IoP and alexa, (took awhile to showup). Between using variables and light switches as alarms in polglot alexa and then routines in the alexa app, have been able to get my ring devices connected to IoP without the rink node server. -door bell ring send to IoP to flash lights when bell rings - control of outside camera spot lights from insteon wall switch in garage for manual control - connected ring bridge lights to IoP Took a bit of learning (the ring camera light ) but in the end all works and response is very quick.

Not sure what I diid, left it alone for a few hours. Now all the nodes appear. Have to have patience with these things.

On moving Ecobee from Pg2 having problems getting the nodes to install correctly in IoP. Nodes show up in PG3 for the 3 ecobees ok. Getting error measages saying divers not found in the log file (included below ) here is what i see in IoP after hitting install all nodes in IoP. It has a long way to go to match PG2 interface. Tried to delete and reinstall get same results. Thanks, Eric Ecobee_7-13-2022_122129_PM.zip

lets put this down to jumping in before looking. Setup my key as APIKey and enter the value. Nothing worked. Finally delete and reinstalled the node and notice Key format API Key, need the space. Might want to fix the configuration instructions. Configuration The Ambient Weather node server has the following user configuration parameters: APIKey : Your API Key, needed to authorize this node server to connect to the Ambient Weather server and retrieve your data.

Need to check if you did not do the update yesterday will the new commands today install everything correctly.

sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx as stated by Jwagner. Same commands worked for me.

Tried the fix and it did not work. Michel worked on it this afternoon and got all working. Not sure they will issue another fix or you should enter a ticket.

I had the same problem had to open a ticket and Michel fixed all this afternoon. The cause was an error in updated Python library on the 27.

here is what I used in PG2. For PG3 do i need to add the app_key and what is its format for the api_key what is its format APIKey ?

I did this a few years ago for PG2, What am i missing? Setup new key in ambient weather. have an application key and the new key i called Polisy. What do I enter for key and what do I enter for value. I assume enter the key in the key location and in this case nothing for value. Lost on a simple item . 2022-06-28 16:42:00,934 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-06-28 16:42:03,419 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.46 Starting... 2022-06-28 16:42:03,432 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.0.63 [ISY: 5.4.4, Slot: 6] 2022-06-28 16:42:03,434 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.104', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2022-06-28 16:42:03,435 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-06-28 16:42:03,441 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6'}} 2022-06-28 16:42:03,483 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-06-28 16:42:03,485 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:56:0c:24_6 - MID: 1 Result: 0 2022-06-28 16:42:03,498 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-06-28 16:42:06,601 Thread-1 udi_interface ERROR ambient-poly:discover: Missing API key

Tazman Looks like it has been fixed. See from Michel below. Have not checked it yet. Found the issue and fixed it. Please click on Admin Console | Configuration tab | Upgrade Packages. Once you hear 4 beeps, reboot Polisy.