Panda88

you may have to press update Profile

I think you just clock the yolink node, click what you paid and do reinstall here (not new slot) - it just copies the latest code over

from the node server click log -then select debug (on right side drop down) Reboot - wait a little and then select download log - send to me as private message

Just checked - I must have made a mistake checking in the editor file at some point so the info was lost. If you force a reinstall it should work - I did not update version as I have been working on other stuff SelfcheckState-0 = Not recommended SelfcheckState-1 = Recommended SelfcheckState-99 = Unknown As you can see the self check is note for you to perform it (I guess)

I do not know how self-check works to be honest - I have never seen it fail. 1 / 0 seems like a node problem in setup files - I can check - but my smoke detector is no longer on-line so I need someone to help check it afterwards For control vs. status. Controls can send actions (trigger other devices) - status you need to check and make your own actions afterwards. The idea is you can trigger on a smoke event but not on a temperature reading

you can send me a log file - enable debug please - and I'll see if there is anything The devices show up separately from the node you show (as stand alone devices)

i hope to be able to start looking at it the coming week - I have a new items to close and then I can focus on this one

My thermostat is set at 41F as heat point (permanent) - it shows correctly in node, and on thermostat. However, temp shows 160F on node server but 61F on the actual thermostat. Another thermostat works fine (running auto). Is there a bug or has something changed - I think it worked fine before Also - how it away mode working - It seems it only toggles on - how to disable it? Thanks

Correct - I meant to say that I do not believe the password resets the UAID etc (it has not in the past)

I am aware and on my list - I just got a beta for oauth support in the ISY needed to use the new API. I have not started to test it yet - I'll likely do another (simpler) nodeserver first before addressing the tesla one (I do not have a tesla to test on so I need to make sure I understand the use of the new oauth API before starting the tesla solution

I am trying to throttle the calls to match the new limits, but my count does not match what their server uses for throttling. Also if a device goes offline it shows up as being throttled ?? I did try to introduce a throttled state in each node, but not sure how well it works - There are likely still some bugs as the logic has had to be changed and that introduces bugs On the use of UAID - there is no relationship to the login - unless the reset the access when passwords are changed - you can likely see in the app if the password is revoked You can also send a log (PM) and I can take a look

I am not aware of any progress - there is a new cellular enabled HUB being released - there were rumors that it would support local API but I doubt it will be available at launch.

