EricBarish

here is the error code I get with the romba node. This keeps repeating. I will add it to the romba PG3 tab 2024-06-12 07:25:54.883 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-06-12 07:25:54.885 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-06-12 07:25:54.885 MainThread udi_interface INFO __init__:<module>: User=000db9560c24_4 2024-06-12 07:25:54.886 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db9560c24_4 2024-06-12 07:25:54.886 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db9560c24_4 2024-06-12 07:25:54.887 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTY6MGM6MjQiLCJwcm9maWxlTnVtIjo0LCJsb2dMZXZlbCI6IklORk8iLCJ0b2tlbiI6IkpFVi1PWlIlaHl4K0Y4QjMiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4yNyIsImlzeVZlcnNpb24iOiI1LjguMyIsImVkaXRpb24iOiJGcmVlIn0= 2024-06-12 07:25:54.887 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-06-12 07:25:55.524 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-06-12 07:25:55.800 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-06-12 07:25:57.143 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-06-12 07:25:57.145 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-06-12 07:25:57.145 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-06-12 07:25:57.146 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-06-12 07:25:57.146 MainThread udi_interface INFO __init__:<module>: Loading OAuth module 2024-06-12 07:25:57.148 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-06-12 07:25:57.148 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.3.12 Starting... 2024-06-12 07:25:57.415 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-06-12 07:25:57.415 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560c24_4/roomba-poly.py", line 19, in <module> 2024-06-12 07:25:57.416 MainThread udi_interface ERROR udi_interface:write: from roomba import Roomba 2024-06-12 07:25:57.417 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9560c24_4/roomba.py", line 42, in <module> 2024-06-12 07:25:57.418 MainThread udi_interface ERROR udi_interface:write: from collections import Mapping 2024-06-12 07:25:57.418 MainThread udi_interface ERROR udi_interface:write: ImportError 2024-06-12 07:25:57.418 MainThread udi_interface ERROR udi_interface:write: : 2024-06-12 07:25:57.419 MainThread udi_interface ERROR udi_interface:write: cannot import name 'Mapping' from 'collections' (/usr/local/lib/python3.11/collections/__init__.py)

Had to restart each node on plugin dashboard to get them connected. Roomba node not connecting.

I'm also seeing the same thing since yesterday.

I used a wifi extender to get wifi control into the garage and to my ring spots on that side of the house. Plugged into a outlet in laundry room next to garage fixed my connection problems.

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.

If you us nodelink no (but you need the pi to load nodelink and the CAI node and a ISY portal account) . If you us network resources yes. Time to upgrade you system ? That will give you the network resouces, but you will still need the PI to run nodelink to get the CAI node, no PG3 node for CAI devices. I updated two years ago to a polisy, PG2/3 was very unstable on the PI. Nodelink is still running on the PI and never have a problem with it.

I've been using CAi web control (a little old, $35) on my ISY 994 and then on Polisy. Can control and get results using network resouces or download nodelink ( need a PI ) and get the node for this device. No PG3 node for this device. 8 digital inputs 8 digital outputs 3 andlog input 8 optional DS18B20 digital temp, 1 optional humidity sensors built-in I2C and SPI support, up to 1000 line PLC program

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.