Panda88

I am not on 5.5.5 yet - I am out this weekend, so it will have to wait until Monday - need to have enough time to investigate what is going on

I went ahead and ordered one - we will see what I find

I see a smartRemoter API. I assume that is the remote. I can buy one next time I buy devices and then try to integrate - unfortunately I just bought some so it may be a little while - I'll add it to the list

Strange - it is doing exactly what it is supposed to do - It says is does not see any changes in node-defs - (which is true) - 0.7.5 corrects a few spelling errors -that is all I am not sure - it is possible the SW is too smart and does not upgrade because it does not see a change. The changes actually end up on the ISY I just received the power-fault detection device and will add this soon - I believe that release will force an update for sure as I will be adding a new node type

Can you send the PG3 log as well - everything seems fine besides speakerhub not connecting - I verified code on github is 0.7.5. I assume you have a version from the production store (you should have otherwise it would not notify on a new version)

Do you have a log - I think code should reflect 0.7.5. It seems like the node is still using the old code.

will do thanks Christian

Yolink should work well for that

List is up to date. I did not get a thermostat yet, but It should not be too much effort to add it If you are willing to work with me (or let me access it for a little while) I can try to add it

Is there a log for the PG3 it self you can provide. There may be an issue with installing on of the python libraries. I am travelling and am not back until the new year so it's difficult to debug - especially without a log being generated

Thanks - unfortunately PG3 uses pip for install - I may be able to use pkg as part of the install script - need to experiment a little

I did update the requirement.txt to force the version I use - Can you try to delete and reinstall ?

If you are talking sub nodes of a multi-output device (e.g. numbers outlets or USB outputs) - then yes - this release renamed those nodes - I found a case where 2 nodes would get the same name with the old names (It was a bug in the first place) - I do not expect other devices not to show, unless yolink do not report them It was mentioned in the release note

Possible - I am trying to get a new Test_TESLA_EV released

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