Jump to content
AT&T to end email-to-text ×

oh2bnMaine

Members
  • Posts

    101
  • Joined

  • Last visited

Profile Information

  • Location
    Florida & Maine

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

oh2bnMaine's Achievements

Member

Member (3/6)

16

Reputation

1

Community Answers

  1. Update: While I'm still not successful, I realized the .sh script on the web page did not have the call to run either of the procedures. I added a line to run the procedures to set up the boot nvme stuff and the program now runs. Now, I'm having the same problem I was having with the nvmecontrol devlist command, I think.
  2. I created the setup_nvme_boot.sh program and tried to run it. I do not get any indication that the program ran. The echo commands do not show up. No error messages. No indication whatsoeever. Normally, if I chmod a .sh file and then run it I would get something, right?
  3. I've let things run for awhile before coming back to this. After correcting the variable's INIT value, the issue has gone away. Thanks to everyone for your assistance!
  4. I purchased a Crucial PCIe Gen4 NVMe 2280 M.2 SSD and installed it in my eISY. I almost immediately ran into a problem, though. Can someone help me with this? I'm good for using unix, but I'm by no means an expert. Here's where I'm at... [admin@eisy /etc/zfs]$ sudo nvmecontrol devlist nvme0: CT1000P310SSD8 nvme0ns1 (953869MB) [admin@eisy /etc/zfs]$ sudo zpool create storage /dev/nvd0 cannot create 'storage': no such pool or dataset [admin@eisy /etc/zfs]$ Help?!
  5. Hmm. So, maybe I shouldn't be doing it this way regardless whether it is the issue or not? -- all the writing to EEprom memory? I never had issues with this program, which has been running for just over a year. Since I fixed the INIT value for the variable, my isuses have gone away. I'll leave it as is for another few cycles, though. That should confirm that the issue was a changed variable -- probably I fat fingered something.
  6. As a result of these two responses, I got to thinking about what my Programs do. The routine I run to change On Level via the scene uses variables to accomplish this. For some reason, the INIT level of the AM (Day) routine was 0. This doesn't explain why things are working intermittently, though. But it is a step forward. I changed the INIT & VALUE to 75% and I'll monitor the system today. Here's what I do in the program. This is the first program I wrote to control a scene, so I'm open to improvements! I wouldn't bet my life on this order, but I most likely added them to the scene in Admin Console and then recreated the scene at the switches when things still didn't work.
  7. I can control all three switches from UDI phone app. While controlling the switches, I can see that they are switching on to the correct brightness levels -- I have a routine that changes these from day to night. The switch that is wired to the light is the only one that is actually turning the lights on. When I have a minute, I'll look for a spare 2477D to change the switches one at a time to see what happens. I'll get the PLM information later this morning.
  8. Well!! It happened again yesterday evening! I Just found out have performed the Restore Devices function on all three switches. The first switch I did, the ISY Admin Console restarted itself and I had to re-log in. Further attempts did NOT restart the ISY console. Unfortunately, this did not fix the issue. Any other thoughts? I'll leave it as is for now to see if anybody can help me get to the bottom of this (since it seems like it will come back)
  9. I didn't think of using the Restore function until it was too late. That would have been a good test.
  10. First off, I fixed it, but I am still curious if somebody can explain what happened. I have recessed lights in the kitchen connected to a 2477D (Switch A). I have two other 2477Ds (Siwitch B, Switch C) that controlled the 'live' switch. This has been working for approximately 2 years now. This morning, my wife actuated one of the controller switches (not the one that is physically wired to the lights) and the scene seemed to break. The two controller switches stopped working as expected. Turn lights ON using Switch A Note that the LEDs on Switch B & Switch C did NOT change position (this used to work) Actuate Switch B (from OFF to ON) to try to get it in sync with the scene Lights turn OFF Switch A LEDs go from ON to OFF Switch B LEDs go from OFF to ON Switch C LEDs do not change I removed the three switches from my ISY and re-adding them. I recreated the scene in the admin console. I then created the scene at the switches. I'm not sure if I HAD to do both #5 & #6, but just doing #5 did not seem to fix the issue. I have ~40 scenes. This is the only one (that I have found) that broke. Any thoughts on what happened? Two months ago, I migrated from my ISY994 to an eISY. Other than that, I haven't made any changes that I would think could have impacted this aspect of the ISY. None of those changes were in the last few days and we've been using the kitchen lights every day.
  11. Thank you for asking that question!! I had only been trying the individual lights in the scene; not the scene itself. My problem went away after I removed and re-added all devices in the scene. Now the scene works fine again. I'll go through and do this to all ~40 scenes!! (I imagine some don't work. I am pretty sure I've seen at lesat one other scene work since migrating)
  12. I have upgraded from my ISY994 to an EISY. I think my problem is isolated to scenes. I see the scene in Alexa and Google Home, but the expected action doesn't materialize even though the smart device tells me it was successful. I have a scene called "Master Suite." I say, "Alexa, turn off the master suite." I get the confirmation sound from the Alexa that the action was understood but the lights to not change. I say, "Hey Google, turn off the master suite," I see it finds the object on my phone and tells me it successfully turns it off but the lights in the room do not change. I removed the "Master Suite" device from my Alexa. I then disabled the Alexa skill for the ISY and reenabled it. This forced Alexa to find the "Master Suite" as if it were new. The problem has persisted though. Alexa and Google both have no issues operating EISY Devices that are actual light switches. Any thoughts?
  13. I've tried using InPrivate and removing all extensions. I still see this message. Are there other suggestions I should be trying?
  14. Yes. 8-361. Sorry for the delay, I have been away from my computer for a couple of days. I will update to 5.3.4 regardless. Thanks for reminding me!
×
×
  • Create New...