Hi I think all of these should be there already (besides RF level/strength) - I can add the RF strength but in my experience, it does not change if the devices are stationary (it should not). I cannot rule out there is a bug but it is intended to show this. Note, the node cannot keep testing to see if the device is off-line - as it only queries the cloud status (it would drain the battery if checking the device all the time), so I have to wait for a notification that the device is off line send from the cloud. Also, this is difficult to test as it does not happen often. If you can get me a log (debug mode enabled) showing when the device is offline I can see if it behaves like the node server expects (for offline status) There are 2 fields for battery and Status should show the connection status (Name may not be well chosen - I'll think about a better name next time I fix a bug) )

You may need invite from service@yosmart.com

If you are not trying to integrate YoLink onto an ISY, it is not the correct forum - there is a discord channel for Yolink - Yolink-power-user-group

I think the thinking should be - trust the YoLink temp sensor to send updates when something changes. Even if you query the temp sensor, I believe you only get data from the cloud - If you were to query the temp sensor for data, battery would run out faster and you would get no real extra info (as temperature has not changed). Note, there is an update every 1 hour (I believe it is) It may be possible to get info on when last temp sensor measurement was made but time is not handled easily in the ISY. I could look into it, but need to understand the use case. The node/device being on-line shoudl be a similar indicator - again - I do nto believe I can force a reading from the temp sensor - it is only reporting the cached data from the YoLink cloud server (as YoLink believe their device will send data when something changes)

The yolink sensors send updates when changes happen so updates (timing) depends on the situation. I doubt you need to do something extra in your case. I do not know the update rules for humidity but you could ask service@yosmart.com There is currently no difference between update and query - besides query can be rub at a higher level causing all devices to be queried

Can you message me you whole log. I can see if there is something happening before the issue?

You can also try a reinstall. It may install files again

Did you do a power cycle? Another option is to generate a new token in the yolink app If not i would open a ticket

I have seen this as well - on more than 1 node server - I have restarted polisy and it went away, Not sure what caused it

I doubt it - unless the web interface which I assume is operating on a different port

Hi I have 2 system setup. One is working flawless and the other has issues on and off. I though there may be issues with the envisalink so I ordered a new one but it remains the same. It sometimes will not start - it retrieves the system (all nodes etc so it must be talking to the envisalink) but when it comes to panel1 it states there is no connection - some times it manages to get by this state and I will work ok Any idea log: 2023-12-16 14:54:08,500 Thread-51 udi_interface DEBUG nslib:start: In start() for node panel1... 2023-12-16 14:54:08,502 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '53aad9c8-a83b-4776-9cc5-bd7b5a272909', 'uuid': '00:0d:b9:52:d9:38', 'profileNum': 5, 'address': 'panel1', 'name': 'Alarm Panel', 'nodeDefId': 'PANEL', 'nls': None, 'hint': '16843008', 'controller': 0, 'primaryNode': 'panel1', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1677029040739, 'timeModified': 1702767248422, 'dbVersion': 1} 2023-12-16 14:54:32,144 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:54:32,146 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:54:32,147 Thread-52 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:54:32,149 Thread-52 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:54:32,150 Thread-52 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:54:32,150 Thread-52 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:54:32,153 Thread-52 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:54:32,154 Thread-52 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:54:32,155 Thread-52 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:54:32,157 Thread-52 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:54:32,158 Thread-52 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:54:32,159 Thread-52 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:54:32,160 Thread-52 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:54:32,161 Thread-52 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-16 14:54:32,163 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'panel1', 'driver': 'ST', 'value': '0', 'uom': 2, 'text': None}]} 2023-12-16 14:54:32,165 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'key': 'notices', 'value': {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'}}]} 2023-12-16 14:54:32,449 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-12-16 14:54:32,451 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-12-16 14:54:32,452 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'} 2023-12-16 14:54:32,453 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking no_connect / Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. 2023-12-16 14:54:32,489 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-16 14:54:32,492 MQTT udi_interface.interface INFO interface:_message: Successfully set panel1 :: ST to 0 UOM 2 2023-12-16 14:55:02,124 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:55:02,126 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:55:02,127 Thread-53 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:55:02,129 Thread-53 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:55:02,130 Thread-53 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:55:02,131 Thread-53 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:55:02,133 Thread-53 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:55:02,134 Thread-53 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:55:02,135 Thread-53 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:55:02,136 Thread-53 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:55:02,137 Thread-53 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:55:02,138 Thread-53 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:55:02,139 Thread-53 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:55:02,140 Thread-53 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-16 14:55:02,144 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'panel1', 'driver': 'ST', 'value': '0', 'uom': 2, 'text': None}]} 2023-12-16 14:55:02,147 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'key': 'notices', 'value': {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'}}]} 2023-12-16 14:55:02,260 MQTT udi_interface.interface INFO interface:_message: Successfully set panel1 :: ST to 0 UOM 2 2023-12-16 14:55:02,302 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-12-16 14:55:02,305 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-16 14:55:02,305 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-12-16 14:55:02,308 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'} 2023-12-16 14:55:02,309 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking no_connect / Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. 2023-12-16 14:55:32,130 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:55:32,131 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:55:32,133 Thread-54 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:55:32,135 Thread-54 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:55:32,135 Thread-54 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:55:32,136 Thread-54 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:55:32,138 Thread-54 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:55:32,139 Thread-54 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:55:32,140 Thread-54 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:55:32,142 Thread-54 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:55:32,143 Thread-54 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:55:32,143 Thread-54 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:55:32,144 Thread-54 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:55:32,145 Thread-54 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot.

OK - I though you had the flow meter as well I believe this is the same API as the manipulator that is/was used to control valves before. The name of the node is what you specify in the YoLonk app (short of special characters) - the yomanipu is the manupulator driver. This shoudl work fine

My guess is it reports as 2 different devices - and one is the valve controller (manipulator). There is no API yet for the flow meter but hopefully it will come soon. Once it is available maybe you can give me access to your controller for 1/2 a day and I can likely add the support - I would buy my self, but they do not have my pipe diameter