Javi
Employees
-
Joined
-
Last visited
-
If using beta repo for upgrades I would first verify the issue, is the status slow to update or is the program scene slow to execute. Open the event viewer on you phone before you walk into a room if the status change immediately and there is a delay then investigate that path. If status does not update immediately then investigate that path. For the latter, try removing the devices and specify long range (only available in beta) during inclusion. An alternative, if both devices support local linking add both as mesh in a scene (although this may cause other issues depending on your setup).
-
Programs are re-evaluating very frequency. Not an issue but is the cause. The programs list is scheduled for virtualization which will correct, but not sure on the time frame. All improvements to original grids/lists are deferred until virtualization is complete. This is also needed for mobile implementation so is high on the list.
-
It will not trigger inside the folder. What I reference is in a program an if condition can be the status if another program (e.g. the folder), in this case it's not the folder's conditions triggering the program it is the folders's status triggering the program.
-
#1 No. A folder status must be true for automatic condition (IF) evaluation of children. It does not trigger evaluation, this still requires and event/status-change/etc. You could have a sibling program (to the folder) run a programs (IF) condition when the folder becomes true. This may even work in the program itself. Be aware that if the programs condition condition is an event, it will fail (IF), as the event is not true (is not happening). If the condition is a status and is true it will run.
-
Perfect, I added an issue for investigation. ID: /udi/issues/21 We have a backlog currently due to eisy-ui roadmap, but have replicated the issue.
-
Ok so is the issue is the selected state does not persist after reboot?
-
I don't follow, maybe attach an image of the scene or program being used. Batter devices need to be awake to write, so writing is not something that should be done programmatically in most cases.
-
For insteon there is not direct control of a button other than the load button. To control buttons they must be in a scene, so create a tile for the scene that has the C button.
-
See https://forum.universal-devices.com/topic/47131-is-network-resources-still-supported/#comment-407536
-
No changes, it is still supported. View/Edit exists in eisy-ui beta. However there is a UI bug that has issues with escaped chars, better to use admin console to edit until fixed. https://forum.universal-devices.com/topic/47042-eisy-ui-is-getting-there-heres-where-we-stand/
-
-
-
-
Thanks @Techman and @DNewkirk , I have repliacted added issue ID: /eisy-ui/issues/71 For the other Items @IndyMike is correct. The only values reported are in the property boxes at the top. Anything in a command is just default, although sometimes defaults are linked to a property value (init). This is one of the reason in 6.1.1 ( and in UD Mobile) the commands are grouped together without displaying a default until issuing a command. This prevents confusion with current state.
-
Can you please attach a screen shot showing in AC and missing from eisy-ui. Then right click the node in the list > Configuration > NodeInfo (requires eisy-ui beta), similar in Admin Console.
