tazman

I did not know where to post this since there is no TeslaEV topic in the PG3 Node Servers area. I purchased and installed the TeslaEV node server written by @Panda88but I always seem to have trouble setting these up as it is not intuitive to me what information to put in. I try to put the code that the authenticator app creates and restart the node server but it seems like it takes longer then the allowed 30 seconds for the node server to restart. How can this work without my user email? Am I using the correct code or am I supposed to use the backup passcodes I got from the Tesla site? Any guidance would be greatly appreciated! Tom

@bpwwer Thank you the current KWH seems to be working for me now but the KWH today is showing what my Vue car charger used. It is also showing as connected now.

@bpwwer I installed the node server and made sure Poisy was up to date but I have a "1" for online, Kilowatt Hours keeps flashing between 0 and a number and Kilowatt Hours Today is at 0. VUE_5-10-2022_65900_PM.zip

Yes you will need one for each location. Yes and it can be tight fitting them both in the USB ports because they are close together. Some use extension cables or a USB hub.

Someone recommended MacroDroid to me a while ago and I have been using it without issues.

@Javiyou are correct going back to the original version fixed it Thank You.

@JaviI hate to do this but it looks like IOP 5.4 made your fix stop working again! Any idea what changed?

@macjeffto start over with isy you want to sudo pkg remove isy then sudo pkg install isy then sudo service isy restart the only thing is for me every time I did it the portal would disappear but when I restored from a backup it would come back. Good luck! Tom

You were right I did have the tag manager on a different part part of the network from Polisy. I did not think of that since it was able to grab the information with a query. Thank you for the help and the hard work you put in to bring us these great programs!

I moved from the PG2 to PG3 version and in both versions I have to query the tag to get it to update. I will attach my log file to see if it helps to figure out what is happening. WirelessTag_2-4-2022_70950_PM.txt

@Javi Your the man THANK YOU!! I appreciate the time you put in to help me. Just so others know if they come looking "wsclient.connect(wshost, null, origin, header); " was what made it work for me. I'm not back to where I was with houspanel I only have 2 Items working but the fact that they update makes me think I can get back to where I was before.

@Javi I'm not sure what you mean with the connect function but I don't see anything in the file I cut the information from and posted above. I'm going to attach 2 files that seem like they could be relevant and if they are not it I guess I will just go back to giving up. websocket.js WebSocketConnection.js

@JaviBelow is the main area that looks to me it defines the websocket. Would you be able to tell me what to change to make it work? // make websocket connection to any ISY hub // unlike ST and HE below, communication from ISY happens over a real webSocket var wshost; for (var h in GLB.options.config["hubs"]) { var hub = GLB.options.config["hubs"][h]; wshost = false; if ( hub["hubType"]==="ISY" && hub["hubEndpt"] && hub["hubAccess"] ) { var hubhost = hub["hubEndpt"]; if ( hubhost.startsWith("https://") ) { wshost = "wss://" + hubhost.substr(8); } else if ( hubhost.startsWith("http://") ) { wshost = "ws://" + hubhost.substr(7); } } // set up socket for ISY hub if one is there if ( wshost ) { var wsclient = new webSocketClient(); var buff = Buffer.from(hub["hubAccess"]); var base64 = buff.toString('base64'); var origin = "com.universal-devices.websockets.isy"; var header = {"Authorization": "Basic " + base64, "Sec-WebSocket-Protocol": "ISYSUB", "Sec-WebSocket-Version": "13", "Origin": "com.universal-devices.websockets.isy"}; wshost = wshost + "/subscribe"; wsclient.on("connectFailed", function(err) { console.log( (ddbg()), "Connection failure to ISY socket: ", err.toString(), " wshost: ", wshost, " header: ", header); }); wsclient.on("connect", function(connection) { console.log( (ddbg()), "Success connecting to ISY socket. Listening for messages..."); // handle incoming state messages from ISY // this will be ignored if the node isn't in our list connection.on("message", function(msg) { if ( msg.type==="utf8" ) { processIsyMessage(msg.utf8Data); } }); connection.on("error", function(err) { console.log( (ddbg()), "Connection error to ISY socket: ", err.toString()); }); connection.on("close", function() { console.log( (ddbg()), "Connection closed to ISY socket"); }); }); wsclient.connect(wshost, "ISYSUB", origin, header); } } }

