pkauf

For "on/off" lamp and dimmer - does this mean virtually any brand or is there an actual list of brands/devices that are supported?

Third Reality Motion Sensor and Water Leak Sensor https://www.amazon.com/dp/B08RRRWK6B?ref=ppx_yo2ov_dt_b_product_details&th=1 https://www.amazon.com/dp/B09GYFN8VL?ref=ppx_yo2ov_dt_b_product_details&th=1

Thanks. That’s what you get for not reading carefully. 😀

Just got my Zmatter board turned on for Zigbee and am trying to add a simple motion sensor device. When it does the interview it comes back with 2 nodes, on unknown, and the other a switch. I've had similar problems with Zwave, and normally an additional interview fixes it. I tried that with this, and it still shows up with invalid devices. Do I just have an unsupported device? Is there a list of devices that should work? Totally new to Zigbee and I'm just trying to test the waters . . . Any help would be appreciated.

I am ordering one of these. I've had Schlage's for years, and they just have too many issues. Gets here Tuesday, based upon other posts, seems like this is much improved, and I like the fingerprint . . .

OK, I'm a moron. File this thread under "I didn't think about the obvious". I finally updated the default admin login after doing my migration from my old ISY hardware to the Polisy/PG3 a couple days ago. Forgot about having to update the Polisy IOX password for the connection. After I rebooted the Polisy, the connection to the IOX showed disconnected. That finally joggled my old brain into "OMG, what an idiot". Sorry for the fire drill. Completely my fault. All is working again. Thanks!

I take it back. Although I can see the statuses devices change inside PG3, none are now updating in the ISY interface. The zones were working before, but not anymore. But I still can click the "Toggle Door Chime" and it updates the DSC.

and, I'm able to click the button "Toggle Door Chime" and it works. I can see the panel accept the command, it just doesn't update the ISY.

Also, the Zone status update fine. So it can see some of it.

I don't think so. What's the solution? Reinstall?

I watch the node server itself and I can see GV0 toggle when I change the chime status, it just doesn't update on the ISY device for the partition.

I have a DSC alarm and running this node server, and having issues with the statuses on my partitions. I can send a toggle command on the "Door Chime" device, but the status of the Door Chime doesn't show up on the partition. In fact, even though I have seen data here before, now it's all blank. Not sure what the problem it, but it makes my programs not work as they can't get the current setting for the door chime to turn it on or off (I have a program that checks status of chime to determine whether or not to send the toggle command to turn it off or on as requested. Any thoughts on what's wrong here? See Screen shot.

OK, thanks. If you ever get the want to do it, let me know. Thanks for all the replies.

So is there any instructions on how to do it or does it just not work?

Am I doing something wrong? What is the process to allow the NS to connect for the j7+? 023-05-12 13:10:02,369 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:02,372 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:02,373 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:02,376 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:02,377 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:02,380 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:07,380 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:07,383 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:07,383 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:07,387 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:07,499 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:07,500 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:12,509 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:12,510 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:12,513 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:12,515 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:12,619 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:12,620 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:17,632 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:17,635 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:17,636 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:17,639 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:17,640 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:17,643 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:22,649 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:22,652 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:22,655 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:22,658 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:22,757 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:22,758 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:27,760 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:27,762 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:27,764 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:27,766 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:27,877 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:27,878 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:32,883 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:32,883 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:32,886 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:32,889 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:32,997 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused

Want to also say thanks to @bpwwer for spending a couple hours remotely on my system trying to figure this out. Very bizarre problem, doesn't make sense. Really learned a lot about the entire config by watching him troubleshoot. Thanks again!

I just converted my old ISY994i to Polisy Pro, and needed to convert my old PG2 Node servers to PG3. I installed the trial version of the Envisalink-DSC and get this error in the log file when it tries to start. Any idea what's wrong? 2023-05-08 10:46:25,857 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-08 10:46:25,869 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-08 10:46:25,870 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/./evldscns.py", line 11, in <module> 2023-05-08 10:46:25,871 MainThread udi_interface ERROR udi_interface:write: import evldscns 2023-05-08 10:46:25,872 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/evldscns/__init__.py", line 2, in <module> 2023-05-08 10:46:25,872 MainThread udi_interface ERROR udi_interface:write: from .nslib import Nodeserver, Node, getValidNodeAddress, getValidNodeName 2023-05-08 10:46:25,873 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/evldscns/nslib.py", line 1 2023-05-08 10:46:25,873 MainThread udi_interface ERROR udi_interface:write: poly 2023-05-08 10:46:25,874 MainThread udi_interface ERROR udi_interface:write: IndentationError 2023-05-08 10:46:25,874 MainThread udi_interface ERROR udi_interface:write: : 2023-05-08 10:46:25,875 MainThread udi_interface ERROR udi_interface:write: unexpected indent

Very cool, I did not know that. I have my own subscription on my existing ISY, so I can do that. I will contact support. Thanks for the info!!!

My original question also was asking - Can I run my ISY on Polisy in parallel with my 994 and access the ISY portal? I bought the Polisy and a USB PLM a couple weeks ago, and would like to transition some of it over gradually. Is there a way to do that?

