drprm1 Posted June 15, 2022 Posted June 15, 2022 8 minutes ago, Panda88 said: When you reboot it is designed to remove existing nodes and then recreate them - you often need to refresh the browser to the the node server to show all - it is a known polyglot UI issue Have you updated polyglot to latest version? There have been some node handling changes recently I do not see the behavior you describe - maybe you can enable debug in the log and send me a long log - Maybe I can figure out what is happening on 3.0.62...will update now
jkraus Posted June 16, 2022 Author Posted June 16, 2022 sorry, I did not know you needed to , nor do I know how , to update the polygot, can you let me know how?
Panda88 Posted June 16, 2022 Posted June 16, 2022 I believe a full power cycle should do it -unless you had a very early version I think you may have the latest version already 1
jkraus Posted June 16, 2022 Author Posted June 16, 2022 OK.. so figured out how to upgrade, now on 3.0.63
Geddy Posted June 16, 2022 Posted June 16, 2022 2 hours ago, jkraus said: sorry, I did not know you needed to , nor do I know how , to update the polygot, can you let me know how? I know you got it updated, but just so you (and others that might read this) know you can find the directions in the release notes in the "Current Release Announcement" threads. Specific the most recent for PG3 is found here: Make sure you follow the main forum area of Current Release Announcements to get notifications for any Universal Device release announcement made so all systems can be kept up to date. Update directions can also be found in the Wiki in the Polisy User Guide section.
jkraus Posted June 20, 2022 Author Posted June 20, 2022 the temp on my Youlink temp sensor is now reporting in Celsius again, despite having configured the NS Temp to "F"
Panda88 Posted June 20, 2022 Posted June 20, 2022 35 minutes ago, jkraus said: opps, restarted the NS all working fine now something is likely happening - need to take a look at it, but I am travelling without access to a debug setup so unless you can catch a log file showing what is happening it will have to wait until I return
jkraus Posted June 21, 2022 Author Posted June 21, 2022 yea, just not working. Go away for a few hrs launch the AC again and the nodes are once again gone. Not sure what file you want
jkraus Posted June 21, 2022 Author Posted June 21, 2022 If I hit "restart" on the NS then everything works again
Panda88 Posted June 21, 2022 Posted June 21, 2022 10 hours ago, jkraus said: does this help? thanks - do you have the polyglot log as well
Panda88 Posted June 21, 2022 Posted June 21, 2022 (edited) 2 hours ago, jkraus said: hope these files are correct ones Looks to me you have more than 1 version of yolink running - can you try to power cycle the Polisy? There are quite a few other node servers generating errors as well I did notice the motion sensor sends an openReminder that I did not know exist - it is not documented what the API can send as events - I am not sure if that is the root cause - I'll see if I can find a way to handle it cleanly - maybe even find a way to use it in ISY Edited June 21, 2022 by Panda88
jkraus Posted June 21, 2022 Author Posted June 21, 2022 OK rebooted NS and Polisy, seems to be working now, but in my experience that will be temporary, will let you know
jkraus Posted June 22, 2022 Author Posted June 22, 2022 (edited) ...well, spoke too soon, stopped working again with no changes to program. Rebooting the isy made it come back to working Edited June 22, 2022 by jkraus
Panda88 Posted June 22, 2022 Posted June 22, 2022 6 hours ago, jkraus said: ...well, spoke too soon, stopped working again with no changes to program. Rebooting the isy made it come back to working can you send a log again
tjkintz Posted June 28, 2022 Posted June 28, 2022 I am running the latest versions of Polisy and YoLink NS. Of the YoLink devices I have, it is the garage door controllers and sensors I really care about. In fact, that was the sole reason I bought a Polisy. At least twice, maybe more without realizing it, everything in IoP looks fine re: YoLink. I can query and toggle the doors; however, nothing actually happens. The door doesn't move and of course the state doesn't change. I can raise the door via the YoLink app or door button, but the IoP state does not change. My program that toggles the door based on other criteria runs but doesn't raise the door. The most recent occurrence was this morning. I restarted the NS from Polyglot and then I could successfully toggle the door from IoP and the sensor would reflect the proper state. Restarting the NS seemed to remove and then add the YoLink devices. However, the programs I have written to run when the door state changes, are not running. The if-clauses look like they are pointing to the right devices. I increased the NS logging level to debug and may get better data re: what is happening but, in the meantime, are there any clues or suggestions to isolate and eliminate the problem?
jkraus Posted June 28, 2022 Author Posted June 28, 2022 (edited) Exact kind of action I see on my motion sensor. Yes, I have been debugging with @Panda88, He is working a solution, as currently (at least for me) YoLink is just not consistent. works...then doesn't Edited June 28, 2022 by jkraus 1
drprm1 Posted June 28, 2022 Posted June 28, 2022 "Restarting the NS seemed to remove and then add the YoLink devices" This is what I see too....Do all node servers do this? I never noticed
tjkintz Posted June 28, 2022 Posted June 28, 2022 (edited) "Exact kind of action I see on my motion sensor." Oh great, I just ordered 3.☹️ The NS didn't continue working for even an hour. It never detected an open or close and sending toggle commands from IoP again does nothing. The NS log shows nothing for the open and close times whereas the YoLink app history shows them. @Panda88, let me know if there is anything I can do to help debug. Edited June 28, 2022 by tjkintz
Panda88 Posted June 28, 2022 Posted June 28, 2022 (edited) I am also trying to understand what is happening, but it is not easy - I believe the MQTT connection is somehow shutting down -the code stops receiving the messages being sent (even with external sniffer). Note, the YoLink app must use a different API than the one that is presented to external users, as it has more information available that what the API I use offers. I have noticed that it seems that only 1 credential can be used - e.g. you cannot use the same credential for multiple applications (ie. running both on HA and Polisy). - only one for them seems to be served by the API If you know how to log into polisy and retrieve files there are files logging all MQTT events that are recorded by node server. there you can see if the event get generate a log entry that was not passed to ISY I cannot rule out that I am doing something wrong in the code (I probably am and I am no expert in MQTT - it is my first project on MQTT), but it is very difficult to debug. It seems the API suddenly stops reporting events - When I detect it I restart the connection, but it does not make sense to me that I have to keep polling the connection (that is not the idea of MQTT) and furthermore, the even could still happen between connection is lost and the next poll. Th main issue is to understand why the connection stops. The question about removing and reinstalling the nodes - I do it because of a bug that you cannot remove a mode from the polisy interface once created. The bug may have been fixed by now, but I have not seen it being important to change the code - nodes will get same names and everything should b the same - also - I hope to get to a point where there should be no need to restart the node server. Lastly - on my own local setup the connection remains up (or gets restarted) - I may miss events 0 I have not been focusing on that, but my garage door controller keeps working (to open /close) - it used to stop working after a while - naturally it does not mean there is no issues in the code - just makes it even more difficult to debug Edited June 28, 2022 by Panda88
Recommended Posts