Thank you @Javi I'm trying not to be to much of a pain that is why I left it go until others brought it back. I really don't know programing and I don't think UDI should have to support other people's software but I appreciate all you have done so far to help!

@Javi I tried but I don't know what to change because it would not load with what I did. If it is something that will eventually work I can wait. I found ISYSUB 2 places in the hpserver.js file. If I just remove the firs bold it still worked the same with the below error V2.418 on 2/1/2022 8:27:04 PM Connection failure to ISY socket: Error: Expected a Sec-WebSocket-Protocol header. wshost: ws://192.168.0.30:8080/rest/subscribe header: { var header = {"Authorization": "Basic " + base64, "Sec-WebSocket-Protocol": "ISYSUB", "Sec-WebSocket-Version": "13", "Origin": "com.universal-devices.websockets.isy"}; wshost = wshost + "/subscribe"; and }); wsclient.connect(wshost, "ISYSUB", origin, header); }

I went into an older version of housepanel. The log file looks like this with the old 994 7/27/2020 4:08:52 PM Loading 1 hubs. 7/27/2020 4:08:53 PM HousePanel Node.js Server is running on port: 3080 7/27/2020 4:08:53 PM webSocket Server is listening on port: 1380 7/27/2020 4:08:53 PM Success connecting to ISY socket. Listening for messages... 7/27/2020 4:09:06 PM **************************************************************** Serving page at: http://192.168.0.40:3080 **************************************************************** 7/27/2020 4:09:06 PM Displaying main HousePanel web page: http://192.168.0.40:3080 7/27/2020 4:09:06 PM **************************************************************** Serving page at: http://192.168.0.40:3080 **************************************************************** 7/27/2020 4:09:06 PM Displaying main HousePanel web page: http://192.168.0.40:3080 7/27/2020 4:09:08 PM Connection accepted. Client #0 host=::ffff:192.168.0.40 Client count: 1 Pushing client #0 7/27/2020 4:09:27 PM Peer: ::ffff:192.168.0.40 disconnected. for: 1001 desc: Remote peer is going away All I did was change the IP address for ISY to the Polisy one and I get this and have the same behavior of not updating devices state 2/1/2022 7:00:48 PM Loading 1 hubs. 2/1/2022 7:00:49 PM HousePanel Node.js Server is running on port: 3080 2/1/2022 7:00:49 PM webSocket Server is listening on port: 1380 2/1/2022 7:00:49 PM Connection failure to ISY socket: Error: Expected a Sec-WebSocket-Protocol header. wshost: ws://192.168.0.30:8080/rest/subscribe header: { Authorization: 'Sec-WebSocket-Protocol': 'ISYSUB', 'Sec-WebSocket-Version': '13', Origin: 'com.universal-devices.websockets.isy' }

This is what it shows in the error log V2.418 on 2/1/2022 6:33:23 PM Connection failure to ISY socket: Error: Expected a Sec-WebSocket-Protocol header. wshost: ws://192.168.0.30:8080/rest/subscribe header: { Authorization: 'Sec-WebSocket-Protocol': 'ISYSUB', 'Sec-WebSocket-Version': '13', Origin: 'com.universal-devices.websockets.isy' }

Unfortunately that did not work @Javi and it made things weird that items in housepanel would not show a status change when I clicked on them until I refreshed the browser.

This is what is in my hmoption.config file which lists the isy information "hubs": [ { "hubType": "ISY", "hubHost": "http://192.168.0.30:8080", "clientId": "editusername", "clientSecret": "editpassword", "userAccess": "editusername:editpassword", "userEndpt": "http://192.168.0.30:8080/rest", "hubName": "ISY", "hubId": "isy01", "hubAccess": "editusername:editpassword", "hubEndpt": "http://192.168.0.30:8080/rest", "hubTimer": "0" Is there something I can change in here that might make it work?

@Javithe port 3080 is what I use in a Web browser to connect to housepanel

Well with housepanel it gets the devices from ISY and the proper state. I can turn them on and of and if I refresh the browser the state changes properly. The only thing is when the state changes it is not pushed to housepanel.

No unfortunately and I don't have the technical ability to figure it out and it seems the person who wrote the program I was using is not around anymore.

I can confirm it worked for me now thanks Michel!

Yes take a well deserved brake! At least we have access and I will try my older Z-Wave locks tomorrow to see how well they work.

For some reason clearing Java cache does not work.