simplextech

@carealtorin a quick test I also installed HASS on my UnRAID server and in my development server. Both same results with my prod ISY which has several nodeservers. However with my dev ISY which currently only has 1 NS the Withings one I'm working on it loads and parses just fine. So the result stands that there is a problem with the HASS ISY component and Nodeservers. Now to find which nodeserver is the problem...

Yes it runs as a docker container and no 0.103 doesn't run just fine. Not for my setup. I just updated to 103.4 and the same error. Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 172, in _async_setup_component hass, processed_config File "/config/custom_components/isy994/__init__.py", line 477, in async_setup log=_LOGGER, File "/usr/local/lib/python3.7/site-packages/PyISY/isy.py", line 82, in __init__ self.nodes = Nodes(self, xml=self.conn.get_nodes()) File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/__init__.py", line 89, in __init__ self.parse(xml) File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/__init__.py", line 288, in parse Group(self, nid, nname, members, controllers), File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/group.py", line 33, in __init__ for m in self.members File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/group.py", line 33, in <listcomp> for m in self.members AttributeError: 'Nodes' object has no attribute 'status' Now I'm just interested and I'll have to dig into this some more. However this is the error I get with my prod ISY with devices and nodeservers. This ISY is 5.0.16B (was A) and I've been having this error. I can change the configuration and point to my other ISY without nodeservers and everything works perfectly.

I don't mix installs. My nodeservers are running on Polisy for my production system and my dev box is dedicated. I'm currently running Hass.io on a rPi4 What version of HASS? I'm currently on 0.103.0 and tested with the native component and HACS component and they both throw the same errors. I've reported the errors to @shbatmas well.

Version? I "have" run this configuration as well but in the latest it's broken....

I have Hue and LiFX. I recently migrated mostly to Hue and I use Network Resources and the Hue Polyglot Nodeserver which is very good too.

@EddieRocka single pane view would be nice I agree. Home Assistant is a way of doing this but as currently (verified again this morning) it doesn't load and work with NodeServers which is not good. The alternative would be then to move nodeserver functions out of the ISY and use HASS components to achieve the single pane view which is doable but now there are two systems to maintain and configure and dual automations to manage or to try and sync state from HASS to ISY for the ISY to manage/run the programs. A perfect setup would be a fully integrated web interface for the ISY which could integrate cameras and other devices into a single pane view. Why has this not happened yet? Nodeservers are still relatively "new". As they are new, the UI projects haven't caught up to speed yet with Nodeserver paradigm presentation, functionality is still in development which makes it hard for 3rd parties to support. There's many systems out there that can provide a "overall" view of a system and ISY devices... just not so well with Nodeservers... yet. If you don't mind running a multi-controller setup and maintaining multiple environments and the troubleshooting involved of figuring out which system is the issue then there's several options. Home Assistant, HomeSeer, Allonis MyServer, Charmed Quark (CQC). When will a nice integrated UI with nodeservers be available? My guess is when a developer with a personal need or interest decides to write it. Or there's enough demand to make into a product that can actually make a profit over the long term. Historically the ISY has been a Insteon, X10, Z-Wave device controller. These are devices, physical, static. Introduction of Polyglot expands the horizon to new devices, new concepts and requires a new presentation capability.

You can... but... the current HASS components do not work correctly when you have Nodeservers in your ISY. The HASS ISY component (HASS native and HACS) error on startup and will not load. Which means none of the ISY devices are visible/usable which makes the interface non-functional, non-usable.

I don't think you are or are trying to bash anything. Having strings support isn't a UI function actually it's lower level in the device status and variable. Presenting that is the UI and thus presenting it without having to restart the UI would be very nice. A "good" UI is all in the beholder as what some call ugly I call utilitarian and I like that it "just works" versus having to constantly baby sit it. As for HASS. Yes the Lovelace UI is very nice and if someone develops something even half as good that works with ISY that would be great and I would use it. Maybe I'll develop it... dunno I'm not a front end developer so that's challenging... but I have been thinking of it. But who's going to pay for it? Point is though as nice and pretty as the HASS UI is frankly they have spent the last year putting so much effort into making things "easy" and configurable through the UI that the real stability of HASS has suffered and for myself I can't have that. I can't have a pretty UI but unstable system because of the UI. I've been using HASS for several years and watched it grow and been through the upgrade pains and non-functioning system and starting from scratch... all because of UI changes for the most part. Given some were underlying core changes that were necessary and those I understand but when a system is made non functional because of the UI? No... not acceptable. I also was a user and developer for another big name and I moved on from that. Because of them changing the core to appeal to users wanting a "new UI"... and this new UI appeals to a fraction of existing users and is meant to attract new fresh users (read fresh fast money) but changing the core to match the UI is backwards and has and will lead to problems and I'm just glad it's not my problem. It probably sounds like I'm arguing and then agreeing. Kinda back and forth huh? I am. I think a UI would be a nice enhancement but I don't want it bad enough to sacrifice the reliability of the system which means I don't want UDI putting resources towards something which would take away resources from other areas. Now if UDI was made of money and had resources to spare then great... would love it! I doubt they do though. Today if I'm away from home and I need something simple to turn on/off or check something there's already Mobilinc, Agave, eKeyPad Pro or the basic web interface. If the use case is "basic" as you suggested... aren't your requirements already met?

