Announcement

Collapse
No announcement yet.

HS4 Release Announcements 4.2.5.0 is available!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ARuser
    replied
    I'm still having this issue, where newly created events to control Ecobee don't do anything.


    Originally posted by ARuser View Post

    I tried editing an event, and the temperature selection becomes the "New" style with the F, instead of the $%0$

    Out of curiosity, I explored the events.json, and manually changed "72.0 °F" to the old style, which is "72$%0$". When I do that and run the event, the temperature change goes through.

    Here's the info from the events file for the old way, as well as the log output when it's run (the temperatue values may be different, since I was tinkering around a bit):

    Code:
    Scheduler","dvRef":268,"LegacyCheck":-5.0,"ControlLabel":"71$%0$","ControlValue":-10000.0}},"delay":"00:00:15","Misc":64,"evRef":1619,"Action_ Order":6},"K7":{"$type":"Scheduler.Classes.EvACT_DEVICE, Scheduler","devices":{"K292":{"$type":"Scheduler.Classes.EvA CT_DEVICE+clsDevAction, Scheduler","dvRef":292,"LegacyCheck":-5.0,"ControlLabel":"67$%0$","ControlValue":-10000.0}},"delay":"00:00:40","Misc":64,"evRef":1619,"Action_ Order":7}}},"Version":1.2,"evRef":1619,"Name":"Oculus All Off AM","EvGroup":{"GlobalActions":{"mvarActions":{}},"GlobalCon ditions":{"TrigGroups":{}},"Version":1.2,"Group":"Oculus","R ef":787336913},"PlugExtraData":{}},{"mvarGroupRef":150646572 ,"Last_Trigger_Time":"2020-06-02T01:54:58.1042294-05:00","Triggers":{"TrigGroups":{"K0":{"$type":"System.Colle ctions.Generic.List`1[[Scheduler.Classes.EvTrig_BASE, Scheduler]], mscorlib","$values":[{"$type":"Scheduler.Classes.EvTrig_MANUAL,




    And here is the code and log data with the new method, which doesn't change the temperature

    Code:
    Scheduler","dvRef":268,"LegacyCheck":-5.0,"ControlLabel":"72.0 °F","ControlValue":-10000.0}},"delay":"00:00:00","Misc":96,"evRef":3794},"K1":{" $type":"Scheduler.Classes.EvACT_DEVICE, Scheduler","devices":{"K292":{"$type":"Scheduler.Classes.EvA CT_DEVICE+clsDevAction, Scheduler","dvRef":292,"LegacyCheck":-5.0,"ControlLabel":"72.0 °F","ControlValue":-10000.0}},"delay":"00:00:05","Misc":64,"evRef":3794,"Action_ Order":1},"K2":{"$type":"Scheduler.Classes.EvACT_DEVICE, Scheduler","devices":{"K1117":{"$type":"Scheduler.Classes.Ev ACT_DEVICE+clsDevAction, Scheduler","dvRef":1117,"LegacyCheck":-5.0,"ControlLabel":"Off","ControlValue":-10000.0}},"delay":"00:00:11","Misc":64,"evRef":3794,"Action_ Order":2}}},"Version":1.2,"evRef":3794,"Name":"Weekday 715am 72 both, recirc off","EvGroup":{"GlobalActions":{"mvarActions":{}},"GlobalCo nditions":{"TrigGroups":{}},"Version":1.2,"Group":"Temperatu re","Ref":1564955774},"PlugExtraData":{}},{"mvarGroupRef":19 69929945,"Last_Trigger_Time":"2021-09-15T15:2

    Leave a comment:


  • racerfern
    replied
    Since upgrading to 4.2.5 from 4.1.18, I get two errors that are related to the front door. One is the z-wave action, the other one I believe is the front door being unlocked.

    Not sure what I can do about them. I do know that the front door bell used to ring the moment the contacts went open, now it can take 10 seconds (at times) after opening the door.

    The lock is a Yale YRD226 and works just fine.

    Below are the two errors and the event. Thoughts please.

    ---Error--- from the chime being changed to a ding ding when the front door opens. This has worked for over four years until now.
    10/28/2021 12:57:24 Legacy-Plugin Z-Wave Warning A Z-Wave action in the event Door Actions Front Door Opens returned an incomplete (failed) result.
    10/28/2021 12:57:24 Legacy-Plugin Z-Wave Error Event Action Set Configuration Parameter failed in Event Door Actions Front Door Opens

    ---Error--- from door being unlocked or locked. This has worked for over two months until recently.
    10/28/2021 12:57:19
    Legacy-Plugin Z-Wave Warning >>>>>>>>>>> Got NAK or CAN <<<<<<<<<<<<
    10/28/2021 12:57:19 Legacy-Plugin Z-Wave Warning >>>>>>>>>>> Got NAK or CAN <<<<<<<<<<<<

    Click image for larger version

Name:	Screen Shot 10-28-21 at 01.41 PM.PNG
Views:	269
Size:	44.3 KB
ID:	1504969

    Leave a comment:


  • Walnut2000
    replied
    That's sorted it for me, thank you.

    Leave a comment:


  • w.vuyk
    replied
    I have corrected the slowness of the JowiHue plugin causing the slowness on the HS events page in the latest version of the plugin, 4.0.5.5.

    Leave a comment:


  • nunoary
    replied
    Originally posted by w.vuyk View Post
    Ok thanks for confirming. I am now working on a work around so it is no longer slowing down the buildup of the page.
    I also confirm that I used the plugin with HS3. I appreciate your trying to work out a solution but it would also be nice if rjh could say something about this bug in HS4.

    Leave a comment:


  • w.vuyk
    replied
    Ok thanks for confirming. I am now working on a work around so it is no longer slowing down the buildup of the page.

    Leave a comment:


  • Walnut2000
    replied
    Originally posted by w.vuyk View Post
    I think most of you having this performance issue with the JowiHue plugin, have used HS3 before with JowiHue?
    My experience supports this view, Wim.

    I was previously using Jowihue with HS3 before upgrading to HS4, and I'm now having this performance issue where the Events page is very slow to open.

    Leave a comment:


  • w.vuyk
    replied
    I think most of you having this performance issue with the JowiHue plugin, have used HS3 before with JowiHue?

    I already pointed to this potential performance issue in the pluginsdk github almost two years ago: https://github.com/HomeSeer/Plugin-SDK/issues/68. Once that issue is resolved, performance of (HS3) events checking will resolve.
    So far HST does not show responses in that thread. Although some developers heard that something might change after HS 4.2 would be relased. Is that still planned rjh ?


    Wim

    Leave a comment:


  • nunoary
    replied
    Originally posted by Jez View Post

    Yes, thats it. Once I've disabled the JowiHue plugin the events screen runs perfectly.
    Its obviously not a permanent fix but proves where the problem is.
    Yes...maybe w.vuyk can help.

    I also noticed that by disabling the JowiHue plugin, which solves the delay when opening the events page, but it seems that sometimes the plugin management page takes too long...nothing too worrying but that should be resolved. One of the main advantages I already see in HS4 compared to HS3 is the speed in opening pages but these situations don't help.

    Leave a comment:


  • Jez
    replied
    Originally posted by nunoary View Post

    Do you have the JowiHue plugin installed? If so, can you disable it for a moment and check if the events page opens faster?
    Yes, thats it. Once I've disabled the JowiHue plugin the events screen runs perfectly.
    Its obviously not a permanent fix but proves where the problem is.

    Leave a comment:


  • nunoary
    replied
    Originally posted by Jez View Post

    I've also noticed that the events screen is very slow and I also assume its because of the (very useful) broken event detection function. Perhaps it would be better if this was run on demand rather than at every refresh?
    Do you have the JowiHue plugin installed? If so, can you disable it for a moment and check if the events page opens faster?

    Leave a comment:


  • Jez
    replied
    Originally posted by nunoary View Post
    Hi rjh

    I don't know if it has already been reported but I notice that the events page takes some time to open. And if it's out of the local network with MyHomeseer it gives an error and it can't open.

    Browser: Chrome

    Version=HS4 Pro Edition 4.2.5.0 (Windows)
    Antivirus=Windows Defender
    OS=Microsoft Windows 10 Pro - Work Station
    OS Version=10.0.19043
    Uptime=1 Day 13 Hours 7 Minutes 21 Seconds
    Device Count=1377
    Event Count=444
    Processor:=Intel64 Family 6 Model 61 Stepping 4 at 2.51 GHz
    Modules/Threads=133 Modules, 168 Threads
    Available Threads=1023
    System Load=163 Processes, 33% Load
    Free/Total Memory=5.42 GBytes / 7.93 GBytes (68% free)
    Free/Total Virtual Memory=6.55 GBytes / 9.18 GBytes (71% free)
    HomeSeer Memory Used=144 Mbytes
    Plugin Memory Used=16 EXE Plug-Ins using 178 Mbytes



    Edit: I upgraded from version 4.1.16 to 4.2.5.0 maybe it is related to the new "Broken" event detection function.
    I've also noticed that the events screen is very slow and I also assume its because of the (very useful) broken event detection function. Perhaps it would be better if this was run on demand rather than at every refresh?

    Leave a comment:


  • WWWV
    replied
    I am having the same issue as Jazz... Running Zee S2 on Linux and was able to upgrade up to, and including, 4.1.17.0 and have been unable to upgrade through the 'Install Update' button on the 'Setup' tab ever since. System doesn't crash rather, goes through the update messaging & reboots as it used to but when I return to the 'Setup' tab, 'Current Version' reflects 4.1.17.0 and 'Latest Release' displays 4.2.5.0 with the 'Install Update' button next to it, ready to go.
    I have too have a 32GB card in the Zee S2 so I don't think it is a space issue.

    UPDATE:
    I was never able to get my system updated to 4.2.5.0 through the "Install Update" button on the setup tab however, was able to get it done directly in Linux via PuTTY. After not giving-up and searching all corners, I found the "Alternate Method" in the HS4 docs - link below.

    Interestingly, the update also fixed the issue I was having with Alexa & ZWave in that "On" & "Off" commands wouldn't work! In order to control my ZWave lights with dimmer switches, I had to command %'s whereas straight-up switches/plugs would not respond.

    Alternate Method:
    Connect via SSH to your system.
    1. Login with your homeseer system user.
    2. Navigate to the HomeSeer directory
      cd /usr/local/HomeSeer
    3. Run the following script. Replace # with version number you wish to update to. (IE. 4_1_0_10)
      sudo sh updatehs.sh #_#_#_#
    4. Your system will reboot once complete.

    Source: https://docs.homeseer.com/display/HS4/Updating+HS4

    Leave a comment:


  • John245
    replied
    Originally posted by scorp508 View Post

    Interesting. I'm on HS4 Pro 4.5 (and betas leading up to it). My EasyTrigger is at 3.0.0.72 with no notification of update available, but I see you're on .73 and it says an update is available.
    Interesting. Why it is working for me and not for some other people.

    ---
    John

    Leave a comment:


  • Wade
    replied
    Originally posted by scorp508 View Post

    Can you remind me what that URL is? I didn't realize I had outdated plugins until you brought this up. Or do you mean the legacy section of the plugin shop?
    http://<HSIPaddress>/_interfaces.html

    Leave a comment:

Working...
X