Jump to content

ISY4Me

Members
  • Posts

    129
  • Joined

  • Last visited

Community Answers

  1. ISY4Me's post in Upgrading the eisy... didn't hear 4 beeps + 1. was marked as the answer   
    I have read (somewhere) that the EISY does not have a speaker, so no sounds. 
    if you have a hdmi monitor and keyboard on the EISY you can monitor the update by viewing the log after you login  
    sudo tail -f /var/udx/logs/log If you don’t have a monitor and you are comfortable with it, you can ssh into the EISY and then view the log. 
    When updating is complete the last line in the log will actual state that the update is complete. 
    Another option is… if the update is still in progress, you will see a warning when you start the AC for the EISY, but I have never confirmed that the update is complete if the message is not visible. 
  2. ISY4Me's post in Mounting ZMatter Board into the Enclosure was marked as the answer   
    I received a reply from @Michel Kohanim this afternoon regarding my ticket on this issue.  Here is a cut/paste of his response... shared with his permission.
    There were no suggestions as to how to snap the excess off the board, but at least we are aware of the guideline.
    Michel Kohanim wrote:
    2023/01/01 17:28
    Hi Jim,
    Yes, so very sorry. You need to snap it in the middle.
    JWeaver01 wrote
    2022/12/31 08:05:27
    With no guidelines or instructions included with the Enclusure I was trying to mount the “as shipped” ZMatter board into the Enclusure intact getting interference with the posts of the antenna connector.  Yes, there was extra depth to the cable that I originally pointed out, which made that interaction worst, but that may be a non-issue. 
    But after looking closer at things this morning and seeing that one image of a mounted board (see attached) I am beginning to think that the full ZMatter board was never designed to mount in the Enclosure.  
    Is snapping (or cutting) off the top half of the ZMatter board the sanctioned method approved by UD?  Recommendations on how to do that without damaging the board? 
  3. ISY4Me's post in Changing Ecobee climate type with indefinite hold fails was marked as the answer   
    I ran multiple tests this morning and finally was able to get a persistent change.  I think @Jimbo.Automatesis correct, in that something was not under control.  So, this is the criteria that finally appears to work.
    I set the Ecobee app "Device Settings" for "Hold Duration" to the "Until I change it" selection In IoP, I programmatically set the Climate Type to my "Away" test comfort setting, but I had to set the "Hold Type" to "Indefinite Hold" to keep the changed value for climate. In IoP,  programmatically issue a "Wait" command for two minutes to give time for the last command to propagate to the thermostat settings.  Changing the Climate Type will change the Schedule Mode to "Hold Next", so that setting needs to be stable before forcing it in the next step.  Perhaps it can be shorter that a 2 minute delay... needs further testing. In IoP, programmatically issue a "Schedule Mode" change to "Indefinite Hold" In the testing so far, the Temperature, Climate and Schedule Mode are all staying as set in the experiment.  They did not change when the Ecobee when through a Scheduled Comfort Setting change.  I then manually changed the schedule on the Ecobee App to go back to my standard daytime schedule and again, the Temperature, Climate and Schedule Mode remained the same as they were for the Away Test experiment.
    Reverting back to standard operation is as simple as issuing an IoP command to change "Schedule Mode" back to "Running" and everything goes back to the standard schedule.
    The standard Ecobee Vacation Mode is a very good tool, but I am optimistic that being able to programmatically control things will give me other options where they are needed.
×
×
  • Create New...