brians

I received my Polisy in January and I believe that it already had UEFI installed, because I was able to go into the TPM setting to set a password in Administrative Console (I didn't set one yet) prior to the latest update which forced UEFI.

Today I went into PG2 and checked for Polisy updates, said it found 8 and then I updated Polisy. I waited a bit and restarted PG3. Now PG3 shows correct IoP version 5.4.1, and also a couple Nodeservers updated that would not before. This is not very intuitive - using a "deprecated" PG2 interface to update Polisy and PG3 while there is no update option in PG3. The update 5.4.1 in IoP did not seem to do these updates and is that just supposed to update IoP and nothing else? We are told that ssh updates will be a thing of the past. I anticipate that all the updates are going to be consolidated into one area one day.

Thanks, I will be more clear next time and make a new comment!

Update: I uninstalled/re-installed from PG3, authorized and is working again. Seemed to stop working after I upgraded Polisy to 5.4.1. Not sure if coincidence or something else. Here is log of errors after restarting it... 2022-03-08 16:27:39,196 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-03-08 16:27:41,875 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.31 Starting... 2022-03-08 16:27:42,003 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.10.106', 'netmask': '255.255.255.0', 'broadcast': '192.168.10.255'} 2022-03-08 16:27:42,005 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-03-08 16:27:42,013 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-03-08 16:27:42,014 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'installprofile': {'reboot': False}} 2022-03-08 16:27:42,154 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-03-08 16:27:42,156 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:59:40:78_1 - MID: 1 Result: 0 2022-03-08 16:27:42,175 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-03-08 16:27:42,275 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2022-03-08 16:27:45,025 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: Node server config has not yet been recieved. 2022-03-08 16:27:45,030 MainThread udi_interface.interface INFO interface:addNode: Adding node Ecobee Controller(controller) [None] 2022-03-08 16:27:45,032 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2022-03-08 16:27:45,226 Thread-6 udi_interface ERROR udi_interface:write: Exception in thread 2022-03-08 16:27:45,232 Thread-6 udi_interface ERROR udi_interface:write: Thread-6 2022-03-08 16:27:45,234 Thread-6 udi_interface ERROR udi_interface:write: : 2022-03-08 16:27:45,235 Thread-6 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-08 16:27:45,236 Thread-6 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-03-08 16:27:45,241 Thread-6 udi_interface ERROR udi_interface:write: self.run() 2022-03-08 16:27:45,241 Thread-6 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-03-08 16:27:45,245 Thread-6 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-03-08 16:27:45,246 Thread-6 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:59:40:78_1/nodes/Controller.py", line 282, in handler_params 2022-03-08 16:27:45,248 Thread-6 udi_interface ERROR udi_interface:write: self.Params.load(params) 2022-03-08 16:27:45,249 Thread-6 udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/custom.py", line 74, in load 2022-03-08 16:27:45,250 Thread-6 udi_interface ERROR udi_interface:write: for key in new_data: 2022-03-08 16:27:45,251 Thread-6 udi_interface ERROR udi_interface:write: TypeError 2022-03-08 16:27:45,252 Thread-6 udi_interface ERROR udi_interface:write: : 2022-03-08 16:27:45,252 Thread-6 udi_interface ERROR udi_interface:write: 'NoneType' object is not iterable 2022-03-08 16:27:45,885 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=10 2022-03-08 16:27:46,921 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=9 2022-03-08 16:27:47,930 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=8 2022-03-08 16:27:48,941 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=7 2022-03-08 16:27:49,945 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=6 2022-03-08 16:27:50,947 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=5 2022-03-08 16:27:51,960 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=4 2022-03-08 16:27:52,992 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=3 2022-03-08 16:27:54,014 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=2 2022-03-08 16:27:55,030 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=1 2022-03-08 16:27:56,045 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=0 2022-03-08 16:27:57,048 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-1 2022-03-08 16:27:58,077 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-2 2022-03-08 16:27:59,083 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-3 2022-03-08 16:28:00,088 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-4 2022-03-08 16:28:01,091 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-5 2022-03-08 16:28:02,140 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-6 2022-03-08 16:28:03,200 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-7 2022-03-08 16:28:04,260 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-8 2022-03-08 16:28:05,272 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-9 2022-03-08 16:28:06,288 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-10 2022-03-08 16:28:07,309 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-11 2022-03-08 16:28:08,311 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-12 2022-03-08 16:28:09,316 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-13 2022-03-08 16:28:10,318 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-14 2022-03-08 16:28:11,369 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-15 2022-03-08 16:28:12,428 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-16 2022-03-08 16:28:13,431 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-17 2022-03-08 16:28:14,469 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-18 2022-03-08 16:28:15,533 Thread-10 udi_interface WARNING Controller:handler_start: Waiting for all to be loaded config=True config_done=True params=None data=True nsdata=True... cnt=-19

I did and does not display correct version. I restarted entire Polisy also.

I upgraded which success, but my PG3 web interface still shows 5.3.0 while PG2 shows 5.4.1

Since upgrading to Polisy a month or two ago, I just left the STMP Use Default and has been working. I thought UD got rid of this before because of spam. Should I add my gmail back in?

Hi, my wife wants me to install a backlit LED mirror in our bathroom, and the only power there is from the wall switch to existing light. I am thinking the way to do it is to hard-wire the power always on in switch to the light and control locally at the light via a module such as Insteon 2443-222, but since they are no longer available I am looking for a Z-Wave replacement. I am not sure if I want smart control of the mirror right now, but would be easy with another similar module. I want ability to turn the mirror on separately without the main light. I currently have no smart switches in the bathroom... was thinking of just a Zen 71's to control control the module using a scene or program via ISY.

I have seen them go higher than $100 USD, plus shipping etc . is expensive. I have been purchasing used ones since around December to replace failed/failing ones, and have seen the price rise drastically on them. If sticking with Insteon and ISY, I recommend looking at Z-Wave switches.

@JaviOne more thing you could add is a query option from ISY, not a huge deal but I just noticed was not available.

I happen to have an OpenSprinkler I purchased a couple years ago when my EZ-Flora died. So far it has worked fine as standalone but was surprised to see it in the store here! Since it is winter here up in Canada and cannot actually test it by watering the lawn, I can only test using the web UI response and seems to be working. Some minor quirks I notice... If I turn on multiple stations too quickly in a program, instead of the open sprinkler queueing them, it seems to have more than one of the stations enabled on simultaneously - sometimes I have seen a couple, other times I have seen four on at once, which is not possible to do normally and it should normally queue them to run after each prior one is finished. I have worked around this by putting a wait of 5 seconds between each station on command in ISY program. Other thing is I named one of my stations "Front Lawn/Side Lawn" and ISY does not show this station with the "/" slash character. I think I have seen this before in other node servers but I would suggest to replace the / with whitespace or some other character depending on what the actual reason is. I fixed by renaming the station in open sprinkler without the / and then I had to remove/add the poly for ISY to see. The good thing about having ISY integration and programs turning on the stations is I can water in different order now. Opensprinkler programs only water in order of the stations 01-08 and cannot have a program that does stations in order 03,06,01,04 for example. I actually rewired mine so it would water lawn in proper physical order.

I was meaning at a higher level where controller is not required like Insteon, but it is nice to know that there are different types of associations and the assigned association seems more like Insteon in the aspect that it allows indirect communication. I just initially searched what these associations were, because of this discussion of Z-Wave scenes in ISY, and found out a bit more how they work and that other hubs seem to support. I am more interested in IoP supporting this as I have no desire to use ST or Hubitat.

I looked it up and other hubs like smartthings, hubitat , Vera etc. appear to do direct associations. Seems to work similar to Insteon scenes where the controller is not needed after an association is setup. I hope UD works on this and is on their roadmap.

Working good now, seen it is fixed in ISY Version 5.4.0_2

You mean the Z-Wave Association and Z-Wave scene dropdown which nobody has seen?

I made small error in my last post and called it a dimmer switch when I meant it was a motion switch that was faster updating. Anyways I did test the Zen71 on my ISY994i with a series 500 board and the performance is no different than my Polisy with Zooz S2 USB stick - meaning the ISY994i receives the on/off status nearly instant. Back with testing on the Polisy... I did notice however that if I added the Zen71 to a scene, a couple Insteon switchlinc for example, and quickly turn on/off the Zen71 the IoP would get a bit confused and start getting communication errors in administrative console and the switch would become unresponsive for a bit while it caught up. Now I don't think people would normally turn on/off a switch this way but thought would mention.

Yes, I think that I found before I disabled and made my own custom Query program that it would hang up on certain Z-Wave devices. In particular ISY seems to spend a long time with my Zooz ZEN25 double plug and I think it is sending power consumption updates frequently causing network traffic. I also think it is the ISY Maybe there could be an option on each device/node to exclude from query all, but my workaround seems ok. However, I do let the regular built-in query run at 3am and have not experienced any errors so it does work, and I believe there is more overhead with GUI when watching it from the Administrative console open.

I have experienced similar issue with previous version of IoP back when I first got it. For me, it was the query all program is doing this on startup. What I did was uncheck Query at Restart in Configuration, System. I then make my own custom query program that only does devices I want and this seems to be much quicker... I set this program to Run at Startup. It took a while to add all my devices but once is done I just have to maintain it. If you do not Query and know state of devices then some programs, scenes etc. may not work correctly, or not at all. I am interested in knowing what exactly the built-in Query does and why it hangs up like this.

With latest version today this seems to be resolved now after a full polisy reboot. Restarting IoP separately still causes PG2 to require a restart while PG3 updates nodes over time (but a query also works to refresh them all). I am not too concerned about PG2 because I am using only one nodeserver on it which should be updated to PG3 soon.

I just did this and now I lose all communication with every Insteon device. Update... rebooting entire Polisy resolved issue.

I fixed title and post to be more specific.

Did something get mixed up in this post? I am referring to UD mobile having issues and the responses here do not seem related. I posted here in this forum because was specific to UD mobile.

My old Leviton Z-Wave plus (500 series) switch that doesn't do instant status kills the Jasco even with overhead of a hail/query. The Jasco dimmer switch also is just as fast as this Zen71 and it is 500 series... if you look at my previous testing I go over this. I also have a Zooz Zen15 which status updates instantly when manual pressing the button and it is 500 series. Having said all that, I would not expect 700 vs 500 to be 2-3 seconds faster anyways, and 700 from what I read is just more security and distance. It is problem with this model of Jasco switch with slow status updates that I have and I would like someone else to test if they also have these Jasco switches.

Got my Zooz ZEN71 and it is way better than the Jasco. The response when physically turning on/off the ZEN71 is nearly instant to the ISY - similar to Insteon. I added to a scene and perform nearly as fast. Stay away from the Jasco brand switches.

I applied update remotely from my work and that update fixed ability to reboot IoP from the administrative console. What was other bug that is fixed?