markv58

I managed to get Ecobee into HA by adding to Home Kit then deleting it from HK, then HA saw it and integrated it. I have an area with a sensor that needs to be monitored so a program can do its thing and that is back online.

Did you notice that an update was pushed to the thermostat? I've done some poking around and it seems to me, I could be wrong, that Ecobee may be kicking us out like Nest did a while back. I've tried to add Ecobee to Home Assistant and that isn't working out either. The API has probably changed and I found a notice that Ecobee is not allowing any more outside things. Hope I'm wrong about this because the node server has been fairly important to my programming.

My UniFi APs updated at 3am, ISY is plugged into a Linksys router and has no portal connection either. I can connect to ISY through a Command Fusion app from the www and everything is working there. Seems like a portal problem.

Probably, got very busy with other projects. The "energy" part would be a separate ns because of the complexity. Planning to setup Brultech when time permits.

@gzahar @hart2hart The id is not linked to the variable, it was in the beginning but the nodeserver evolved. After much thought and feedback I decided to just have a number as the id rather than a proper name, which you can choose in the admin console and rename any time you want.

The virtual switch is its own variable, on or off. You can link it to a variable with a program if you want but that seems redundant. A vs can be queried or used in a program same as a variable. I put them in scenes so I can query whether a scene is on or off and use them for a dozen other things as is.

Pushed an update, v1.0.15, should fix the problem on Polisy. Does not seem to effect RPi installs.

For myself, not having an irrigation system and only wanting to take care of the ornamentals, I chose to go the LinkTap direction. There is already a nodeserver for that.

Short answer, yes. Longer answer, you can use the Pi GPIO to trigger a relay. You could write a nodeserver to do that using the ISY programs. Exactly what would be needed as an intermediary so as not to burn up the Pi would need research. I did this to control a garage door. Here is the link to that GitHub: https://github.com/markv58/UDI-GarageDoorPi

Use a program to update the generic: If <something> is not <generic> Then <generic> is <something> Just to check, did you save changes after deleting the custom config param?

@DennisC The Generic is for any value 0 - 100 so it would be fine for humidity. When you delete a node from the nodeserver nodes page it should be removed from ISY too, make sure to delete the custom config page entry or it will reappear in ISY on a nodeserver re-start.

@tmorse305 Once you get that straightened out you should be ok. You probably need to update the ip of the nodeservers on the ISY side.

@tmorse305 Well that is odd. Do other ns work on the polyglot? Did the polyglot ip change?

Update the new ISY address on the Virtual custom config page, save then restart.

@JBanaszak That can happen on rare occasion. The nodeserver needs to be restarted but can be difficult to reset. Watching the log, hit the restart button and then immediately hit the stop button several times until the ns stops. Hit start and if the error is cleared you should have a normal log. If you get the connected then unexpected disconnect message repeatedly try again.