-
Posts
4644 -
Joined
-
Last visited
Everything posted by Jimbo.Automates
-
My old PLM finally started to die and I've replaced it with a v2.4 that I had already purchased. I have been writing changes to all my battery devices and all are done except one mini remote that keeps failing with the exact same error every time I try. e 08/18/2020 12:07:40 PM : [1C 47 E2 1 ] Memory : Write dbAddr=0x1005 [0E] cmd1=0x20 cmd2=0x0E Tue 08/18/2020 12:07:40 PM : [INST-TX-I1 ] 02 62 1C 47 E2 0F 20 0E Tue 08/18/2020 12:07:40 PM : [INST-ACK ] 02 62 1C.47.E2 0F 20 0E 06 (0E) Tue 08/18/2020 12:07:49 PM : [INST-TX-I1 ] 02 62 1C 47 E2 0F 20 0E Tue 08/18/2020 12:07:49 PM : [INST-ACK ] 02 62 1C.47.E2 0F 20 0E 06 (0E) Tue 08/18/2020 12:07:50 PM : [ZWAVE-RX ZW041_1] [32/02] CC=0x32 cmd=0x02 [21640194205B007701941FFF] ACK,AUTO,EXPLORE From=0x29 Tue 08/18/2020 12:07:58 PM : [INST-TX-I1 ] 02 62 1C 47 E2 0F 20 0E Tue 08/18/2020 12:07:58 PM : [INST-ACK ] 02 62 1C.47.E2 0F 20 0E 06 (0E) Tue 08/18/2020 12:08:02 PM : [1C 47 E2 1 ] Memory : Write dbAddr=0x1005 [0E] cmd1=0x20 cmd2=0x0E - Failed I am preforming the updates the same way I did with everything in the same location and this one consistently fails. I've also tried starting over with a restore device, then tried factory reset followed by restore device, all fail in the exact same line.
-
Thanks Larry, but firewalla support figured out what is happening, damn google wifi is responding to the DHCP request when it shouldn't... I'm bummed I need to dump the google wifi, it's been a no brainer and has just constantly worked, but it doesn't work in bridge mode. Looking at the new Orbi's now...
-
I have a new router, a Firewalla gold, and now when I reboot either of my ISY's they both have issues with DHCP and the error and memory lights constantly blinking. I have it configured correctly on the router, but the ISY is saying there is an IP Conflict, when there is not. Sun 2020/08/09 01:44:21 PM System -100 [DHCP] state=INIT Sun 2020/08/09 01:44:26 PM System -170001 [Network] Error: IP Conflict Sun 2020/08/09 01:44:37 PM System -100 [DHCP] Failed Starting Client If I change the DHCP reservation to a different IP, then restart the ISY it works, but then the next reboot as this same issue.
-
I would like to, but still a haven't had the time. Sent from my Pixel 3 XL using Tapatalk
-
Google Home spokens won't turn off scenes
Jimbo.Automates replied to Eyeflydoc's topic in Google Home
@bmercier had discussions about scenes a while back, I looked for the post but couldn't find it. Scenes used to be only for Google "routines" or something, but I don't remember the current status. -
Submit a support ticket and they will help. Do you have the Pro? If not you should do the upgrade. Sent from my Pixel 3 XL using Tapatalk
-
Go to the node server menu in the admin console and delete it from there. Not at a computer so can't say exact steps. If it didn't delete from ISY when deleting from Polyglot, that means Polyglot connection to ISY was not completely functional. Sent from my Pixel 3 XL using Tapatalk
-
@TexMike Did you all notice they state:. Our warranty is one year(12.6v charger). Life can be 2 -3 years if you use 12.0v special charger I guess I'm not surprised, but not sure how you know when it needs to be replaced? Sent from my Pixel 3 XL using Tapatalk
-
Nice! Thank you. Sent from my Pixel 3 XL using Tapatalk
-
Did yours arrive and did it work? If so, please send me a link to what you ordered.
-
It's discussed here https://forum.universal-devices.com/topic/25016-polyglot-nodeserver-monitoring/ The nodes sends a DON/DOF to the controller node every longpoll. Sent from my Pixel 3 XL using Tapatalk
-
All my nodeservers have heartbeats, and a couple others I added it to, but not Nest. Sent from my Pixel 3 XL using Tapatalk
-
It's mentioned in the doc https://github.com/Einstein42/udi-ecobee-poly Sent from my Pixel 3 XL using Tapatalk
-
Check the ecobee nodeserver log for errors, add a heartbeat monitor for it on the ISY to make sure it's always running. Post issues with the ecobee nodeserver in the subforum so other ecobee users see it sooner. Sent from my Pixel 3 XL using Tapatalk
-
You add the ISY scene as a light in Google home. Sent from my Pixel 3 XL using Tapatalk
-
Just red error light blinking means SD Card issues https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help Sent from my Pixel 3 XL using Tapatalk
-
I think the Google home scene category is for use with Google routines only. Sent from my Pixel 3 XL using Tapatalk
-
Thanks for this! My ISY is not near my UPS so I've been wanted to get a small one for that closet and this was perfect! Powers the little Ethernet switch, CAO Wireless Tag Manager, and ISY. Three wall warts put in spare parts bin
-
Is this on Polisy? Directory permission needs to be opened up for the polyglot user. PermissionError: [Errno 13] Permission denied: './logs Sent from my Pixel 3 XL using Tapatalk
-
Anyway to push voice alerts/notifications to Home?
Jimbo.Automates replied to switzch's topic in Google Home
Nice! I had previously setup https://github.com/greghesp/assistant-relay which is what HomeAssistant is using, but there were many problems, now there is a new version that looks to be much better. It's on my list to look at again and add to the Notification Nodeserver someday. -
You can use ${sys.node.n014_timedata.driver} where driver is whichever one represents the name of the Day. You'll have to look at the profile to figure that out. Sorry, could provide more details when I have time or the author can replay.
-
Google Home can no longer sync devices
Jimbo.Automates replied to Jimbo.Automates's topic in Google Home
Yes I had hoped that was the case but not one of them ended up in a GH room. Sent from my Pixel 3 XL using Tapatalk -
Google Home can no longer sync devices
Jimbo.Automates replied to Jimbo.Automates's topic in Google Home
@bmercier thanks for confirming about accounts. Sent from my Pixel 3 XL using Tapatalk -
Google Home can no longer sync devices
Jimbo.Automates replied to Jimbo.Automates's topic in Google Home
@bmercier Really appreciate you looking into this. One question, when you say "MUST BE THE SAME AS THE ONE GH WAS LINKED TO" you are saying the Portal account email address must be the same as the Google Home user I used to add the account? That's never been the case for me and it's always worked. The reason it ended up this way is I used my personal email for the Portal when I originally created it long ago, but the account I use for Google Home is a shared account that my wife and I both have access to. So, in GH when I link to Universal Devices I use the shared account, but when the authorization for Universal devices comes up, I use my personal account since that's what is used in the portal. This should be remember so it knows how to sync, right? To answer your questions: 1. I've never had this problem before, it just started recently. It was working before, but I've no idea they last time I used it. 2. Yes, the sync does work! I never even looked because I just assumed it didn't work due to the error. - Jim -
Google Home can no longer sync devices
Jimbo.Automates replied to Jimbo.Automates's topic in Google Home
Wow, this post sure went of the topic... Thanks guys [emoji18][emoji849] Sent from my Pixel 3 XL using Tapatalk