apostolakisl

had some issues with .05 and went back to .04. The node is still populating correctly. ???

@Javi I am still having issues with the names of thermostats I added. For Example, Venstar AHU1 Conf (this is fine, displays as expected) Venstar AHU3 Lobby (this displays as Venstar AHU3 it cut off the Lobby part) I open the full device dashboard page and the full name is there, I try to edit the name, hit save, but it doesn't save it.

I'm still on 6.0.4 and did legacy sync and at first glance it seemed to have worked.

I restored a backup from a few months ago, and all is normal for how it was at that time. But when I do a synchronize, it breaks again. I got no errors, but my nodes are either missing, not configured correctly, and nothing populates. This isy is running 6.0.4. I haven't made any changes to the ISY firmware since I upgraded to 6.0.4 however long ago that was (not long after it was first introduced). The changes I made that needed sync'ing was I added a new PG node and moved a PG2 node to PG3 and deleted a few devices and changed a few programs. EDIT I tried uninstalling ud mobile and clearing all data. Again, the sync results in the same non-functional ud mobile. Restoring the backup gets it back to a working ud mobile as it was at that time.

I have two ISY's connected to UD mobile. I made a bunch of changes to one of them and re-synced it. I got some error about a node definitions file if I recall and now none of the nodes on that 1 ISY work. My favorites folder had bunches of stuff from that ISY disappear. Further syncs show no error but don't fix it. @Javi The other isy seems to be normal.

@paulbates Seems that you are correct. I factory reset again, setup wifi, turned on api, and they are both working with nodelink and pg3x. I will let it go for a few days and then see what happens if I try connecting to skyport.

Possible. I factory reset the two that aren't working, connected to wifi and turned on the local api, and I got a connection on nodelink (didn't try pg3x at that point). I thought I had it fixed, I then rejoined skyport thinking I was good. When I went back later to check on it, it was no longer working. So maybe I need to leave skyport off.

There are no clients connected to the ones that won't connect. The ones that will connect have no issue being connected to nodelink and pg3 at the same time and accepting manual queries. The ones with no cleints connected won't respond to manual query commands either. I tried connecting to only 1 thing, then if it didn't work tried the other thing. I agree with chatpgt analysis that the thermostats' public api engine is crashed/frozen/whatever word you want to use. It is clearly on but not responding to anything but simple commands.

I just noticed in nodelink that the two t5800 with dongles that aren't connecting are reporting the thermostat type and firmware to nodelink. Nodelink shows that info, but it does not show any data. I did a curl query to one of the thermostats that doesn't connect and the same to the one that does, and the one thermostat gives a response, the other doesn't. It seems as though the local api is off, despite being on. C:\Users\apostolakisl>curl 192.168.3.89:80/query/info {"name":"AHU3 153434240000000000bby","mode":3,"state":0,"fan":0,"fanstate":0,"tempunits":0,"schedule":1,"schedulepart":1,"away":0,"spacetemp":73.0,"heattemp":67.0,"cooltemp":76.0,"cooltempmin":35.0,"cooltempmax":99.0,"heattempmin":35.00,"heattempmax":99.0,"setpointdelta":2.0,"availablemodes":0} C:\Users\apostolakisl>curl 192.168.3.127:80/query/info C:\Users\apostolakisl> CHAT GPT said this: What’s happening internally on your Venstar T5800 is likely: HTTP connection accepted Request handed to handler thread Handler tries to process route (/foobar, /query, etc.) Handler crashes / times out internally Socket closes with no response → curl shows empty reply 👉 That delay = the thermostat is attempting to process the request and failing, not ignoring it. chat gpt basically wants me to do a hard reset. it thinks the api subsystem is locked up. if that fails, do a factory reset. This is consistent with me having issues with other thermostats that somehow stopped having issues. @Guy Lavoie The SD card just needs to be between 2 and 16GB and Fat32 formatted. I use a micro SD and an adapter. You can download a tool from venstar that puts the firmware and any custom images you want onto the card.

Things did not go well. 6.0.4 to 6.0.5. Seemed to go well at first glance. But opening java ac takes forever. None of my insteon nodes populate. programs aren't running. Can't open java ac programs page, it times out and gives error. Can't open programs page from ud mobile, gives an error. Can't open eisy ui. It gets a response from eisy as evidenced by the non-secure icon showing open in the browser, then it just spins forever. I tried a reboot from an ssh session. That didn't fix anything. I also did a java update and deleted the cache and all which did not work (as expected since problems all around, not just java).

Initial testing would indicate yes. The one node populates several seconds before the other, but it does populate and previously it never populated without a query.

I have a similar issue with an Elk node. I have two garages that are monitored by Elk alarm. I set them both up to display on my favorites page. But only one of them ever populates without doing a query. The other always populates. They are identical to each other except for the specific Elk sub-node referenced. It has been like this for a very long time. If I close UD mobile and open it back up, the node is again not populated. According to google play store, I am up to date on ud mobile app. If I look at all of my Elk nodes, it seems hit or miss which ones are populated. What can I do about this?

No, you can't. But you don't need to set the on level to 0, just use the controller off button. Of course if you want it so that no matter what action you take at the controller, the scene turns off, then you would need to set on level to 0 for all devices. If it is a kpl, you can set it to non-toggle off instead. Isy used to let you propogate the settings for one controller to all of them, but they got rid of that many moons ago when they added non-insteon products. Apparently the logic broke when applying to node server devices.

I now have 3 connected Venstar thermostats. I just added a 4th, and it won't connect. This makes no sense. Two of the others also wouldn't connect, then one day out of the blue they started connecting. The 3rd unit discovered immediately. I do not understand this. I ask the thermostat to do a firmware update and it says it is already up to date. The others supposedly were also up to date. Perhaps some update is actually happening after being online for a while even though it says not? Two of the connected thermostats are t5800 with wifi key, and one is a t7850 with built in wifi. The 4th is also a t5800 with a key. All of them are connected to the Venstar skyport server without issue.

Speak for yourself. Texas time. . .