Jump to content

Panda88

Members
  • Posts

    727
  • Joined

  • Last visited

Everything posted by Panda88

  1. It should but i have checked it recently. Tesla may be changing the local access requirement. I am ravelling so i cannot check until i return as you needed to do a physical switch when starting - see the notes
  2. i was referring to a change i am planning - not there yet ill check what changed in v22 biy the only thing i can remember is commenting out a debug statement that was causing an issue ill see if i can debug while travelling
  3. It appears for the log that it goes back to the original message (0) after trying node 2 and later node 3 - Is that not the case? If it is the case, it may be a bug on yolink side Anyway - I am thinking why not include the message as part of the pay function directly (no need to select message first) - would that work? - then there is no reason to cache the previous message text then - I could add the other parameters as well - It is possible to do this now with the later versions of pg3x
  4. I'll take a look to see if I can find something - I did not change any code relating to this, but there must be a bug. I have no way to test as I am travelling Can you send a full debug log - the issue may occur earlier than what you included - ideally as a log zip file
  5. Panda88

    Yolink Local API

    click on the localHub and get the needed info under general and integrations
  6. Panda88

    Yolink Local API

    I was expecting that - I had to create a new node to get it on the non-production store
  7. Panda88

    Yolink Local API

    YolinkTest is for different purposes. ill remove it later as changes have propagated to the production node
  8. Panda88

    Yolink Local API

    Try now - it shows on my other eISY now (It always shows on the one used to release)
  9. there was a mistake in the release - try 1,4,22
  10. Try to install 1.4.22 - I had a mistake of not enabling all devices (used during test)
  11. Panda88

    Yolink Local API

    I added a new TSTyolinkLocal - hopefully this one makes it through
  12. Panda88

    Yolink Local API

    I am not sure what happened - I pushed it - it showed up and was later removed - It happens often to me - not sure why I have not tried to replay the original node - It will have a different node id, but nodes should have the same names and addresses - it may work and it may not
  13. what do you mean by nodes? there should be one node per speakerhub registered. the setting is to select different messages to be played on different conditions you may need to restart once more as the node updated and it will not remember the setting from the previous version if just set (i believe)
  14. there is a config parameter NBR_TTS you can use to specify the number of messages that can be defined. I think the code allows you to set a higher number - and you should then run the node, stop it and start it again - that should increase the number of messages that can be defined It may not work, but let me know if it does not and send a log file with debug enabled
  15. I think the number of messages is arbitrary - I can likely increase it but it has been a while since I looked at the code - I'll put it on my list when back from vacation
  16. I have not tried it, but I guess it should e possible as long as you can share the TTS definitions
  17. Panda88

    Yolink Local API

    Just pushed the YolinkLocalBe to the non-production node store You need to enter IPaddress and SUBNET_ID, local client_id and local_client_secret (from Yolink app) Set mode to hybrid (probably not needed any more) - there is no true local mode - it communicated through the hub to the internet and only allows local operation if internet is not connected -
  18. Panda88

    Yolink Local API

    you need new node. you keep the existing uuid and secret but need to add the local key as well. ( see earliervin thread how to get it) the hub will work as existing hub without the local key once added (with the new node server) and devices are made local (on uolink app) it should work as existing app.
  19. Panda88

    Yolink Local API

    may not be until tomorrow. i cannot get my VPN stable
  20. Panda88

    Yolink Local API

    aounds good. ill try to get access to internet (vpn) and release as a beta today (i hope) there is limited difference from the original node besides the need for a different authorization
  21. Panda88

    Yolink Local API

    I have a beta release i can provide. a new node is needed to support local integration. it should run fine with existing node if no local integration is needed note i am travelling so supporting the beta node will be slower and more difficult as i do not have access to my setup
  22. There is a slack channel where people are helpful I think you can achieve what you want using the automations in the Yolink app
  23. You can reference the node variables directly in an email - like this You can find the names in the node definition in the node server e.g. just copy (press the copy icon) the relevant one - in your case CLITEMP you can then make an email (like above) with the desired info and have a program send it to you at a given time
  24. Can you enable debug and send me a log - I need to see if the data reported had changed - I do not recall being able to extract the info from the log - that said it is a long time ago and things may have improved You can just PM it to me
  25. I have not used it extensively - basically you can train different codes to be transmitted, and you can then control when to send them from the node. I tried to enable leaning from node, but never managed to make it stable, so you need to train from the YoLink app and then you can activate from node If you need more features let me know and we can see if they can be added
×
×
  • Create New...