gviliunas

@N8N , Unfortunately the default server is UDI's server which, in the past had (Not sure if still true) a shared-by-all-of-us monthly limit for messages sent and occasionally went off-line. The advice to use Google or other SMTP server under your control was an attempt to address this unreliability. Now, with all the Google security changes, Google has also failed to work reliably. I think most of us have given-up on SMTP notification. I think that the modern accepted and reliable approach is to use a notification service like PushOver.

I fixed this problem by splitting the first program into 2. One program detects dark as <= 15 lux while the second program detects light as > 25 lux. (And removing any Else clauses) For me, this prevented the little cloud rolling by near sunset from causing the it's-dark....wait no it's light flip-flopping.

@leonpc, The second error that you list is the same one that you get if power is off to the LiFX light as the NS is initializing or if the IP address of the bulb has changed or if the MAC is different than specified. I also vaguely remember sometime back that LifX changed the MAC addresses (a slight 1-octet change easily missed) of their bulbs during a firmware update so the MACs given on the paperwork didn't match anymore and my previously-working devlist, created with that paperwork, stopped working. This killed my first implementation. If you created your devlist from the paperwork that came with the bulbs, you may want to check your router to be sure the MACs and IP are correct in in the devlist. At the time, I opened a ticket with LiFX. They acknowledged the change but offered no other help or suggestions. Finally, if you haven't set reserved IP addresses for your bulbs in your router, I would recommend that you do so. After fixing the MAC addresses in my devlist my NS has worked for several years now. Finally, there were rules for creating the devlist. Notepad++ was a good tool. Addresses should have lower-case letters. Names should be 14-characters or less and without special characters. Type will be 'bulb' (no quotes) or ??? (can't remember. Check the documentation if you are adding strip lights - Otherwise the type is usually bulb. Good Luck!

I'm not sure why our outcomes are different but I've been using this NS on Polisy with 29 bulbs and a devlist for several years now and I haven't had problems. I am using a dd-wrt router and have reserved IPs setup in the router for each bulb.

Thanks @shbatm That is strange. I deleted the Scene and the folder, restarted IoX and now I was successfully able to install the HA plugin! Yeah! Thank You!!!!!

Thanks @shbatm!! Here are the files nodes.xml status.xml

I have installed Home Assistant on a spare NUC and have just begun to learn HA in order to connect to sensors not supported in Polisy. I and am hoping to access my UDI Polisy v5.8 system via Home Assistant to make it all run seamlessly. (LOL) I can install the plugin and connect to the Polisy. I then see the HA query all of my devices but the setup then seems to fail with some missing "available nodes" in Home Assistant. Am I reading this correctly? Any ideas as to how to fix? Here is my Home Assistant log: 2024-01-18 14:41:29.986 DEBUG (MainThread) [pyisy] ISY Response Received: /config 2024-01-18 14:41:30.020 INFO (MainThread) [pyisy] ISY Loaded Configuration 2024-01-18 14:41:30.022 DEBUG (MainThread) [pyisy] ISY Request: http://192.168.1.72:8080/rest/config 2024-01-18 14:41:30.027 DEBUG (MainThread) [pyisy] ISY Response Received: /config 2024-01-18 14:41:30.050 INFO (MainThread) [pyisy] ISY Loaded Configuration 2024-01-18 14:41:30.050 DEBUG (MainThread) [pyisy] Increasing available simultaneous connections 024-01-18 14:41:32.004 DEBUG (MainThread) [pyisy] Parsing group: S-All Dining Room [13825] 2024-01-18 14:41:32.005 DEBUG (MainThread) [pyisy] Parsing group: S-Dining Room [21083] 2024-01-18 14:41:32.006 DEBUG (MainThread) [pyisy] Parsing group: S-All-Office [338] 2024-01-18 14:41:32.007 DEBUG (MainThread) [pyisy] Parsing group: S-KPL-H Special Lights Status [37129] 2024-01-18 14:41:32.007 DEBUG (MainThread) [pyisy] Parsing group: S-KPL-C Kitchen Status [688] 2024-01-18 14:41:32.008 DEBUG (MainThread) [pyisy] Parsing group: S-KPL-B Guest Rm Status [52360] 2024-01-18 14:41:32.008 DEBUG (MainThread) [pyisy] Parsing group: S-KPL-1 Hall Status [27424] 2024-01-18 14:41:32.008 DEBUG (MainThread) [pyisy] Parsing group: S-KPL-E Office Status [38353] 2024-01-18 14:41:32.009 DEBUG (MainThread) [pyisy] Parsing group: S-Christmas Lights [15887] 2024-01-18 14:41:32.009 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ISY (192.168.1.72) for isy994 Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 406, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/usr/src/homeassistant/homeassistant/components/isy994/init.py”, line 104, in async_setup_entry await isy.initialize() File “/usr/local/lib/python3.11/site-packages/pyisy/isy.py”, line 143, in initialize self.nodes = Nodes(self, xml=isy_setup_results[2]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/usr/local/lib/python3.11/site-packages/pyisy/nodes/init.py”, line 127, in init self.parse(xml) File “/usr/local/lib/python3.11/site-packages/pyisy/nodes/init.py”, line 461, in parse Group( File “/usr/local/lib/python3.11/site-packages/pyisy/nodes/group.py”, line 57, in init self._update() File “/usr/local/lib/python3.11/site-packages/pyisy/nodes/group.py”, line 101, in _update valid_nodes = [ ^ File “/usr/local/lib/python3.11/site-packages/pyisy/nodes/group.py”, line 105, in self._nodes[node].status is not None ^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: ‘Nodes’ object has no attribute ‘status’ Thanks in advance for any help!

I look at HA as more of a decorative feature of the home. Yes, we could no longer live without our "invisible hand" turning lights on and off, fans responding to our every humidity whim, and are team of personal servants (Alexa, Echo, Computer, Ziggy, and Amazon) ready to help as servants do (or do not!). Funny, there are (actually) those among us who prefer to apply electrons the old-fashioned way. I decorate my home for me with little thought of the next buyer. Love me love my HA is not my mantra. Life is short. Live for my own enjoyment. The next buyer can either expand on my vision, suffer over my "hallucination" , or just give-up and pull the whole darn thing out. I am never going to stress over their decision much as I'm sure my seller never stressed over leaving me green shag carpets. e-gad!

@KentinadaI am not sure. I only use the T6 as connected directly to Polisy. Since it is Z-Wave, I suspect it doesn't support a cell phone app - BUT I don't know for sure.

I have been using this native z-wave Honeywell thermostat for several years. It was easy top connect and works well. No node servers needed. Honeywell TH6320ZW2003 T6 Pro Series Z-Wave Stat Thermostat

Upgraded with no issues on Polisy. Thanks UDI Team!!

I'm not a developer but, on the hardware side, this looks like a good inexpensive solution to presence detection. I would purchase a copy of a node server supporting this if/when this becomes available.

Hi @baabm, I'm not sure what you mean by the "Telegram Service device" My Admin console view is attached. Where do I click to find the Telegram Service Device??

Updated successfully. Thank you to the UDI team!!

I agree with @brians, The last time I tried this was with Polisy and a Zooz 700 dongle. The only way I was able to maintain the zwave node numbers was to factory reset the dongle and then re-add the devices in the same order as previously added. With ~45 devices, it was a giant PIA. One mistake and start over. Probably better to re-add the device, accepting the new z-wave node and then fix any program issues.