Panda88

Maybe I can try to rename it

Thanks - I will be travelling so out of reach for a little while - Not too urgent to check it out - just wanted to get the latest changes in - It seems Tesla changed how they report sleep and this addresses this and some other fixes

Is there any chance I can get you to try the release in non-production store - There are some fixes there I want to release it but do not have a good way to test

I can try to force the original version I was using in the requirements @Michel Kohanim - Can I get you to try to build version 5.9.2 I do not feel like trying to edit this package

0.2.18 hopefully fixes it - there was one more conversion bug in the code

yes - looks like a build error - I was on 5.4.4 when building it and used release 5.9.2 @Michel Kohanim - Any input as to why psutil will fail build on 5.4.5?

I believe I fixed it already - it was one of my first python projects and I have no way to test the control code, as I do not have a car to test it on

0.7.2 - I see it inthe production store - maybe try to refresh the store

Found a bug - 0.2.16 I have been working on furhter improvements but not released yet

Do you have a more complete debug log (enable debug) - It is very difficult for me to debug this as I do not own a Tesla. I'll take a look tomorrow

Ignore above - I had a mistake in the release procedure - try 0.7.2

Can you send log? - I removed code to remove nodes?

I somehow got it to connect - not sure what happened - maybe the Envisalink people did somehting remotely

I released 0.7.1 I am no longer trying to remove older nodes - Main issue will be with multi Output devices - the naming changed to prevent multiple nodes with same name (when using multiple multiOutput of same type) Hopefully this works now

I see an error - I'll take a look tomorrow - I think there is a bug when the addresses are too close The removal of nodes was only supposed to remove the sub nodes of multi-devices - I had a bug in the old node

👍

I wonder if my router/firewall updated FW and somehow blocked the port (on the LAN side) - I did submit a question there as well

yes - even power cycled it

I think you can just refresh the store and it should show up

Just released version 0.7.0 - I believe it resolves the resource use

I had Envisalink check - there are no devices connected on teh TPI port (4025) - it still refuses connection

thanks Let me check - In the past I had issues with rain machine devices attaching to the envisalink - It is just strange it worked until changed to PG3 Also - I can log into device from browser, but it may be a different connection type

thanks There was an issue when installing - I was asked if I wanted to install in in the existing slot(PG2) - I said yes - and after that both pg2 and pg3 showed the node. I deleted the PG2 node but it did not solve the issue

Just upgraded from PG2 to PG3 (trial). It was working nicely on pg2 but I cannot get a connection to the Envisa from PG3 - I can log in via browser without issues Any suggestions - I cannot find anything in the log file but you may see something Thanks debug.log

Seems the eisy may be good for development - What development tools will be supported for node server developers?