whywork

Hi, I use and enjoy my ISY/Polisy devices every day. Meets my requirement for local control (cloud independent) and very robust event driven programming/control. Not to mention bulletproof hardware. I want Matter to work on Polisy. In my opinion, Matter protocol is like Democracy, the worst form of government, except for all the rest. I am confused by Michel’s recent post on eisy iox 6.1.1 “Regarding upgrades, the OS cannot be upgraded to anything above 14.3p5. Matter support remains buggy mostly due to IPv6 dependency. While we're on 14x OS, you can upgrade UD packages (only) via ssh as long as you understand that they have not been tested, and especially due to dramatic increase in processing for eisy-ui, you might not have a good experience.” 1) Why can’t a Polisy device be upgraded to FreeBSD beyond 14.3? Hardware limitations, Firmware limitations? What? Confused. 2) Matter by design depends on IPv6; not news. Since matter/ipv6 dependencies have been acknowledged/intrinsic, what is the plan moving forward about Matter on existing Universal Devices hardware? Confused again. I hope Universal Devices can embrace and succeed with Matter. Thanks to all the forum/community contributors.

Any experiences with 6.1.1, Polisy and Matter? I really want to be able to use an IKEA Bilresa wireless matter remote control.

Circling Back - Been busy on other stuff TL;DR - still no success with matter on my Polisy I use and enjoy my ISY devices - and insteon network. Thanks for the feedback and useful information on my matter troubles. Some additional specifics on my installations: I have both Polisy/zigbee/zwave internal dongle and homeassistant running. Homeassistant using their ZBT-2 dongle running matter and creating a thread border router. I have several matter devices connected to homeassistant including a melross thermostat an ikea/bilresa wireless pushbutton remote and tapo webcam hub that work. I have an additional Bilresa wireless pushbutton remote that is factory reset. So far I have been unable to get my Polisy 6.051 to pair with any matter device. 1) I have tried udmobile app on ios and android direct QR code pairing of new Bilresa 2) UD mobile shared code pairing old Bilresa from homeassistant 3) UD mobile shared code pairing of polisy matter to homeassistant hub No success. Interestingly during UDmobile paring with QR new Bilresa I get popup feedback after reading the QR code that a "switch" is going to be added. Times out/I give up after 10 minutes, no error messages. On method 2 polisy starts pairing and then times out/i give up with no error messages after 10 minutes. Method 3 Homeassistant creates sharing code for itself, Polisy accepts code but never finds homeassitant. (in opposite direction, homeassitant did accept sharing code from Tapo hub to pair that hub) I will be patient. I understand matter support is currently alpha. And killing java may be a priority. I look forward to updates with more guidance, diagnostics and future releases of matter on ISY devices.

