Panda88

What version are you using? Can you send me a log with debug enabled - I looked in the code, and see no reason it would not work The logic is really not in the node (it presets both values being possible) - it is interface not accepting it (I believe) - there should be no node action when creating the program. Do you see unknown as an option in the drop down?

Can you send me a log with debug enabled and then restart the system I have no issues last week when split my system in two - remember do not restart system after you update the F2A code - you save and wait

I think I found a solution - I can create two nodes one for F and one for C and select them dynamically The only issues is the water sensors that have the same issue but besides temperature they have water volume (4 units) so it creates 8 nodes I'll try to get it done in next release, but you will need to fix your code then

I do not believe it works - it is internal to the console - it does not convert - only show the unit of the number provided My only solution would be to overwrite node definitions - not select between the units as I do now It has not been an issue for be as I work in C

I think the only way is to make two different node definitions - it may be possible, and I can take a quick look to replace one on the fly - if so it is an option - I will not start developing two sets of nodes for each device

I agree it is confusing - I actually think it is a bug in the console - I use a special method to specify temperature - I specify an option for F and an option for C (and an option for unknown as text)- otherwise I would need to generate 2 versions of any node that has different unit support (and code for each of them) The unit defaults to C (as this is what YoLink uses as default) and is changed (forced) to F whenever data is accessed - Console knows both exists and I believe in this case believe it selects the default - It may be there is something I can do to fix this (besides having one C variable and one F variable in the node), but I do not know how to.

Can you PM me a log with Debug enabled?? - is there a space before the 5 in Local_client_ID I cut and paste to email and email it to my self I would remove the picture with your credentials - you can always PM me

I think I found the issue - at least my current version (internal) does not show this - I am working on another bug I want to fix at the same time - The above is more cosmetic - there should be no functional issues

Yes - I realized there was a problem in the release - should be fixed now (I hope) if you reinstall

Looks like you are trying to use the YolinkLocal node - Did you set it to CLOUD in the config - hybrid and local requires the local HUB (log shows it is trying to access the local as well) - keep the local keys blank (Looks like you entered the cloud credentials there) Setting it to cloud (only) should allow this node to progress - but please make sure you have the local fields BLANK until you get the local hub You can also try the Yolink (no Local) - unless you plan to get the local hub in the future

Sorry to hear that is still not working - there is something in your setup (most likely the tesla APP) that is causing this. As you are selling your car, I will not spend more time on this unless others are having similar issues

you can also try to generate a new UUID/secret and insert that

Can you PM me a log file with debug enabled and I'll take a look Are you sure there are no empty spaces in the UUID / secret? Hub should be fine - but you need to configure the cloud portion - local only works on 1606 There should be install instructions in the more detail portion

I released the yolinkLocal to the production store If you are an existing user (of TSTYolinkLocal) and want to keep the setup, it seems you need to backup your system, delete the TSTYolinkLocal, install the new YolinkLocal in the same slot and restore the system. There is likely a bug in PG3 that prevents an upgrade when the node changes name - the nodeID is the same - only the name changed

Thanks - It seems there is a bug in PG3x handling name changes If it works, I'll release to production store and get going on releasing next version with improved error (offline) handling

Just to be clear - you have a license but it cannot upgrade? Can you make a backup remove the TST and install the new in the same slot and restore - does that work?

Added a new node to control Netro(home) irrigation controllers and moisture sensors Netro_watering Offers basic control as well as access to the data provided for the controller Do not poll too often as there is a limit for 2000 API calls/day per device - default is probing every 20 min

Thanks I'll contact UDI and see if there is a solution

Just removed the TST from the name in the non-production store - getting ready to move to main store - Can someone check if it allows update/upgrade of the TST version - This is a super version of the yolink server supporting both cloud and local operation (but also more complicated to setup) I hope to have 1.6.x working soon - better retry mechanism but I wanted to get all of this done before releasing 1.6.x (to keep variables to a minimum) I also have the new shufoff valves on my list to do - I did purchase them and hope it should be simple Also ordered the new ON/OFF Fob - want to see if it is truly ON OFF only or is it the same as the 2 key FOB limited in the App

Did you ever find out what the issue was?

Nothing obvious in install.log :-(

Can you send me the install log - I cannot see how it can still get the new version On the other had, I am happy the 1.6.0 works - I am seeing the same and plan to release soon - but wanted to upgrade to 6.0 to make sure it works there as well - I have not had the time for the upgrade yet

There is still a bug in the release - it is supposed to be 1.5.16 1.6.0 is very close to release - includes improved retry but it is not officially released I guess I need to understand my release tool better - I am not releasing from main (allowing me to test main before releasing) I installed 1.5.16 back to the release but 1.6.x is coming soon -= will likely switch to 6.0 before doing that release but need to finish something else first

It is MQTT related - may be 6.0 related - I'll try to figure out if something changed in 6.0 I have seen this before and sometimes a reboot/power cycle fixes it

There was a bug in speakerhub - did not update the ST - 1.5.16 should fix it