Jump to content
c4forums | The Control4 Community

dw886

c4Forums Member
  • Posts

    220
  • Joined

  • Last visited

Recent Profile Visitors

1,083 profile views

dw886's Achievements

Community Regular

Community Regular (8/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

22

Reputation

  1. Is there a way to programmatically change the icon for a scenario button? Background: I'm having issues with the Pentair IntelliCenter driver in one project (I have another project that works fine) where when something is toggled in the driver it turns on, and then a few seconds later goes back to off - both are running the same version of the driver, so I'll have to call in to have someone take a look at it. In the mean time to work around it I used an Experience button (like Waterfall) for turning on the pool waterfall - there's no timers set within the project - they're only ON / OFF buttons. The IntelliCenter is running it's own timers, so when certain things (water features, heat modes, lights, etc) are turned on, the Intellicenter has an egg timer where it shuts these things back off after a set period of time. The problem that I have is if something is turned on via the Control4 interface (like the fountain), the experience button icon changes, however when the IntelliCenter turns them back off after the egg timer expires (or someone uses the Pentair panel or mobile app), the Control4 icons are out-of-sync. I can see these events in the driver, and can program off of them, but I don't see any action for the experience button other than "Select" or "Device Specific Command: SetCountdown". Is there not a way to change the state of the button to a specific state (Off or On)? If it's just "Select" this would be like a power toggle on the a TV, you're firing a command and not understanding the current state. The only other option that I see is to fire the event, run a conditional check that looks for the "State" device variable on the Experience Button, and then if the state is on and it's supposed to be off, fire the select command to toggle it... Is there a better approach?
  2. I work on pools as well as control4. Just a point of clarification in this thread because it seems that there is some confusion as to what equipment people have. Easytouch / Intellitouch are both systems that were designed 10+ years ago that are still being sold. Intellitouch just has more expansion capabilities than the Easytouch, but both are largely the same, and the panels have no rj45 port on them. The 4 wire bus from the panel either connects to a wireless module that gets mounted by the panel and sends the 4-wire signal wirelessly to a receiver that connects to the screen logic adapter which has the rj45 network port jack for network connection, or you need to run the 4 wire from the panel directly to the screen logic adapter, which has the rj45 port that gets connected to the network. Easytouch has no control4 driver. Intellitouch has a driver and can be connected but it's a bit of a mess and requires finding some old hardware. Easytouch looks like this. Intellitouch looks almost the same but doesn't have a screen. Intellicenter is the newer system that has a touchscreen on the actual panel in the load center. This was in development and announced like in 2017, but didn't really hit the market until like the mid/end of 2019. The dates and the touchscreen will both help you understand which one you have. The intellicenter has an rj45 port directly on the circuit board (on the back of the panel). If you don't have a network cable run to the load center, then Pentair sells a kit that basically is a bridged AP. It connects to the rj45 on the intellicenter panel with a POE injector to power it, and you set up the AP to connect to your existing wifi bridging the connection to make the intellicenter part of your network. Intellicenter has a Control4 driver, and if your intellicenter is connected to your network, no additional hardware is required. Integration works reasonably well. I have seen sometimes when turning off an intellicenter circuit (which could basically be like a slide or something) the driver will toggle it back and forth multiple times before completely turning it off. Other than that, adjusting heat settings etc all seems to work reasonably well. Intellicenter lacks buttons and instead has a touchscreen. Looks like this:
  3. Anyone else that's using this driver recently start getting failures? This quit working for me - the MP3 file never gets updated. When I look at the Google API, i can see that failures started sometime around the very end of Feb / beginning of March: Looks like something is failing when calling the Google Text to Speech API, but I cannot see the failure to see if it's a misconfiguration issue on my Google account, or if it's something with the driver.
  4. My point isn't so much about having an issue, it's more about the fact that it's perceived as "random". I work with software, and I know, there's very little that's "random" unless you're calling random in your code intentionally. Code doesn't "randomly" work. There's always a reason why these things work the way that they do. I'm more concerned with the lack of accountability. I played this whole thing out with UBNT support just to see what happens, and how they troubleshoot. What I'm learning is that they don't. I gathered heaps of logs, tried to help them help themselves help me, and at the end they threw their hands up, and said the obvious "the unit seems to have some internal issues". We have no idea at this point if it's the hardware, the software, or possibly the config. So right now, we go down the RMA path, and may well be at the same point 3 weeks from now if it's a software issue or an issue with the config. Day 1, chat goes for 3 hours, chat agent "moves incident to Tier 2" via email and asks me to reply to the initial email with the logs. Day 2 @ 4:56pm, email support rep finally picks up the case, and replies asking me to send the "support info" file, which I had given via chat on Day 1. I replied with that, and gave them the exact lines in the log to look at to try to determine what was taking place. I know within a few minutes of when things went offline, because I can see them go offline in OVRC, and it correlates to lines in the log that show the switch in the UDM restarting. Day 3, no updates Day 4 @ 12:55pm, email support agent says "I am escalating this to our Tier 2 Team and they will get back to you as soon as possible.", which is what the chat agent told me on Day 1 Day 5 @ 5:52am, email support replies and says: "The unit seems to have some internal issues. I'd suggest performing the Recovery as suggested in the below-given help article and see if that fixes the issue. https://help.ui.com/hc/en-us/articles/360043360253-UniFi-UDM-UXG-Emergency-Recovery-Mode-UI If that doesn't help, you can go ahead and file the RMA. Hope that's helpful. If you have any other questions, please let us know!" The moral of the story here is that you'd better have backup hardware on hand, and don't waste time expecting them to diagnose and fix an issue. It's far cheaper for them to send you a $379 UDM than to put someone on this that's skilled enough to dig in.
  5. Yeah, I agree that everyone has a story like this with some brand. I'd also say, things will go wrong at some point with everything. I'm just trying to understand how well the support side works with Ubiquiti when things go south. Yes, I have a backup. Yes, I've done the factory reset (last time this happened on Jan 28 I did both assuming something had been corrupted). I'm not using the SFP ports regularly, but in testing the last time this happened, I threw a RJ45 SFP module into the LAN SFP port and connected copper via that SFP. When the switch goes down in the UDM pro (all 8 RJ45 ports), the LAN SFP port continues to function. Everything is running on the stable release, not on beta. If I power cycle enough times, I'm assuming it'll fix it - last time about 10 power cycles did the trick. Factory reset, restore from backup, etc all didn't do anything, but enough reboots seemed to have done it last go round with this gremlin. This time, I'm waiting to see what support says before doing the reboots. They have the full logs. Right now anything connected to the SFP port on the UDM pro can egress to the WAN. Anything connected to the RJ45 ports on the UDM-Pro cannot egress, and the gateway cannot be reached from devices behind those ports. Feb 22 07:02:13 UDMPro syslog.warn kernel: [1668166.302652] systemd-journald[31]: /dev/kmsg buffer overrun, some messages lost. Feb 22 07:02:13 UDMPro user.info kernel: [1668166.303387] al_eth 0000:00:03.0: al_mod_eth_function_reset: performing FLR Feb 22 07:02:13 UDMPro user.info kernel: [1668166.308789] Configured MAC to RGMII mode Feb 22 07:02:13 UDMPro user.info kernel: [1668166.309496] al_eth 0000:00:03.0 switch0: using MSI-X per Queue interrupt mode Feb 22 07:02:14 UDMPro user.info kernel: [1668166.956394] eth [al_mod_eth_3]: set link speed to 1000Mbps. full duplex. Feb 22 07:02:14 UDMPro user.info kernel: [1668166.956406] al_eth 0000:00:03.0 switch0: Link is Up - 1Gbps/Full - flow control off Feb 22 07:02:23 UDMPro user.err kernel: [1668176.240055] al_eth 0000:00:03.0 switch0: al_mod_eth_reset_task restarting interface Feb 22 07:02:23 UDMPro user.err kernel: [1668176.278978] udma [eth tx 2]: al_mod_udma_q_pause timeout waiting for dcp==crhp Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293846] [0479](ffffffc01e921df0): 9d0000fd 00000000 9b64c846 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293851] [0481](ffffffc01e921e10): 9d000066 00000000 9b64cc3e 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293857] [0483](ffffffc01e921e30): 9d00004e 00000000 635305ca 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293862] [0485](ffffffc01e921e50): 9d00003c 00000000 b56d303e 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293864] [0486](ffffffc01e921e60): 9d00004e 00000000 b82af84a 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293867] [0487](ffffffc01e921e70): 9d000047 00000000 b82aecca 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293869] [0488](ffffffc01e921e80): 9d00006a 00000000 b82ae14a 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293872] [0489](ffffffc01e921e90): 9d000065 00000000 b82adf4a 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293877] [0491](ffffffc01e921eb0): 9d000052 00000000 b82ad94a 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293882] [0493](ffffffc01e921ed0): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.293889] al_eth 0000:00:03.0 switch0: UDMA0 Primary GROUP D cause reg: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294031] al_eth 0000:00:03.0 switch0: msw_drop_sop: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294037] al_eth 0000:00:03.0 switch0: msw_wr_eop: 0x00010da5 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294044] al_eth 0000:00:03.0 switch0: tso_no_tso_pkt: 0x0000021f Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294050] al_eth 0000:00:03.0 switch0: tso_seg_pkt: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294053] al_eth 0000:00:03.0 switch0: tso_pad_pkt: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294059] al_eth 0000:00:03.0 switch0: tmi_in_tx_pkt: 0x000001e0 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294066] al_eth 0000:00:03.0 switch0: tmi_out_to_rx: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294072] al_eth 0000:00:03.0 switch0: tx_q_bytes[i]: 0x00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294075] al_eth 0000:00:03.0 switch0: tx_q_bytes[i]: 0x0000003c Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294081] al_eth 0000:00:03.0 switch0: tx_q_pkts[i]: 0x000001df Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294087] al_eth 0000:00:03.0 switch0: tx_q_pkts[i]: 0x00000001 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294098] al_eth 0000:00:03.0 switch0: EC STATS: Feb 22 07:02:23 UDMPro user.info kernel: [1668176.294101] al_eth 0000:00:03.0 switch0: faf_in_rx_pkt: 0x00002333 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297210] [0983](ffffffc20705bd70): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297215] [0985](ffffffc20705bd90): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297219] [0987](ffffffc20705bdb0): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297224] [0989](ffffffc20705bdd0): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297227] [0990](ffffffc20705bde0): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297232] [0992](ffffffc20705be00): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297237] [0994](ffffffc20705be20): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297241] [0996](ffffffc20705be40): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297244] [0997](ffffffc20705be50): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297249] [0999](ffffffc20705be70): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297254] [1001](ffffffc20705be90): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro user.info kernel: [1668176.297259] [1003](ffffffc20705beb0): 00000000 00000000 00000000 00000000 Feb 22 07:02:23 UDMPro syslog.warn kernel: [1668176.302573] systemd-journald[31]: /dev/kmsg buffer overrun, some messages lost. Feb 22 07:02:24 UDMPro user.info kernel: [1668177.081974] eth [al_mod_eth_3]: set link speed to 1000Mbps. full duplex. Feb 22 07:02:24 UDMPro user.info kernel: [1668177.081988] al_eth 0000:00:03.0 switch0: Link is Up - 1Gbps/Full - flow control off Feb 22 07:02:33 UDMPro user.err kernel: [1668186.293135] udma [eth tx 0]: al_mod_udma_q_pause timeout waiting for dcp==crhp Feb 22 07:02:33 UDMPro user.err kernel: [1668186.306038] udma [eth tx 1]: al_mod_udma_q_pause timeout waiting for dcp==crhp Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333679] [0468](ffffffc05e9c9d40): 9d000052 00000000 b6d5a94a 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333682] [0469](ffffffc05e9c9d50): 9d00004e 00000000 2fb12082 00000002 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333687] [0471](ffffffc05e9c9d70): 9d00003c 00000000 b56d303e 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333692] [0473](ffffffc05e9c9d90): 9d00003c 00000000 b56d343e 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333697] [0475](ffffffc05e9c9db0): 9d00003c 00000000 6769f6ca 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333700] [0476](ffffffc05e9c9dc0): 9d00003c 00000000 6769f0ca 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333705] [0478](ffffffc05e9c9de0): 9d00003c 00000000 b56d1c3e 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333710] [0480](ffffffc05e9c9e00): 9d0002f0 00000000 b507b046 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333716] [0482](ffffffc05e9c9e20): 9d00003e 00000000 2fb13c92 00000002 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333718] [0483](ffffffc05e9c9e30): 9d000099 00000000 74caeec6 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333723] [0485](ffffffc05e9c9e50): 9d00003c 00000000 6769cfca 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.333728] [0487](ffffffc05e9c9e70): 9d000081 00000000 74caec46 00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.336150] al_eth 0000:00:03.0 switch0: MAC iofic Group B cause reg: 0x3c000395 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.336157] al_eth 0000:00:03.0 switch0: MAC iofic Group C cause reg: 0x00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.336164] al_eth 0000:00:03.0 switch0: MAC iofic Group D cause reg: 0x00000000 Feb 22 07:02:33 UDMPro user.info kernel: [1668186.336167] al_eth 0000:00:03.0 switch0: MAC iofic Group D mask reg: 0x3fffffff. masked cause 0x00000000
  6. Call this Karma, but everything went down last evening at 1:03AM, so I reached out to support via chat this morning. They basically told me to RMA without doing any troubleshooting. I pushed back, because I'd really like to find out if it's the device or something else. I was told that the only way to get logs is to get the UDM to be responsive, and get into the interface or SSH. All the RJ45 ports went down, and the whole network shows offline on the UDM touchscreen (0 devices, 0 clients, internet 'OK'). Wanting to get the logs, I hooked up to the SFP port, and could SSH into the machine only on that port. I downloaded the log files, and there's a bunch of things that happened to "switch0" at 7:02:13 AM GMT, which would be 1:02am my time. Chat guy said he needed to escalate, and it would be handled via email, with no ETA. To me, this isn't so straight-forward of an answer to the OP's question. Yeah, Ubiquiti has nice features, and it's far easier to sell a $179 Nano than it is a much higher priced 810 series Araknis or 4200 series PakEdge, but I don't like random gremlins, or not having a timeline on any type of resolution.
  7. Yeah, the UDM has auto install updates turned on for its firmware, so firmware is current (1.8.6.2969) and the network is on 6.0.43. When this happened, the UDM was completely unresponsive from the LAN, including SSH. Have you had a decent experience with the live chat?
  8. For those of you using Ubiquiti on installs, is there a "pro" version of support for hardware issues? I have a UDM pro that decided to stop functioning one morning at 6:15am - luckily it was on my network and not a customer's. I was working on my laptop hardwired in the office, and all of a sudden internet just stopped - had been happily running for a year without issue. UDM was completely unresponsive (ICMP, refused to route LAN --> WAN) although all of the lights were still on and blinking and the WAN connection was still up. Rebooted it about 5 times, and eventually tried using an SFP LAN port instead of the 8 RJ45 LAN ports. LAN SFP port would work, but none of the RJ45. Support via email took a day to hear back, and they suggested rebooting on every email response. Long story short, after about 20 reboots (and multiple emails from Ubiquiti support suggesting the same exact thing - reboots), it just started working again. Makes me real nervous that this could easily happen to a customer, and having zero root cause, and 5 emails from support all asking for the same "reboot" makes me question the reliability of the UDM Pro (and the support options). With PakEdge or Araknis, it feels like you'd have more options for support, and overnight hardware if you needed it, whereas with Ubiquiti, it's easier to manage through their interface, and cheaper, but I feel like there may be more risk? With Ubiquiti sometimes I feel like I'm a beta tester even though I'm not openly knowing it.
  9. My SR260 remotes all went from 2.1.120 to 2.2.27 with this update. 2 updated on their own. 1 got stuck downloading, and the one stuck remote seemed to stop all of the rest of the remotes from going. I had to reboot the remote that partially downloaded, and then reboot the rest of the remotes. About 60 seconds after a reboot they'd update.
  10. Did you ever get beyond this? I've been getting this for the last few days.
  11. I have it, and it seems to sync up states, however I do see some bizarre things here and there. For example, if I turn off a water feature (slide) from C4, sometimes the slide will go On / Off / On / Off / On / Off / On / Off (over and over for a minute or two) - this doesn't happen, but when it does, it makes you wonder what's happening. When this is happening, you can see the slider on the touchscreen going back and forth on it's own... I've also seen the same thing with the lights, where the lights will turn on, you'll change the color using C4 on the touchscreen, and the lights will turn off (when this happens I think that it's just the intellicenter adjusting the color, because it works by cycling the circuit x number of times to tell the lights what colors to use, and while doing this the lights remain off), however they will stay off indefinitely. I rarely turn things on via the IntelliCenter itself, we almost exclusively use a touchscreen that's near the patio.
  12. IntelliConnect is a new Pentair system that came out last summer. It gives control of a few devices (intelliFlo pumps, heaters, intellibrite lights via 1 of the 2 relays). It doesn't have valve controlling capabilities that the older systems (EasyTouch or IntelliTouch) or the newer Intellicenter has, nor the expansion options, but meets the needs of many pools. There's no Control4 integration at this point for the IntelliConnect.
  13. I've been getting the same messages, but I have been ignoring them. Do I need to worry about them? The email that I got today says "Your trial is over"... Curious if anyone has gone beyond the "trial" end date, and if so if it quit working...
  14. So now that there's a way to lock down individual touchscreens, is there also a way to lock down individual 4Sight users? They show up in the Identity agent, but aren't available as selections in the Access agent... From what I can gather, they all lump into the "Default" bucket, which could be customized, but it would see like a common request to limit some 4Sight users more than others (kids vs parents, owners vs visitors, etc).
  15. Is anyone aware of anything in the pipeline to add XTRA channels (streaming only channel numbers > 1000) to the SiriusXM driver (Or maybe there's already a way to do this that I just missed)? Right now I have a work around by playing it on a TV and joining rooms to the session, but that's not ideal. I'd rather just have a native way to do it in the Audio driver than having to use video as a bandaid.
×
×
  • Create New...