Hi, I use and enjoy my ISY devices every day. I have a Polisy Pro running 6.04 with the internal zwave/zigbee matter dongle. Background: I am looking to replace a couple of aging Remotelinc 2s. IKEA is now selling a matter capable Bilresa two button switch for $6. I got a couple and I think they are nice. I have a matter network with thread over wifi running in my house with Home Assistant. The Bilresa switches pair/add to matter OK on Home Assistant. I have Zwave and Zigbee devices paired with my Polisy. I have never tried to use matter on my Polisy; no devices added. I understand that to add an already paired matter device to an additional matter "server" is not just scanning the original QR code but requires getting a new pairing code for the matter device from the first/existing matter "server". I am unable to get my Polisy to pair with the Bilresa switch. I have tried several ways. Open Home assistant, ask to share Bilresa, get pairing code. Open UD mobile, verify Matter is enabled. Ask UD mobile to add new (this would be first matter device on Polisy) matter device. UD Mobile asks for pairing code - I enter the sharing/pairing code from home assistant. After several minutes the request times out. Bilresa not added. I have tried adding Bilresa using both UD mobile on android Pixel phone and on iOS iPad. Bilresa does not add. Tried with Bilresa within inches of Polisy. No Bilresqa added. At a different location I have successfully added/shared a different matter Bilresa to two matter "servers" ((Nest hub and Home Assistant) on the same network. Bilresa is seen and works with both matter "servers." Is Matter really running on my Polisy? What other ways should I try adding/sharing Bilresa to my Polisy? Any suggestions? Thank you for you advice.

Thanks to Panda88 for your work on the yolink (local) plugin. This is a follow-up report - I have successfully implemented a 4 button on/off fob YS3605-UC as a substitute for an aging Remotelinc2. Running a local hub YS1606-UC with on/off fob YS3605-UC (bound to local hub) and Yolink local 1.6.9. The YS3605 works reliably and from longer distances than remotelinc (LoRa). Some provisos - The YS3605 is exposed in the Admin Console as a four button device, however it really functions as a two button device with long and short press messages: Green button 1 gives button 1 short press, Red button 2 gives button 1 long press, Green button 2 gives button 2 short press, Red button 2 gives button 2 long press. button 3 and button 4 do not seem to exist. Make sure programs only expect information from button 1 and 2 (not 3 or 4). Also, there seems to be a bandwidth challenge. During testing, I found that many rapid Yolink button presses seem to backup/queue and get delivered in bursts. Remotelinc does not exhibit these delays. In real-world use, the Yolink fob works well with only millisecond delay. Goodbye Remotelinc2, hello 4 button on/off fob YS3605-UC. I also like the formfactor of the Yolink fob over the remotelinc. Again thanks.

Deleted one Yolink node Now running only TSTYolinkLocal(11) Current Status: Connected Current Version: 1.5.14 / Standard [Beta] Time Started: Sep 26, 2025, 10:00:39 AM Thanks

Thanks for the quick reply. Happy to run only one node. Just to be sure, which node should I be deleting? What is its exact name?

Hi, FYI - This is information - not a request for help (yet) Was away for a while. And perhaps with the merging of local/cloud versions of hub this issue will go away but: I now have a bunch of fobs with the same name and I seem to be missing one fob and the fobs have generic names that make them hard to differentiate. More details: I have two locations - each with a standard Yolink talking hub YS1604-UC and each with a "local" Yolink hub YS1606-UC. One location has one regular 4 button fob YS3604-UC The second location has one regular 4 button fob YS3604-UC, one 2 button small fob YS3614-UC and one 4 button on/off fob YS3605-UC I have the the two Yolink plugins Current Version: 1.5.14 (local and regular) running on Polisy with Polyglot V3 So far so good However when I ask both local and regular Yolink plugins to "add all nodes" I run in to trouble I get two nodes labeled Yolink Fob I get one node labeled Yolink Fob Small (I think I renamed it) And another two nodes named Yolink Fob with the name of my second location ( I think I renamed it) Huh! Which fobs are connected via local hub(s)? Which fobs are connected via cloud hub(s)? Anyway - I use and enjoy the Yolink plugin every day. I have a feeling when the cloud and local Yolink plugins are merged, this may resolve itself. Thanks

Hi, I ues and enjoy the Yolink plugin on my Polisy every day. Yolink sensors; temperature, open closed, etc working well. I am trying to use a Yolink on/off fob YS3605 US to replace my aged Insteon Remotelinc 2444A2. But I cant seem to get it to work. Background: I added a Yolink mini on/off fob YS3614-UC (mini fob, not "regular" on off fob) This is a two button mini fob. The YS3614-UC is exposed by the Yolink plugin with four parameters: Key One, Short press, Key One Long Press, Key Two Short Press, Key Two Long Press. Configured the YS3614 so key One short press is DON, Key One long press is DOF, Key 2 short press DOF and Key 2 Long press DON. Adding the YS3614 to a to a program and using the only available "control" conditions I can turn on and off an insteon switched light. Control key 1 is on and light turns on, control key 2 is on and light turns off. I can see the last command in the Admin console tab for each of the two keys in the fob. Great except that the YS3614-UC has only two buttons. The YS3605 US has four buttons, A Green and Red and B Green and Red. And is is about the same price as the YS3614-UC They are exposed as Key One, Short press, Key One Long Press, Key Two Short Press, Key Two Long Press. Key Three Short press, Key Three long press, Key Four Short Press, Key Four Long Press. Configured in same pattern as YS3614. Key One Short Press DON, Key Two Short Press DOF, etc. Add it to the existing program Control on etc The YS3605 switch one works once, to turn on the insteon light with switch one. The YS3605 switch two never works to turn orr the insteon light. Turning off the insteon switched light by "hand" and now the YS3605 switch one creates an admin console error of inability to communicate with the insteon switched light. Also the admin console only shows last command for key 1. The others, key 2 key 3, key4 always say unknown, no matter how many times I push those fob buttons. I have to use the YS3614 to turn the insteon switched light on and off. Then the YS3605 will again turn the light on only once. Yikes! I am confused. Suggestions? I would copy/paste my actual programs/settings to the forum if I knew how.

Thank you. I had missed that Polyglot plugin setting/information/action in the UD app. Still, I see no way to easily reboot Polyglot.

Hi, I use and enjoy UD devices every day. I am old and cranky. Keeping plugins updated - I may be confused but: It seems I have to logon to PG3x web interface Https://mypolisy:3000, say OK to this site is not secure (no certficate), then go to logon page to enter username and then password, then click on purchases. Then have to scan display page to finally see if any plugins I have purchased/installed need to be updated. A lot of steps - how about sending me an email or at least notifying me via UD mobile app that i need to update a plugin? Rebooting Polyglot PG3x There have been times when my Polisy is running (scenes and programs working) but Polyglot plugins seem to stop working/hung. There does not seem to be a drop down menu item on the polyglot interface to reboot just polyglot. I have tried warm rebooting the "working" Polisy but I often need to cold boot Polisy to get the plugins working again. How about adding a Polyglot menu item to reboot Polyglot only (perhaps in the System tab) Suggestions, comments? Best regards

Hi, Magic happened. Its working. After your note about new version yesterday, I reinstalled Polisy/Hubitat/Nodeserver and rebooted everything. Thought I was up to date. This AM I got a "message" from PGx3 that a new version of Polisy/Hubitat/Nodeserver was available. OK thought I had done that. I re-reinstalled Polisy/Hubitat/Nodeserver and magically "CONNNECTED" appeared on the Polisy Hubitat nodeserver. Current Version: 1.0.2 [Production] - seems like something got fixed. Still no Real-time Hubitat log file. But I now see six Hubitat nodes/devices that include the lights I want to control. Now lets see if I can make stuff happen to those lights. Thanks for your help

Hi, In this post above https://forum.universal-devices.com/topic/43492-my-experience-with-hubitathousepanel-nodeserver-in-2024/#comment-383412 I uploaded some 2 zipped overall logfiles from Polyglot/Polisy (not hubitat nodeserver specific) that were recorded around the time I first tried to install Polisy Hubitat nodeserver - they include explicit lines mentioning hubitat nodeserver. FYI - sudo pkg python3 - returns with you have the latest version of phython3 already installed.

Hi, Again thanks for your help. I tried reinstalling Polisy Hubitat Nodeserver as you suggested. No Joy. (I did get the always present error message saying the install of Polisy Hubitat Nodeserver FAILED. I am not sure I am communicating what I am experiencing on my Polisy - I think the Hubitat nodeserver is not installed/working correctly. Two reasons listed below. 1) I always get an error message from day one, saying my install of Polisy Hubitat Nodeserver FAILED. While it seems to be running, every install gives me one of those annoying popups that disappear saying something that vanishes almost immediately, telling me some message to the effect that install has FAILED. 2) Polisy Hubitat Nodeserver NEVER shows any log files. I click on the log button, the window changes, but only shows the image below Real-time Hubitat log file Scroll to BottomDownload LogDownload Log PackageDebugInfoWarningErrorCritical But NO LOG information - Blank, not even a data window is created As an example of a nodeserver (Yolink) that is working for me "data window" - see below Real-time YoLink log file Scroll to BottomDownload LogDownload Log PackageDebugInfoWarningErrorCritical AutoScroll 2024-05-20 23:14:01,722 Thread-7 udi_interface ERROR yoLink_init_V3:connect_to_broker: Exception - connect_to_broker: timed out 2024-05-20 23:14:03,726 Thread-7 udi_interface INFO yoLink_init_V3:connect_to_broker: Connecting to broker... 2024-05-20 23:14:03,727 Thread-7 udi_interface DEBUG yoLink_init_V3:request_new_token: yoAccess Token exists : True 2024-05-20 23:14:03,728 Thread-7 udi_interface INFO yoLink_init_V3:connect_to_broker: Retrieving YoLink API info 2024-05-20 23:14:03,729 Thread-7 udi_interface DEBUG yoLink_init_V3:retrieve_device_list: retrieve_device_list 2024-05-20 23:14:04,242 Thread-7 udi_interface ERROR yoLink_init_V3:retrieve_device_list: Exception - retrieve_device_list : 'devices' The Hubitat Device logs show nothing other than what I posted previously. I keep thinking that the Polisy Hubitat Nodeserver, while showing valid configuration settings, is not really installed correctly. What are the FreeBSD packages dependencies for Polisy Hubitat Nodeserver? Thanks

