tazman

@gzahar mapped the original ISY codes and created files for it you should be able to download and use

I know it did at one time. I don't know enough about the errors but I know some plugins require it and it won't hurt anything to give it a try.

Here you can see the commands show up in both PG3 and the AC.

Did you install the Developer Packege from the AC?

It has been a long time since I set this up but my first thought on what you said is I don't think the harmony remote sends IR I think it sends RF commands to the hub and the hub sends the IR commands. When button presses are added they show up in the AC also. From what I remember the codes you are going to use need to be loaded to the Flirc from a computer to be used in ISY.

It has not been possible for me and I have spent some time watching videos and messing about in Visual Studio.

Great post @Javivery informative thanks for sharing!

Isy portal is needed if you're running the occupany items in the portal.

Try shuting down the eisy with 6 clicks of the multifunction button and unplugging the unit when the light turns red wait 10 seconds and give it a while to start then try accessing it. Sometimes eisy gets hung up and needs a complete power down to return everything to it's proper state.

I believe they can be deleted in ISY where you took this screen shot from. Click on each individual node server and I think there is a delete button in there.

My biggest cost savings is to use node servers / plugins with programs I wrote to charge an electric vehicle using excess solar and not use electric from the grid.

Have you checked the link tables in the motion sensors? Maybe have the event viewer open on level 3 while you trigger the motion sensors?

Have you shutdown and unplugged your "ISY" device? That seems to be a step that can cure some "issues"

This happened to me a couple of times in the past and the only way I know to fix it was to submit a ticket with UDI and they would do something on their end to correct the issue.

As far as I know you have to use a control device/program/variable from Eisy exposed to Alexa with a Routine in Alexa or multiple Routines depending on how much control you want over the device in Alexa. The Virtual node server is the actual name of it. https://github.com/UniversalDevicesInc-PG3/Virtual/blob/master/README.md

You can have some control of Allexa devices from Eisy. You can expose a variable to Alexa as a motion sensor and there is the Virtual node server that you can create virtual switches to use in Alexa. You can also create Routine in Alexa where anything exposed to Alexa from Eisy can control Alexa devices.

No problem I'm thrilled with my setup, the way it looks and performs! I appreciate the time and effort you have given me.

Also pi@raspberrypi:~/hpserver $ sqlite3 SQLite version 3.34.1 2021-01-20 14:10:07 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite>

@kewashi I think the first command removes node and after running the two commands neither housepanel new or old would work saying it could not find node command so I reinstalled node and ran the first command again to capture what it would say but not complete it. pi@raspberrypi:~ $ sudo apt install libnode72 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: gyp libjs-highlight.js libjs-inherits libjs-is-typedarray libjs-psl libjs-typedarray-to-buffer libssl-dev libuv1-dev node-chownr node-color-name node-err-code node-extsprintf node-fast-deep-equal node-indent-string node-ini node-is-typedarray node-json-parse-better-errors node-json-schema node-json-schema-traverse node-qs node-resolve-from node-through node-typedarray-to-buffer node-universalify node-uuid Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: nodejs The following NEW packages will be installed: libnode72 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 7,261 kB of archives. After this operation, 153 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. I then tried running just the second command to see if it would work and my older housepanel works again but the new version still does not and the log is the same as before.

@kewashi thank you results below pi@raspberrypi:~ $ node -v v20.8.1 Created node.js file and ran i@raspberrypi:~/HousePanel $ node node.js >& node.log & [5] 2259 [4] Exit 1 node hpserver.js &> hperver.log node.log had This is a test i@raspberrypi:~/HousePanel $ node hpserver.js >& hperver.log & [10] 6720 [9] Done node node.js &> node.log pi@raspberrypi:~/HousePanel $ node hpserver.js >& hperver.log & [11] 6762 [10] Exit 1 node hpserver.js &> hperver.log I'm not quite sure why I see a different response when ran a second time. hperver.log didn't notice your typo until after running this doing copy paste to try and not make mistakes node:internal/modules/cjs/loader:1327 return process.dlopen(module, path.toNamespacedPath(filename)); ^ Error: libnode.so.72: cannot open shared object file: No such file or directory at Module._extensions..node (node:internal/modules/cjs/loader:1327:18) at Module.load (node:internal/modules/cjs/loader:1091:32) at Module._load (node:internal/modules/cjs/loader:938:12) at Module.require (node:internal/modules/cjs/loader:1115:19) at require (node:internal/modules/helpers:130:18) at Object.<anonymous> (/home/pi/HousePanel/node_modules/sqlite3/lib/sqlite3-binding.js:4:17) at Module._compile (node:internal/modules/cjs/loader:1241:14) at Module._extensions..js (node:internal/modules/cjs/loader:1295:10) at Module.load (node:internal/modules/cjs/loader:1091:32) at Module._load (node:internal/modules/cjs/loader:938:12) { code: 'ERR_DLOPEN_FAILED' } Node.js v20.8.1