The ISY doesn't have a "user interface". There's an "admin console" for administration but otherwise it's a automation system. There has been a market for mobile access and Mobilinc, Agave, ekPro have filled that niche and I'm sure there will be others. When a large enough demand for a web UI emerges I'm sure someone will fill that niche as well. Until there's either a personal drive or monetary drive for development or enhancement I don't think it will happen. I've said it before that I'm happy I don't see UDI wasting resources on making a UI pretty (I want string support and dynamic updating rather than restarting and having to re-upload/process profiles). Otherwise I don't care as long as it's reliable and functional over pretty.

Sounds like it might be dead... replace it.

Not necessary when just doing firmware upgrades. I've upgraded several ISY's a few times with Z-wave. Just make a z-wave backup first just in case.

Ok. It's odd that node remnant are still in the right panel but not in the node list. You could try running a synchronize. This will take a while with as many z-wave devices as you have but it will interrogate each node in the z-wave module db and isy and compare and synchronize them. Admin Console Z-Wave menu -> Tools -> Synchronize Nodes -> All

Actually I don't care so much for what the whiteout is covering. I'm more concerned about helping you enter the modern age of taking screenshots from your computer and being able to edit them without having to use your phone, email them to yourself, etc etc... Whatever you may be hiding under the whiteout is your concern... if that is whiteout?

I have to ask... why does it look like whiteout on your screen? And it looks like you're taking a picture of your screen with your phone? or other camera? Why?

The motion sensor works fine. I have several deployed in daily use. This is a "motion sensor" NOT a multi-sensor so the temp, lux, etc are NOT meant to work outside of the device even though they are "visible" to and presented by the ISY. So do not run around in circles about these items. The MSII has a couple product defects. 1. the internal motion sense timer doesn't reset properly so using the MSII for controlling lighting and using the auto off/reset of the lights doesn't work. This is a device problem not ISY and nothing UDI can do to fix this. There's also a device problem with LED not being able to be turned off when on battery. Again device problem not ISY. Outside of setting expectations correctly and the two issues above. Yes the MSII works great. I use the on-only mode for scenarios where I want very fast lighting response and that gives me great flexibility using ISY programs to determine when to turn things off based on things besides motion.

For what it's worth I also have half a dozen 2421 sensors and no false opens on them. I do have random long delays of reporting "on" from them but no false reporting.

Been very busy bee's with the documentation.... good job.

The physical wiring is the same. Regardless of using an ISY or Insteon Hub or No hub/controller at all. Follow the wiring instructions but you can ignore the "configuration" instructions as they are intended for use with the Insteon Hub or direct linking. For a 3 way you will not wire the second switch with a traveler like a normal 3-way switch. You will wire the first switch controlling the load just like any normal switch with a load. The second switch will be wired with power/neutral but without a load. Cap off the red wire and any remaining wire in the box. (generally the traveller). Verify the first switch is physically controlling the load correctly. Then you can link the switches either via ISY or direct that is all up to you but I recommend using the ISY as it just makes it easier.

If you're ISY is default (DHCP) and the Google Wifi does not have a DHCP reservation defined for the ISY then how in the world have you kept the same IP address forever? Suppose it is possible if you've never had the ISY disconnected from the network for any period of time. Amazing actually. I think you'll have to wait for UDI and see if they can do a remote session to debug this but it all smells of a network issue.

Was the IP address the same or different from before the re-install? May have been asked already but is your ISY configured with a static IP address or DHCP?

No DHCP reservation.... so the IP address of the ISY could have changed during your testing and rebooting and such. Have you cleared your java cache and downloaded and installed the ISY finder during any of this?

I've been giving this a lot of thought recently..... I looked into Home Assistant again and their native and hacs component for ISY. Neither are even loading or working if Nodeservers are present so this is a non starter. I looked into OpenHAB and their binding. It's deprecated and not maintained. Probably wouldn't work correctly so I didn't continue looking. If someone else runs OpenHAB with the ISY binding please let me know how well it works and particularly with Nodeservers. Currently none of the mobile apps (eKeyPadPro, Agave, Mobilinc X) support nodeservers. I've heard from all of them they are "looking into it". At what time frame is unknown and which developers they are working with to test/validate nodeservers? I think HAD or a variation of it is still viable and could be continued. However at what level of interest from people and at what cost? (development time).

As mentioned earlier all of this is pointing towards some network issue. I went back in the thread and you said you don't have a "Port" reservation. But do you have a DHCP or Host Reservation within the Google Wifi router? I know nothing about the Google Wifi or how/what they may call it but it should not be "Port". Does the AC still work only sometimes? after a ISY reboot it works and then stops working?

It sounds like there's a lot of issues and a lot of changes before, after, during this whole debacle. Have you contacted UDI support? Can they look at your system and try to get things working? From the Portal and AC side I think UDI should look to verify the portal registration is good.

Doing the linking from the ISY gives you the best of the technology. Without the ISY managing the switches you can't use them in a program. The devices are still inked and still work without the ISY being online just like they would with direct linking. So you lose nothing but gain the ability to use them with ISY programs.