Panda88

click on the localHub and get the needed info under general and integrations

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

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

Try now - it shows on my other eISY now (It always shows on the one used to release)

there was a mistake in the release - try 1,4,22

Try to install 1.4.22 - I had a mistake of not enabling all devices (used during test)

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

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

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)

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

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

I have not tried it, but I guess it should e possible as long as you can share the TTS definitions

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 -

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.

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

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

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

There is a slack channel where people are helpful I think you can achieve what you want using the automations in the Yolink app

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

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

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

Enable debug and send me a log (you can PM me) - I'll take a look I do not know how devices instantiate and I do not have one yet - just ordered the new one with shutoff valve. I believe it should be an easy add once I get a log

I am not expecting a special version for you - just for you to test if it helps before I would release it as a new version (there is no need to do a new version if it does not help) Nothing obvious in the log (from my side)

I can provide a non-production store release with traditional config file to see if that fixes your issue Let me know and I can prepare it - if OK I'll make a full release of the node

It may be related to you setup with separate ISY - any particular reason not running it internally on the Polisy? I know this node has some "optimization" on how the NLS file is made and I wonder if that could cause this - I can try to change it to not use common NLS settings - I know it affects the REST interface in some cases