Jump to content

rlebel

Members
  • Posts

    182
  • Joined

  • Last visited

Recent Profile Visitors

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

rlebel's Achievements

Experienced

Experienced (4/6)

7

Reputation

1

Community Answers

  1. I updated to 3.2.27. This morning I got the same problem again.
  2. At random times I get a sequence of fail/disconnect/connect notifications. Happens roughly once a day. It has been happening for a long time, since it reconnects immediately it is just an annoyance not an operational issue.
  3. _5 and my DST checkbox is still set and grayed out. Sunrise/set displayed correctly.
  4. It would be nice if the About box gave the _x suffix, mine just says 5.0.7.
  5. Today mine are too! They weren't yesterday. But the greyed out DST check is still incorrectly checked.
  6. I think that rebooting (in my case after doing an update packages) has fixed this for most people. The display problem of sunrise/sunset is the remaining bug but that doesn't impact proper program operation since it is only the UI.
  7. I did an update packages and reboot and my programs seem to have been appropriately reenabled. However, sunrise and sunset and the DST checkbox are still wrong.
  8. All of my programs disabled also - and by looking at when variables had last been updated I see it happened exactly at the DST change. I don't have disabled programs labeled in any special way so enabling is going to be a real PITA. I also see that DST is still checked on the configuration screen and sunrise and sunset are an hour earlier than they should be!!!
  9. Thanks. I suspect that my problem was that I forgot to buy a perpetual license!! Purchased now, will see if I have a future problem!
  10. Recently I found that my EISY was not getting any updates from my wireless tags. I checked that the tag manager and polisy were running then I restarted the node server manually and all was well. My question is can I automate this? I could set up a program that would detect if there had been no updates for a while but I don't see that I have the ability to restart the node server. The device shows the ability to reboot the tag manager but not the node server. Ideas? Thanks
  11. I too had a strange result disabling WiFi, your hint saved me a lot of trouble! The eisy is now hard wired in the equipment closet. Enjoy the lake house, I seem to have everything working now.
  12. The loop seems to work, so far I am not using any PIR so a one minute update of sensors is fine. If I went to a hardwire link for my eisy I guess it would work. I have to disable the wifi? When might you get around to fixing this?
  13. Yeah looks like you are right about that. I guess I could set up a program to repeatedly send queries.
  14. So I went to polyglot 2, got a new oauth2_code then cut and pasted that into PG3x and at first no luck but then suddenly I did a discover and all the nodes popped up! Thanks all!
×
×
  • Create New...