Hi, Thanks for the follow-up. I have made some suggested changes, but still remain 192.168.1.194 Polisy/Hubitat/PGx3/nodeserver "disconnected" FYI - about logging/logs I turned on 192.168.1.197 Hubitat HousePanel logging and now see logfiles BUT - 192.168.1.194 Polisy/Hubitat/PGx3/nodeserver - I can't see any log files - when under Polyglot V3 Hubitat click on LOG Real-time Hubitat log file - Nothing - restqart Polisy Hubitat node server - NO log file Real-time Hubitat log file Scroll to BottomDownload LogDownload Log PackageDebugInfoWarningErrorCritical AutoScroll Scroll to Top So to recap - after cold boot of Polisy device and Hubitat device, and waiting 5 minutes Configurations Hubitat 192.168.1.197 device: Hubitat HousePanel webSocketHost text 192.168.1.194 webSocketPort text 9100 accessToken String xxxxxx directIP String 192.168.1.194 directPort String 9100 Polisy 192.168.1.194 device: Polisy/Hubitat/PGx3/nodeserver accessToken xxxxxxx hubEndpt http://192.168.1.197/apps/api/906 restPort 9100 LOGS Hubitat 192.168.1.197 Device app:9062024-05-20 04:46:26.311 PMinfostate changes will be posted to HP at IP: 192.168.1.194:9100 app:9062024-05-20 04:46:26.267 PMinfoHubitat Local EndPoint = http://192.168.1.197/apps/api/906 app:9062024-05-20 04:46:26.264 PMinfoAccess Token = xxxxxxx Polisy 192.168.1.194 Device NO Logs - Real-time Hubitat log file - Nothing Status Hubitat(6) Current Status: Disconnected Current Version: 1.0.10 [Production] Time Started: May 20, 2024, 5:22:10 PM Uptime: 29 minutes I remain stumped. Any suggestions?