I am in the process of working on phasing out (EVENTUALLY) my isy994 due to the issues with the serial PLM (I am a huge Insteon user and don't want to trash all my devices) and hopefully replacing it with my new Polisy Pro/USB PLM. I have integrated some basic Polyglot stuff on RPII to my ISY, but am trying to understand the implementation here . . . Will the Polisy be my standalone replacement for all ISY functions, or do I still need to run the ISY hardware? Will my ZWAVE devices work? I use the portal integration for Amazon Echo - can I have 2 PLMs running during my migration? I'm sure I'll have more questions as I move forward, but just starting at the basics here . . . . Is there any documentation that goes over this at a high level? Thanks!!! Paul

Just got back and installed the fix. Works perfectly. Thanks for fixing this!!!!!

Looked at the logs. I have this(see below). I see messages looking like its converting the temperature, but not the same message on the rain. Also attaching what I see when I flip the units from US to Metric. It will change temp back and forth, but not the rain units. Also attaching screen print from meteobridge. 2020-07-02 14:19:03,791 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set rain driver GV3 to 3.8 2020-07-02 14:19:03,792 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver rain - GV3: 3.8, uom: 105 2020-07-02 14:19:03,798 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set humidity driver ST to 81.0 2020-07-02 14:19:03,799 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver humidity - ST: 81.0, uom: 51 2020-07-02 14:19:03,802 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver GV4 to 26.2 2020-07-02 14:19:03,803 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - GV4: 79.2, uom: 17 2020-07-02 14:19:03,805 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver GV0 to 25.1 2020-07-02 14:19:03,806 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - GV0: 77.2, uom: 17 2020-07-02 14:19:03,808 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver ST to 28.7 2020-07-02 14:19:03,810 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - ST: 83.7, uom: 17 2020-07-02 14:19:03,813 Thread-1 polyinterface INFO weatherstation:log_message: "GET //mb.php?d=02/07/2020%2014:19:01%2028.7%2081.0%2025.1%202.7%200.9%20288.0%200.0%200.0%201011.1%20281.0%201%20m/s%20C%20hPa%20mm%202.2%201011.8%203.8%20417.8%203.8%2026.2%2049.0%2028.7%2029.3%2029.3%2020200702131747%2021.2%2020200702031258%202.7%2020200702093901%207.2%2020200702093539%201013.1%2020200702113801%201009.4%2020200702030500%204.3%2013444%206.3%20TL-MR3020%20--%20--%202.3%20--%20281.0%200.0%2027.1%2020200701073223%2020.1%2020200701191906%2027.1%2020200701073223%2027.6%2020200609114208%20-6.1%2020200122110206%20--%2098.0%2020200702034956%2069.0%2020200702122503%2025.4%2020200702140345%2020.6%2020200702024418%2029.2%2080.0%2025.4%2026.3%2046%202.5%202.2%20--%20--%20--%20--%20--%20--%20--%207259581%2029.8%2020200701082249%2021.4%2020200701223210%2029.8%2020200701082249%2021.2%2020200702031258%2033.4%2020200615142822%20-1.9%2020200121065212%2013.0%2020200701191330%2013.0%2020200701191330%2017.0%2020200331113442%203.8%203.8%2020141225172101%20417.8%2020141225172101%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%20--%2020.1%2020200701191906%200%2029.0%2020200701191708%2037.6%2020150717133225%20-6.7%2020150108064422%2029.0%2020150809125932%20-15.9%2020150108053041%2020.6%2020170911164651%201013.8%2020200701121009%201009.2%2020200701195204%201013.8%2020200701121009%201009.2%2020200701195204%201030.7%2020200308111036%20993.9%2020200206145843%201038.3%2020170108091553%20985.1%2020181010122647%207508.5%2025.3%203%2092.8%2014:04%2017:36%2003:25%200.7%2098.0%2020200702034956%2069.0%2020200702122503%20100.0%2020200210230449%2023.0%2020200416145300%2096.0%2020200701014236%2073.0%2020200701112649%200.0%200.0%20[rain0total-max@M1]%20[rain0total-max@Y1]%20--%2028.7%201011.2%20--%202.7%20--%2025.2%200.0%2081.2%2019.9%200.7%2020150108064422%2020141225171735%2020150108073548%2020141225172101%2020141225172101%20230.4%2041.8%2020200630134422%20-8.4%2020200121074400%20_Increasing%20clouds%20with%20little%20temperature%20change. HTTP/1.1" 200 - 2020-07-02 14:19:25,218 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set rain driver GV3 to 3.8 2020-07-02 14:19:25,219 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver rain - GV3: 3.8, uom: 105 2020-07-02 14:19:25,221 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set humidity driver ST to 81.0 2020-07-02 14:19:25,222 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver humidity - ST: 81.0, uom: 51 2020-07-02 14:19:25,224 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver GV4 to 26.2 2020-07-02 14:19:25,225 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - GV4: 79.2, uom: 17 2020-07-02 14:19:25,228 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver GV0 to 25.1 2020-07-02 14:19:25,229 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - GV0: 77.2, uom: 17 2020-07-02 14:19:25,232 Thread-1 polyinterface INFO weatherstation:meteobridge: - Set temperature driver ST to 28.7 2020-07-02 14:19:25,233 Thread-1 polyinterface INFO polyinterface:reportDriver: Updating Driver temperature - ST: 83.7, uom: 17

OK, thanks. I have just been playing with them, and using the values returned to find what I'm looking for. I have a strange issue. I have set the incoming units to metric, and units to US. This seems to work fine for the Temperatures. But for Precipitation is shows wrong. It is showing the metric value (mm) and using a inches label. What am I doing wrong? See screenshots. Thanks again for all the help.

Are there descriptions available for the Meteobridge field numbers anywhere? Names are a little cryptic . . . but I can use trial and error if not.

Thanks so much, I thought that was it, but didn’t know where the list of field numbers were. Awesome job, this is exactly what I needed.