simplextech

I don't use port forwarding for anything. If I need remote access I use a tunnel/vpn/service for the access. ISY Portal serves the purpose for remote access and direct access for me to the ISY. VPN for anything else that I may need.

Hah what mirror?

I normally use Geofency but just to see I installed Locative on my iPhone and set it up. I'm using FW 5.0.16 and I run the Occupancy nodeserver in the portal (NOT Occupancy v2). Using the In/Out links provided it works perfectly. No issues for me with Locative or with Geofency.

I fully understand the view. The only other "smart" floor thermostat I'm aware of is from Sinope. The problem there is that it's Zigbee and won't work with the ISY. Are you specifically looking for a "floor" thermostat or a line-voltage thermostat for baseboard heating? I have several of the StelPro Ki Z-Wave thermostat's for my baseboard heating and they work great and are 100% local being Z-wave.

Control of the thermostat is cloud based. Nuheat (the vendor) provides a internet accessible API to control the thermostat. This is how it can be integrated with other systems. The thermostat itself is fully functional, controllable AND programmable locally. You can create/program schedules on the thermostat just like any normal programmable thermostat and those schedules will run regardless of internet access. The Thermostat is Wifi connected providing the options to use the mobile apps or web interface or integration with other systems but it is NOT required. All remote control of the thermostat is done via their API which is through the internet. Manual control is still available. Because their API is only available via the internet and requires an OAuth2 setup this nodeserver will only be available in the Polyglot Cloud system and will not (currently) work in a local Polyglot install.

I have plans for a nodeserver for the NuHeat Signature thermostat. Amazon link is below. There's only one model of the Signature series. This is a cloud based API so it will run in Polyglot Cloud. The thermostat supports floor heating systems and baseboard heating https://www.amazon.com/Nuheat-SIGNATURE-Programmable-Dual-Voltage-Touchscreen/dp/B00KHA6MEG/ref=sr_1_2?keywords=nuheat+signature&qid=1573166997&sr=8-2 That link is the first one to load from Amazon and the seller is not endorsed or related to anything I do however they have better pricing than even I can provide and if you have Prime it's free shipping.

This has been idle for a while but i wanted to drop the note it is not forgotten. Things have been very hectic and busy unfortunately.

Good to know that it is 4 groups of X number of bulbs and not 4 bulbs max per hub.... that would be horrible! In browsing I did see the 8 channel remote and wall remote which looks interesting but I didn't see a corresponding "Wifi box" controller for them. I wonder if a new controller is necessary or if there was a firmware update to handle more channels?

My understanding and reading from other forums and integrations is that the MiLight hub supports 4 zones. However you can have as many bulbs in each zone as you want. Are you saying you can only have 4 bulbs period?

That's interesting... same slot on my Polisy ... slot 2

Yeah I'm used to seeing the unmanaged from other Polyglot instances and PG Cloud. I have several polyglot installs running so that's normal. However the SolarEdge and DarkSky I have never installed myself so I have no idea where they came from.

Same update error: Platform not recognized - freebsd I have nodeservers listed that I've never installed. They are marked as "Unmanaged". My local polyglot install pointed at this ISY does not list those nodeservers though. So are are they coming from? DarkSky SolarEdge dhclient is prepending the DNS server entries. probably ok for most people. This can be modified to change 'prepend' to 'append' to put internal DNS first in the resolv.conf list. Test install of nodeserver worked. No errors for me with MQTT client or Ambient Weather

A node for each button should be created. Were they? Each button uses the scene controller command class and has options for how many times it was pressed or pressed and held. Or at least it should. The Button from Fibaro includes and works and it uses the same scene controller command class so I would think the key fob controller "should" work. I've noticed with battery devices they don't always create all of the nodes during inclusion and sometimes it takes a z-wave synchronize to create all of the nodes and some button presses.

Using Network Resources Webserver and exec the scripts as cgi scripts Mini webserver (python, node.js, perl) to run your desired code from request end point can provide optional parameters Node-RED workflow probably the most customizable and perhaps easiest Custom polyglot that would exec scripts in a known directory is also feasible.

To add to this Ring aka Amazon are not giving out API key's or developer access easily. I was completely unable to get even a e-mail reply from multiple inquiries for developer access.

AmbientWeather is working now. BTW there are some major changes planned for this NS around node layout. Just an FYI.

That's a problem on my end as I didn't design AmbientWeather to run in PGC as it was an very early NS development. I'll have to fix it.

I've tested against a couple different nodeservers and none of them will install. Not sure what is going on with PGC.

@zxplod I guess I'm curious about what devices or innovation you're looking to or comparing against? I have plenty of Z-Wave experience and am fairly newish to Insteon but so far it's a different ball game in terms of functionality and consistency. So what is it that you're "wanting" exactly?

Something to note about this "issue". 1. This is a powered device 2. This is Z-Wave Powered devices DO NOT send any pings to the controller like a battery powered device. A powered device is expected to be well, powered and available all of the time. The historical process with Z-Wave devices was to use polling to determine device status. This was because of the Lutron patent that prevented widespread use of Instant Status for Z-Wave devices. Many controllers did implement a polling service or a routine to periodically check for devices that did not provide instant status. HomeSeer uses polling as does SmartThings and Vera and many other controllers. This is a legacy thing that coupled with dozens of Z-Wave devices will cripple a system very quickly due to the amount of traffic. Now we fast forward several years into Z-Wave Plus and the expiration of the Lutron patent. Many (not all) newer Z-Wave Plus devices support Instant Status. It's actually rare to find one that doesn't but they do exist and should not be labeled "Plus" but they are. None the less this Instant Status removed the need for the controller to poll the devices to get their status. However this polling in the past turned into a "Heartbeat" type use for many and I think yourself included. It was never intended to be a heartbeat and check if a device was present or alive. It was a work around for getting status on/off so that the controller would automate the environment correctly. I have many controllers in use and testing and have used many for my own home. None of them with polling disabled will "alert" you that a powered device is present or not. This is always implemented from a user stand point usually through polling or other scripts to periodically poll the device to verify it's alive. ISY ships with a 3AM program to perform this on a daily basis. Once you get more than a few dozen devices especially sensors (battery) devices this polling because unbearably slow and no longer has any benefit. If you are thinking this is a limitation or weakness in the ISY then I think you should check your HomeSeer install and turn off polling and see if it notifies you that the devices is or is not available. Without polling HS doesn't know anything more than ISY about a powered device until the device sends an update or the controller sends a command.

Rule of thumb... if you buy cheap you get cheap.... LiFX and Hue are the best smart bulbs on the market currently that have good ISY support through Polyglot. Newer Hue bulbs have good color and do have proper blue/green color display/contrast. The LIFX standard A19 bulbs are still brighter and have great color. Next up would be Sengeled but they are not supported by ISY currently. In general I dislike Wifi bulbs because of the delay from going out to the cloud and back to turn on a light. This is just stupid. LIFX has a local API which avoids this so I like LIFX. Otherwise Zigbee specifically ZLL is the "king" of smart bulbs. Bottom line go with Hue or LiFX they are both great bulbs/ecosystems.

I should have guessed it was either HVAC or Weather related for the quantity

Sounds comprehensive I was just struck by the number of programs vs the small number of devices you listed. Perhaps another thread of "interesting" programs would be more appropriate.

Lots of variables and programs. It would be interesting to know what all is going on if for nothing else but to give me some ideas I may not have thought of

No not within programs.