Panda88

If Yolink were to stop, we would not be able to add new devices etc. It should keep running with what is already there, but adding new devices etc. still rely on the cloud / App

You need to restart the node after enabling the debug level Devices still send data - I just do not process it (as I do not know what to do with it Should be able to see what is reported and then make the needed changes

if you can send a log with power and without power i can tage a look. they do have a dedicated device for this. i do have the pro hub (probably similar to X3 hub) and it may have the same reporting - I'll take a look when I get some time

The plugin ignores the HUBs (besides speaker hub) as they cannot do anything besides being a connection to the cloud

I did some rudimentary test and it worked. I cut the data into the modem when I tested

you should have 4 sub nodes where you define the operations for each press type. i have the same fob and it works Are you trying to use a scene to control this ? I still believe it should work, but I have not tried it I have used programs mostly with this one Send me a debug log (enable debug and press the different keys are few times)

It is mostly to check if all service work. I had some i could not get to work but it may have improvef

can you test 1.4.26 a little longer and if ok ill release the version - yes it was a typo

does the 1.4.29 have the issue you mentioned before. how do i create it for testibg?

It makes little sense that other leak sensors work and one does not - maybe give it a try a little later - sometimes there are issues on the server side

I'll keep it in mind next time I change something

OK - The issue is ST is used to represent if connected - not on/off for this device I guess I can look at changing it but it may cause issues for others

I use UOM=25 to support unknow value

I did a pre-release for you if you are interested ? As I understand there no easy way to revert back - yolinkTest in the non-production store - if it works I can release to the real node

can you ask UDI about this. it may be a define somewhere i am missing but i do not know how to fix

Does the AC change state - I am not very knowlegdable on UDM - but is AC works I need someone else to give a hint as to what to do on UDM

It is difficult to know when connection is down - there is likely an indication on API return but I have not found it yet Yolink is looking to add hubs to local network. - did not work last time I tried - o doubt the speakerhub will work in local mode but i cannot say for sure. I think the tts is in the cloud

You have to create a new set there

Creating a new home should generate a new UUID etc. There is a list of them - one for each home

The local is a few revisions behind - I did not update it when people could not get hub I should be able to use the same code base for both, but initialization is a little tricky as I do not know if system is local or not when the node starts (so it would require to different programs/code to start the node) - beyond that it is common code - this is how it is now - but in two different branches currently (that is why it is behind) - I was planning to let the user specify if local is needed (through the config) but I have not gotten around to look at it yet (config is the most complex part due to the multi-threading of PG3) It may be possible to keep it as one - and it should be a goal, but not sure when I can make it

Tim Maybe you can try to make 2 homes - that should allow 2 sets of credentials and allow operation of existing node - you need to move your test device to the new "home" - I think the new home needs the local hub for testing I do not know enough about PG3 to answer the ID related issues

Correct - I have not found a way to identify the connection type yet - I have a request in but no reply yet The old hub can be used to extend range of network (but the devices attached will not be local (yet - they are working on this) - I have some devices in a pump house that the local hub does not reach reliably (I have an ethernet conenction there), so I hope they will get this working

I so not think there is a need for curl. It is separate from the node. You just need to move you devices to the local hub - do it one by one initially. If you have more than 1 hub (for range reasons)!the local hub must be able to see the device you move

correct - I do not recall if I had to push anything on the hub - I only use ethernet I found some info on home-assistant forum initially that helps me get going

response = requests.post(self.local_URL+'/open/yolink/token', data={ "grant_type": "client_credentials", "client_id" : self.local_client_id , "client_secret":self.local_client_secret }, timeout= 5) if response.ok: temp = response.json() logging.debug('Local yoAccess Token : {}'.format(temp))