Jump to content

AlexE

Members
  • Posts

    20
  • Joined

  • Last visited

Everything posted by AlexE

  1. Yes, this works. Writes the actual values into the spreadsheet. Thanks!
  2. <nodeInfo> <node flag="0" nodeDefId="ZY014_143"> <address>ZY014_143</address> <name>ZY 014 Energy Meter</name> <family>12</family> <parent type="3">36911</parent> <type>4.16.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY014_1</pnode> <rpnode>ZY014_1</rpnode> <sgid>143</sgid> <custom flags="128" val1="0"/> <devtype> <gen>4.16.1</gen> <mfg>634.257.13</mfg> <cat>143</cat> </devtype> </node> <properties> <property id="CC" value="0" formatted="0.000 Amps" uom="1" prec="3"/> <property id="CPW" value="0" formatted="0.000 Watts" uom="73" prec="3"/> <property id="CV" value="124871" formatted="124.871 Volts" uom="72" prec="3"/> <property id="TPW" value="4988" formatted="4.988 kWh" uom="33" prec="3"/> </properties> </nodeInfo> That's the output using the web browser That would mean ${sys.node.ZY014_143_33_3.tpw}, ${sys.node.ZY014_143_72_3.cv} should work? Still only writes node[ZY014_143_33_3] node[ZY014_143_72_3] into the csv file. Thanks again
  3. ok - bracket was wrong: ${sys.date},${sys.time},${sys.node.ZY014_143_33_3.ST} now it writes: node[ZY014_143_33_3]
  4. I got it to write a csv file but I am struggling with writing the actual value for the file for the power. so my custom notification reads: ${sys.date},${sys.time},$(sys.node.ZY014_143_33_3.ST} it outputs day and time correctly but the actual energy output just reads : "$(sys.node.ZY014_143_33_3.ST}" I guess I am missing somehting? Thanks
  5. This is exactly what I was looking for, Thanks. would be great if those charts could be put back to the wiki archives.
  6. I was wondering whether it is possible to write the query results from an esiy program to a csv file (or similar). I have several zooz plug with energy monitor and do not really need a sophisticated online solution, but a rather a simple data dump into a spreadsheet of some sorts. I was browsing the forum etc but could not really find an answer whether this is possible? Thanks for any help in advance
  7. not really - it's in a quite central open spot - I added the other devices from the same original location before moving and it worked. My guess it's that ZEN15.
  8. Thanks a lot - I moved the plug a little closed to the eisy (it was pretty close already anyway - just moved it 6ft) but that did the trick. Could have tried that earlier .... Thanks again!
  9. Both yes That's the output
  10. Yes I did - I am not sure whether Synchronize with interview actually does anything - is there supposed to be some progress feedback? Thanks for helping.
  11. Before upgrading to IoX 5.5.9 I successfully added two ZOOZ ZEN15 plugs with energy meter to my eisy. I was trying to add another one today and the Energy Meter is missing. I tried several times with the same result. I could add it to my polisy which does not have z-matter enabled and the energy meter shows up so I assume the device is ok. I was wondering whether I am the only one encountering this issue? Thanks
  12. I am running IoX v.5.5.2 with pg3 3.0.16 on my polisy and it works as is did before upgrading from IoX v.5.4.5. The upgrade was not necessarily intentionally just did a 'Upgrade Packages' apparently about the same time when it was posted. Not sure I would do it again after seeing how the eisy upgrade went (see below). pg3 seems to work as before. I received my eisy a few days back and this seems to be a very different story. Same versions, but pg3 does only connect intermittently (mostly not) - as you mentioned it looks like eisy PG3 is not ready. All the insteon connections together with the usb PLM work fine. I don't have any z-wave devices so I can't tell.
  13. AlexE

    pg3 missing directory

    http://<eisy.ip.ad.here>:3000 was what resulted in the described error. Uninstalling / Reinstalling pg3 via the terminal and a eisy restart fixed the access issues. I still have problems with the node servers, but it seems a lot of other users report similar issues, so being patient will probably solve a lot of issues over time. Thanks for checking -
  14. I have everything running on my eisy except pg3. When I go to the web interface I get the following error: ENOENT: no such file or directory, stat '/var/polyglot/node_modules/@universaldevices/pg3x/public/index.html' As far as I can tell pg3 is installed and running.
  15. Thanks that's what I thought. Had done all the java cache cleaning and also installed the launcher on a different PC. I would assume that this this is not only me since I just downloaded the launcher from the UD page.
  16. Not exactly the same problem but also IoX launcher related. Just got my eisy hooked it up and downloaded the latest launcher. If I request firmware update nothing is happening.
  17. Never mind found it sudo pkg update && sudo pkg upgradecat /usr/local/etc/udx.d/static/update13.sh | sudo bashsudo shutdown -r now
  18. I am stuck when upgrading my polisy to V13 [admin@polisy ~]$ sudo pkg update && sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ uname -a FreeBSD polisy 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 r369564 POLISY amd64 [admin@polisy ~]$ I am pretty sure I am missing something Thanks is advance
×
×
  • Create New...