-
Garage Door Mock Data.
Replace ipaddress with eisy.local or numerical IP Copy of node definitions http://ipaddress/rest/nodes Copy of node profiles http://ipaddres/rest/profiles?family=10&instance=BB (replace BB with the slot number e.g. 1 for slot 1, 11 for slot 11)
-
Bug?: i3 4 button KPL showing 1 too many nodes
Before attempting to debug any issues, if these were created prior to the lates update the scenes may have been created with the wrong mappings. Try write updates. I think this works but I only have 2 i3 Keypads, and pervious scenes were wiped during testing. So I am not 100% sure write updates works, it may required deleting and recreating the scene.
-
Garage Door Mock Data.
Perfect 2 things Two things: Copy of rest/nodes. Copy of rest/profiles?family=AA&instance=BB where AA is the family (1 for insteon, 10 for plugin) and BB is instance (1 for insteon, slot number for plugin).
-
Suggested UD Mobile Feature - Autobackup of ISY
Without raw creds it would need an oAuth or JWT implementation for refresh, via refresh token. Similar to how the mobile app works.
-
Garage Door Mock Data.
Perfect is ratgdo a plugin? If it is can you send the data requested in the first post?
-
Will eisy-ui Ever Reach Feature Parity?
Please search the forum, all of these things can be done.
-
Bug?: i3 4 button KPL showing 1 too many nodes
We would need to see the scene setup. The issue with the "old" method was button "A" and load "1" where always grouped together. While this worked if button "A" was the linked to load "1" in "Flags" it broke if the load was changed to another button. It could have been that the links were incorrect, due to the "bug" in before the fix which was causing issues. In any case it sounds like it is working now?
-
Garage Door Mock Data.
Looking for either the Insteon sensor + iolink (I think) combo or from a Garage door plugin. In short, I want data to mock this device to show an example of a custom tile which will show door open/close state and control. Similar to the door lock which shows lock state and battery level.
-
UD Mobile - Migrate from PG3 Concerns
Staging fixes the known profile issues.
-
Garage Door Mock Data.
Hi All, I'm looking form mock data for a garage door sensor and trigger and/or data from a plugin that controls a garage door. The goal is is UI testing. Need a copy of rest/nodes. A copy of rest/profiles?family=AA&instance=BB where AA is the family (1 for insteon, 10 for plugin) and BB is instance (1 for insteon, slot number for plugin). Please send in private message along with the node names and/or addresses and context of how it is working in your setup. I will post here if no longer needed.
-
Javi started following Garage Door Mock Data.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Yes staging IoX must be 6.1.2_14 or greater
-
eisy-ui 1.3.4 - Integrated plugins (Beta)
P.S. This is not intended to replace formatted value, it was implemented for strings to enhance the trigger that are single use. For example the last image from a doorbell camera, a detailed error message with a error property, a url for stream or images.
-
Favorite update in real time
Usually related to Android Killing the UDM service before UDM had time to close itself.
-
eisy-ui 1.3.4 - Integrated plugins (Beta)
Yes, Thanks this confirms what i expected, the text is not being sent to eisy-ui. I will need to investigate. So for now formatted text relies on the use of NLS (XML) or editor.names (JSON) from profiles Property XML (node status query response): <property id="ST" value="42" formatted="42 %" uom="51"> <text>Eco Mode</text> </property> Subscription event stream: <Event ...> <control>ST</control><action uom='51' prec='0'>42</action><node>addr</node> <eventInfo>...</eventInfo> <fmtAct>42 %</fmtAct> <text>Eco Mode</text> </Event> Created issue: '''eisy-ui missing "text" param/key in node update events.''' Id: /eisy-ui/issues/152. Currently at least 1-2 weeks out.
-
Zwave LR - pin code
Not Possible, LR requires the QR Code. The pin will get you secure paring only. There may be issues in some browsers, chrome and safari should work, Firefox has known issues. Also taking a clear picture of the QR then uploading instead of scan may work better than some PC cameras.