Panda88

I had Envisalink check - there are no devices connected on teh TPI port (4025) - it still refuses connection

thanks Let me check - In the past I had issues with rain machine devices attaching to the envisalink - It is just strange it worked until changed to PG3 Also - I can log into device from browser, but it may be a different connection type

thanks There was an issue when installing - I was asked if I wanted to install in in the existing slot(PG2) - I said yes - and after that both pg2 and pg3 showed the node. I deleted the PG2 node but it did not solve the issue

Just upgraded from PG2 to PG3 (trial). It was working nicely on pg2 but I cannot get a connection to the Envisa from PG3 - I can log in via browser without issues Any suggestions - I cannot find anything in the log file but you may see something Thanks debug.log

Seems the eisy may be good for development - What development tools will be supported for node server developers?

Just a quick update - I checked my latest code and it does not show this behavior. I'll work towards releasing that - and maybe figure out what is causing the strange behavior - there must be an infinite loop somewhere but not easy to debug on the Polisy platform as I have no development tools there

I see the same issue - not sure what causes it (yet) My new release in testing does not see the issue, but I have far fewer devices on my test platform Polls are not truly needed - MQTT updates when actions happen - short poll is mostly to send a heartbeat there are cases where an update sometimes takes longer so the state has not changed when the display updates on the Admin Console - in this special case the poll causes the display to update - Not if using programs this does not matter

Polls are not truly needed - MQTT updates when actions happen - short poll is mostly to send a heart beat there are cases where an update takes longer so the state has not changed when the display updates on the Admin Console - in this special case the poll causes the display to update - Not if using programs this does not matter

top is installed - it shows the issue Trying to figure out what causes this

I did not study the CPU usage in great detail - I am in the progress of changing the message handling approach - It used to be every device was waiting for input from a queue - I am changing that to start a thread when a message arrives - I think that will lower the CPU usage I cannot think of anything else causing a lot of CPU usage - unless you are using the delay timers

Each device is really a node server by itself - I'll see if there is something obvious wrong but it may take some time to get to the bottom of it

I'll take a look How many devices have you installed? Do you know if Memory increases over time?

I think I fixed it - I made a wrong commit about 12 days ago and that code caused this to happen I am working on redoing the message handling and hope to have a new and improved version soon

Can you send log with Debug logging enabled?

Yes - if you can stop and start and get the log file I can check to see what is happening - it looks like it thinks there is connection to both cloud and local, but it looks like cloud is not working correctly there is no real documentation - even on github, but you are welcome to check out the code there. I am just doing this for fun, and the charging is mostly to give some extra income to universal-devices (they get half of what you pay).

What is your setup - are you running both cloud and local - or local only? -1 means no value retrieved? If running local only you need to run for 24hours before yesterday can be deployed - (it only reports current status). I'll take a closer look once I understand your setup (there is no initialization in the log you provided) Generator is an optional mode where a generator can also be enabled when battery runs out

I did notice a network error in the log as well 2022-11-19 07:13:48,998 Thread-1259 udi_interface ERROR TeslaInfo:pollSystemData: Exception PollSystemData: Powerwall is unreachable: HTTPSConnectionPool(host='192.168.1.71', port=443): Max retries exceeded with url: /api/meters/aggregates (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x8031acee0>: Failed to establish a new connection: [Errno 50] Network is down')) i'll try to see if I can find a way to reconnect if this happens

Looks like you are not looged into the local power wall - Can you log in from Browser? 2022-11-19 08:03:05,414 Thread-6 udi_interface ERROR TeslaPWController:tesla_initialize: local authenticated failed.

Can you send me a log with debug enabled It usually happens if system does not start correctly - it may be you need to power cycle your power wall during start up - to log into it locally - something they recently changed

I actually mean to remove the yolink node (delete it) and then reinstall it - If you replace 1 to 1 I think the programs will remain unaffected - I have tried with my own nodes but not purchased nodes Maybe you can contact Michel and see if he can reimburce you if you purchase again - I am sure it should be ok. Naturally, we should try to get to the bottom of what happened, but it will allow you to move forward

The latest YoLink node server does support the speaker - not as elegant as I would like, but there are some limitations with regarding to text in the AC (you basically need to predefine you text (announcements) and then you can pick them in the AC) -

did you reboot PG3 after the upgrade? I am not 100% this will work, but if you do not start AC - could you erase the node in PG3 - that should free up the node slot) and you can reinstall in the slot - I have done it before with success - you may need to refresh the program and save afterwards - but no editing should be needed

You do not see this option

In my case, there is an option 2/3 way up on the install page to install in existing slot - do you not see this?

It should be 0.6.15 - it shows in store as 0.6.1 but it is a bug in PG3 - when you enter the node you should see 0.6.15