-
ST-NuHeat Node Server broke after reboot
Can you retrieve the profile files again?
-
upgrade fails in eisy ui
I saw there just was a new release of the UI - maybe try that before anything else I would try to delete and reinstall - I believe they are really the same
-
upgrade fails in eisy ui
There are no errors in the Yolink log - Maybe try to reboot the system or reinstall the nodes - there are other nodes with errors as well
-
upgrade fails in eisy ui
can you send me a log and I can take a look
-
-
Compare last device update to variable timestamp
Yes - I use something similar Jari has promised to fix this in a future release of eISY-UI (simply dropping the non-numeric type)
-
Compare last device update to variable timestamp
It seems there is a bug in the eisy-ui interface - I have specified time with 2 possible value types - 1 being the actual time (unix time) and 2 if there is no time a text string showing that (indx, uom25) - This also shown when you pick the variable - it shows index, unixtime - I guess it picks the index (0 or 99) - not the unix time - although it programmed to be unixtime when the value is updated I can remove the index, but in my mind it is a bug in the system - Note, if you use the AC, you can pick unix time and it works there - this is why I have not had issues so far
-
Two button FOB issues
Let me know when you think it works and I can do a full release
-
Two button FOB issues
The original issue was related to smartRemoter devices, so I believe it is covered - I do not have all permutations to test, and each behave slightly different but I do believe the ghost triggering so common - so it should be addressed already
-
Two button FOB issues
Code was updated, but not activated for the 5708 switch - sorry I'll build a version 1.8.61 in the non-production store to make sure it works for you - can you test before I release
-
Two button FOB issues
It should be the same code, but I'll confirm If you can enable debug and capture a ghost event (along with rough time) and pm me log, I can see if I can find the issue
-
New Version
No, first time after the new node is installed, it is required - after that it should not be needed unless down for a long time. Note, I just fixed one more bug, so please reinstall
-
New Version
I have noticed that once in a while a reboot of the system or a delete and reinstall of the node is necesary for up to fully update
-
New version 01.21
Released versio 0.1.21 Fixes bugs in eisy-ui interfsace Ensures time only updates if new data is received Moved to dynamoc profiles
-
New Version
Version 0.6.29 is released It now stored tokens so a reboot should not require F2A code Updated to latest API Time now only updates if camera provides data Swapped ST and GV0 or GV1 so main parameter shows Armed state Few minor bug fixes to show nicely in eisy-ui among other things
-
ST-NuHeat Node Server broke after reboot
Just released version 2.2.20 in productions store - Hybrid mode supporting older and newer system (as much as possible) Few bug fixes related to time - now it does not update if data is not updated - makes it useful for testing if node is running or not (test against unixtime)
Panda88
Members
-
Joined
-
Last visited