Panda88

0.7.2 - I see it inthe production store - maybe try to refresh the store

Found a bug - 0.2.16 I have been working on furhter improvements but not released yet

Do you have a more complete debug log (enable debug) - It is very difficult for me to debug this as I do not own a Tesla. I'll take a look tomorrow

Ignore above - I had a mistake in the release procedure - try 0.7.2

Can you send log? - I removed code to remove nodes?

I somehow got it to connect - not sure what happened - maybe the Envisalink people did somehting remotely

I released 0.7.1 I am no longer trying to remove older nodes - Main issue will be with multi Output devices - the naming changed to prevent multiple nodes with same name (when using multiple multiOutput of same type) Hopefully this works now

I see an error - I'll take a look tomorrow - I think there is a bug when the addresses are too close The removal of nodes was only supposed to remove the sub nodes of multi-devices - I had a bug in the old node

👍

I wonder if my router/firewall updated FW and somehow blocked the port (on the LAN side) - I did submit a question there as well

yes - even power cycled it

I think you can just refresh the store and it should show up

Just released version 0.7.0 - I believe it resolves the resource use

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?