roblombardo

Yes, but I was able to access AC locally. After a post rollback reboot, I appear to be good. It's only been 24 hours, but so far so good. Try one click on the front button for firmware upgrade (downgrade at this point). Perhaps the Polisy will roll back to 5.8.4?.

That's probably how it went down, I left out of town on Friday evening and just got back to it today.

There is only a "multifunction button" accessible through a tiny hole with a toothpick or paperclip. It doesn't seem to have exactly the same functionality as the Eisy. I did submit a ticket and was advised to reboot again. I had already done this twice at least and physically removed power from the PLM and the Polisy. It's conceivable an update was pushed in the background, I'll give it some time and see if this resolves the issue.

I'm having the same issue on Polisy. I was going to try this solution, but Polisy has no red power button.

All good here. If I remember correctly, the portal at slot 1 was deprecated. I remember removing it, but cannot remember the procedure.

Through the use of the UDI ISY integration, homeassistant can control all of ISY on any UDI device. ISY cannot easily control functions of homeassistant however. There are convoluted work arounds, but you'll generally want to avoid this. I use some scene helpers in ISY to sync scene status, but it is a kluge. Also, while homeassistant can command all aspects of ISY programs, but, due to the one-way nature of the communication, it will not be aware of their true/false state or if they are enabled or not. I am currently using homeassistant as an informational/control interface on a wall mounted dashboard and mobile dashboard to great effect. 99% of my conditional logic runs on Polisy however. I have attached a screen shot of my wall dashboard as rendered on a computer monitor. It would appear slightly different on the wall tablet as it is customized for that interface, some header elements to the right size are not visible there.

Any idea how to structure this hint in the editor? In appears to be prompting something like an IPv4 address structure? I have a basic familiarity with homeassistant YAML. This may be too advanced for me.

The value shown in Mobilinc Pro for the YoLink Outdoor Motion sensors and contact sensors is "1 idx". This does not appear to change regardless of state of the device. The state is shown correctly in the admin console, and can be used as such in programs. This is perhaps not an issue with the nodeserver at all. Any ideas?

This must be on MacOS. I suffer the same, an improvement here would be nice.

I had originally done as @elvisimprsntr above. But I then migrated to an instance of Scrypted, as my NVR, with the HomeKit plugin for video. Now I’m using Home Assistant with the HomeKit integration for all other devices. So that is another option.

I recently had a similar issue where the app was launching off screen to the left. This was likely an artifact from using a second monitor at one point. You'd have to look up the exact key combination, maybe Alt>Space>m or something, but it allows you to move the window when you can't drag it with the header. This of course may not be your problem, but it sounds familiar.

There will be no impact to the transformer, switching the output. You could use the Z wave device as a pilot relay, but likely the device has a sufficient contact rating for your load anyway. But, if you would like to relocate that wear to an easily replaced ice cube relay, you could do that. You would just use a 12V source ahead of the Z wave device through the contacts on the Z wave relay to the coil on the new load relay.

Thanks.

I inadvertently introduced a "/" into my group name which was accepted. Now, when selecting the group, an error message is presented which disallows any further advance to the point where the group can be deleted. See attached screen capture. Any solution?

Very much viable. I know the developer has largely deprecated it, but it is still is available for purchase on the App Store. The problem will come when a new iOS version renders it inoperable. Then, I don't know if they'll be any motivation on the developers part to update it. I find it to be the best mobile control interface out there. I am on the latest version of iOS (16.6), on an iPhone 14 Pro.