roblombardo

Yes, replacing the power supply did solve the issue. I did notice that the power supply I was using, (possibly not the original one) did not have the capacity directed by Michael for the replacement. This doesn't appear to have been the issue however, as it just failed.

Just a heads up to the community. I recently had my Policy start crashing periodically and restarting, then it would be down for lengths of time. I finally submitted a ticket and Micheal was fairly quick with a reply to replace the external power supply. Tentatively, this looks like it's solved the problem and I noticed the LED on the power supply was no longer lit. It was providing some power because the third light was flashing, but was unable to carry the load apparently. This does not appear as a troubleshooting step to the third light blinking problem in the manual. So, information for those in a future search.

I originally ran my HA in a docker (they call it something else now) container on Synology. I don't remember it being to difficult to install, but that was long ago.

1) Add eISY devices to home assistant through the UDI integration. 2) Install Homekit bridge in home assistant. Expose devices desired for control. 3) Use Siri for voice control. Note: As an additional benefit, if you have added a garage door opener, this will be exposed via Carplay automatically when within about 2 miles of your home!

I am using the same as the control mechanism. I use a custom mushroom template card in home assistant as the control interface.

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.

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?

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.