Panda88

Updated version to 1.1.0. Supports python 3.11 which the next release of PG3x requires Will still work on PG3 but not sure how long it is possible given PG3 runs older version of python. It is suggested to upgrade to PG3x (testing will be on PG3x going forward) No other changes introduced

I have released a new version of the tesla power wall node server. It uses the official Tesla API and requires PG3x to operate If the current node server works well, there is no need to update, but there is a chance Tesla will force people to update by making new requirements to log onto the power wall (They have done it with the cars). Limited new functionality - mostly reorganized the data and added a few more options

I think I have found a way around this - Still need some more testing, but I can get past the login

I did play around with this but no luck so far - it requires changed deep in the API - I was hoping for a new API to be released

It is a common issue in the API - waiting on an update to the API I have been using Alexa to control in the mean time Sorry - I do not understand the low level communication used by Blink needed to fix this

I am running into some issue with controlling the car. There is s new protocol on top of api and ort is written in a language not supported by Polisy - looking for a solution but it may take a little time

Updated to version 1.0.9 Minor fix to improve cases where tokens are lost - not easy to test (and it should not happen often)

I am working on it and is getting close to release it (beta) There are quite a bit of changes from the original API so it takes time If someone wants to take it over I am more than happy to support that

It looks like an issue at the Yolink server - did it work before? Did it come back - it should keep trying Do you have a full log I can look at?

Just to follow up - it seems the authentication has changed - waiting for update to API

I will take a look later - it is possible they have changed their authentication procedure - I need to research this as it is not using an official API

i am working on it but running into some issues with refreshing the token required - once fixes it should not be long as long as I can get access to a car to test

Yes. It may be specific to my need (developing the SW) but i do change sensors around between different setups so i want to erase the nodes not being used anymore. I guess i could check ifnode is already there and the keep the definition (I'll look at what it takes next time i change something) Disabling the sensor should do the work i believe

I do not disable devices. You can erase the nose if needed. The string is mostly to associate Nodeid to a name. I realize it will recreate the node when restarting. Maybe i need to rethink this I could allow a none to exist but it will require 2 restarts to take effwct

If someone can direct me on what to do, I can try to add it if it does not change the code structure too much As I mentioned I have not used mobileLinc before and I do not know the requirements Currently I do not use hints, so it may be possible to add the hits (as long as I know what to set it to)

I do not know mobilinc and the requirements for it. Do other uplink devices work with it? Any documentation as to what is required Thanks

Latest version is 1.0.8 after another minor bug fix for the water meter controller

New Node server for smart valve products from Netatmo. I do not have a boiler controller but if someone can give me access I can add support Requires PG3x - will not run on PG3 - Does implement the latest Oauth login

Latest version is 1.0.7 after another minor bug fix

It is always difficult to handle connection when there are multiple connections - one is from node to ISY - the other is node to YoLink API I have used ST (shown above to show connection to ISY I have used GV20 to show connection state to Yolink API I believe the leak sensor should be fixed in 1.0.7

I fixed the garage door controller to show connected (even if it was not activated) I also found that I somehow had commented out the connection change in the leak sensor (it was the one I used for main development) - it is also fixed 1.0.7 is coming soon

What variable are you referring to - Online-Offline/suspended is GV20 ST is supposed to show connection to ISY - I think I did default it to no-connected until first transaction The leak sensor (first one) seems to show GV20 = 0 - so connected - 1 is suspended due to too many calls and 2 is offline

If you can send a log - with debug I can try to see what is going on - It may be in needs to wait until first poll - Garage controller is trick as you cannot poll it

Version 1.0.6 is available Mostly a fix for off-line reporting for sensors

Working to Finish the tesla power wall node first (as I have access to one) - allowing me to test the API After this the I am on to looking at the EV server. I did do the initial changes, but testing will not be as easy as I need access to a car to test it (I no longer have my tesla) - and it requires authendication