roblombardo

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.

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.

@JBlake01, +1. Looks like you and I are having the same issue. I also submitted a ticket. I only have the Ring pro doorbell, you probably have more Ring devices.

5/15/2023, 06:58:08 [pg3] info: Verifying node servers are installed on IoX correctly 5/15/2023, 06:58:08 [pg3] info: IoX entry for Ring::2 OK 5/15/2023, 06:58:08 [pg3] info: IoX entry for WirelessTag::4 OK 5/15/2023, 06:58:08 [pg3] info: IoX entry for WeatherBit::5 OK 5/15/2023, 06:58:08 [pg3] info: [00:0d:b9:53:30:34_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB. 5/15/2023, 06:58:11 [pg3] info: [00:0d:b9:53:30:34_4] wtcontroller reporting command DOF 5/15/2023, 07:03:08 [pg3] info: Verifying node servers are installed on IoX correctly 5/15/2023, 07:03:08 [pg3] info: IoX entry for Ring::2 OK 5/15/2023, 07:03:08 [pg3] info: IoX entry for WirelessTag::4 OK 5/15/2023, 07:03:08 [pg3] info: IoX entry for WeatherBit::5 OK 5/15/2023, 07:03:08 [pg3] info: [00:0d:b9:53:30:34_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB. 5/15/2023, 07:06:52 [pg3] info: Getting push notification API token 5/15/2023, 07:06:52 [pg3] error: Failed to get push api token: 5/15/2023, 07:06:52 [pg3] error: Error: Request failed with status code 401 5/15/2023, 07:06:52 [pg3] error: getPushToken: Failed with Cannot read properties of undefined (reading 'data') 5/15/2023, 07:06:53 [pg3] info: call_udx: Making reqeust to socket for /rest/pg3.auth.ns 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.auth.ns on socket happened. 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.auth.ns on finish happened. 5/15/2023, 07:06:53 [pg3] info: call_udx: incoming chunk {"status":"success"} 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.auth.ns returns {"status":"success"} 5/15/2023, 07:06:53 [pg3] info: Successful login by admin 5/15/2023, 07:06:53 [pg3] info: Updating mqtt frontend password to jwt token 5/15/2023, 07:06:53 [pg3] info: call_udx: Making reqeust to socket for /rest/pg3.frontendpw.ns 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.frontendpw.ns on socket happened. 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.auth.ns on close happened. 5/15/2023, 07:06:53 [pg3] info: call_udx: /rest/pg3.frontendpw.ns on finish happened. 5/15/2023, 07:06:54 [pg3] info: call_udx: incoming chunk {"status":"success"} 5/15/2023, 07:06:54 [pg3] info: call_udx: /rest/pg3.frontendpw.ns returns {"status":"success"} 5/15/2023, 07:06:54 [pg3] info: call_udx: /rest/pg3.frontendpw.ns on close happened. 5/15/2023, 07:06:57 [pg3] info: [00:0d:b9:53:30:34_2] Retrieved customparams 5/15/2023, 07:06:57 [pg3] info: [00:0d:b9:53:30:34_2] Retrieved oauth 5/15/2023, 07:06:57 [pg3] info: [00:0d:b9:53:30:34_2] Retrieved customparams 5/15/2023, 07:06:58 [pg3] info: Starting log stream for pg3frontend_tU7vY :: /var/polyglot/pg3/ns/000db9533034_2/logs/debug.log 5/15/2023, 07:08:08 [pg3] info: Verifying node servers are installed on IoX correctly 5/15/2023, 07:08:08 [pg3] info: IoX entry for Ring::2 OK 5/15/2023, 07:08:08 [pg3] info: IoX entry for WirelessTag::4 OK 5/15/2023, 07:08:08 [pg3] info: IoX entry for WeatherBit::5 OK 5/15/2023, 07:08:08 [pg3] info: [00:0d:b9:53:30:34_1] Unmanaged NodeServer 'ISY Portal' found. Adding to DB. 5/15/2023, 07:08:11 [pg3] info: [00:0d:b9:53:30:34_4] wtcontroller reporting command DON

Mine seems to authenticate, buy remains disconnected. I'm at a loss for what to do next.

Thanks for the heads up. Establishing a direct IP connection allowed me to reconfigure and reconnect the variables. Going back to the portal connection switched the “Update ISY State Variable” toggle to off again and unset the variable. I’m going to run a direct IP connection for now. My use of geofencing is trivial anyway. I’m also experimenting with running UD mobile in the background solely for this purpose.

I have lost the ability to update state variables via location services on Mobilinc about the time I updated to 5.6.0. Not sure if these are related, anyone else having this issue? H I’d hate to run UD mobile in the background just for geofencing.

@Illusion Did that solve your Mobilinc problem?

@Illusion Yes, working great. I always used Mobilinc Pro in the distant past when I used ISY portal as well. Are you confident you have your configuration in the app and ISY admin console correct?

@Illusion, I've made the transition back to ISY portal. I feel fortunate that I exported my configuration before I switched to Mobilinc Connect. It is my understanding that if you want to do IoP, you have to use ISY portal. I find the ISY portal method of configuring Alexa spokens slightly less elegant than Mobilinc Connect, but on the plus side, ISY portal is much cheaper and significantly faster to execute.