I'm running on a Pi4. When I saw the error I went to your web site and saw it required SQL so I installed MySQL. I just installed SQlite3 but I get the same error even after running the install aqain. I don't know where the node:internal/modules/cjs/loader stuff is located but I will attach the sqlite3-binding file I found to see if it helps. sqlite3-binding.js

Yes and it finished with some minor warnings so I think the install was complete. I will follow the directories it list to see if I can figure anything out. Thanks for all of your help!

@kewashi I think I got NPM figured out and it looked like the install worked. I assume the new is started the same as the old and below is what I get in the log file when I try to start it. node:internal/modules/cjs/loader:1327 return process.dlopen(module, path.toNamespacedPath(filename)); ^ Error: libnode.so.72: cannot open shared object file: No such file or directory at Module._extensions..node (node:internal/modules/cjs/loader:1327:18) at Module.load (node:internal/modules/cjs/loader:1091:32) at Module._load (node:internal/modules/cjs/loader:938:12) at Module.require (node:internal/modules/cjs/loader:1115:19) at require (node:internal/modules/helpers:130:18) at Object.<anonymous> (/home/pi/HousePanel/node_modules/sqlite3/lib/sqlite3-binding.js:4:17) at Module._compile (node:internal/modules/cjs/loader:1241:14) at Module._extensions..js (node:internal/modules/cjs/loader:1295:10) at Module.load (node:internal/modules/cjs/loader:1091:32) at Module._load (node:internal/modules/cjs/loader:938:12) { code: 'ERR_DLOPEN_FAILED' } Node.js v20.8.1

Thanks @kewashi it looks like the refresh was taken care of with the Slow Timer I'm still on V2.418 I tried updating to your newest but I could not get the install to finish because I'm on an older version of NPM and I was unable to get that to update. All the size changes in housepanel seem to affect the whole tile and not the image. When I view the frame source there seems to be some icon sizes coded in but when streaming directly from the Powerwall the image is bigger but the window is still small. <!DOCTYPE html> <html lang="en"><head><title>Tesla Energy - Setup</title><link href="favicon-32x32.png" rel="icon" sizes="32x32" type="image/png"/><link href="favicon-16x16.png" rel="icon" sizes="16x16" type="image/png"/><meta charset="utf-8"/><meta content="width=device-width,initial-scale=1,minimum-scale=1,maximum-scale=1,user-scalable=no" name="viewport"/><script>window.__INITIAL_STATE__={"configuration":{"isNew":false,"version":"23.28.2","hash":"EDITED","deviceType":"teg","isSolarPowerwall":true,"bootstrapped":true},"sitemaster":{"running":true,"connectedToTesla":true},"system":{"isFirmwareUpdating":false,"Version":""},"authentication":{"loginType":"customer","selectedLoginType":"customer","username":"EDITED","lastLoginAt":1697306954000,"toggle_auth_supported":true}} </script><link href="/app.17c71172308436a079d1.css" rel="stylesheet"/></head><body><div id="root" style="height:100%"></div><script src="/vendor.17c71172308436a079d1.js" type="text/javascript"></script><script src="/app.17c71172308436a079d1.js" type="text/javascript"></script><script src="clear.js" type="text/javascript"></script></body></html>

I use the regular Ocupancy in the portal so I don't know if this applies but did you setup the configuration in the portal and upload the node definitions? I know when that needed to be done for me it would show the light bulb and I have had updates that required me to upload the node definitions again.