simplextech

The two do not work together like that. You should pick one system and work from that point.

I'm sure it would be and would be a lot less profitable. It takes a lot of time which equals money to develop software. Just because Apple/Google have a "family share" option that people like doesn't mean it's fair to the app developers. So the in-app purchase is the only way to circumvent the "family share" that Apple/Google built. I don't mind paying for each install (license) WHEN the app is a reasonable price. Currently @InsteonNutI think the direct + remote is silly borderline ridiculous that they are extra charges. Should be one. I don't have ELK yet and I'm not going to expose camera's via port forwarding so the ONVIF camera support is worthless to me for remote and like many (most) I use Blue Iris or Xeoma or Unifi Protect for cameras so ONVIF doesn't matter. Make the direct+remote (ISY Portal connection) a single app/purchase as they technically are the same connect method and make it a reasonable price for an app.

You can't.

E-mail sent...

In Polyglot Cloud (web browser). Refresh. It's a browser/UI thing with the nodes not being listed in the Polyglot UI. If they are showing in the ISY Admin Console then all is well.

Did you go to the controller node and click the Discover button? See if the missing node appears or not. EDIT: I just did a re-install on my Prod system and I have the 3 day/week/year nodes for the energy log which is correct.

That is odd/interesting that it didn't start overwriting the old... May want to ask support about that one.

There should be the 3 day/month/year. I'll go take a look but I didn't mess with that portion of the code but ya never know...I have seen where not all nodes get created every single time on installs. Do a Discover and see if it shows up.

Default max log size is 3MB. You can configure this from the telnet interface of the ISY. I don't let mine get large and i clear it nightly unless I'm having problems then I disable that program so I can collect and look through the logs.

Homebridge see's ISY devices... Home Assistant see's ISY devices... ISY does not see devices from either of those two....If you have a ceiling fan that Homekit is aware of then it is probably Wifi but I doubt their API is open to other integrations otherwise Home Assistant would directly support the ceiling fan and probably other systems as well.

No info/ideas/clue about HomeKit. I don't have a HomeKit setup. @EddieRockyes you will have to setup again. I'm hoping things with Polyglot change in time but because the profile changed it would have to be re-added this is unfortunately a PGC issue currently that I'm hoping gets resolved some day.

Welcome. Let me know if something else isn't working quite right.

Beta Release v0.1.36 has been pushed to the store. Because of the changes to the profile you should do a delete/install from Polyglot Cloud to ensure the nodes are updated in the ISY fully. Changes Updated profile to use direct editor and not the editor file for UOM specifications Provides text entry option instead of drop down for temperature settings Now visible/usable in programs for status

Interesting. Looking at things the only difference between the energy log nodes and the thermostat node is actually the item I was questioning... the unit measures having both. I'm questioning if that is causing it to not return a usable status because there probably isn't a usable one that the ISY knows how to handle. Hmm.. so much for a short cut on node definitions. I'll do some tweaking and testing to get this figured out.

A controller node "NuHeat" and a node for the actual thermostat device is created. Make sure in your program you're selecting the correct device. SetPoint can be set in a program. The list provides Celsius and Fahrenheit options just scroll to the temp. I think I need to change this to be a input value. Undecided as I the increments are 1 degree increments from what the thermostat accepts. This also accommodates both unit types. Hmm.. input is welcome

Polyglot Cloud version is available and live. I'm running it in my home and @EddieRockis testing it out as well. This currently and conceivably will only be available in Polyglot cloud for these reasons The API is from a cloud system. If you don't have internet then a local nodeserver won't work either so then why does it matter if the nodeserver is ran in Polyglot Cloud? The OAuth process requires a registered publicly accessible encrypted URL for user authentication and token exchange. I can't create a developer account for every single user's possible self hosted URL and I don't think most people will go through the process of registering for developer access nor will they have a SSL encrypted public facing URL they can use for the redirect. I don't know how the Ecobee works or flair. Some systems don't require a user authenticated web process and you can pass the username/password to the API directly and get a token. I'm still investigating if I can do this with NuHeat but until then it's Polyglot Cloud. I have asked and will continue to ask them for a local API. If that ever happens then a local version will be developed. I'm a small shop with little backing/support (just me so far) so nobody listens to me

There's a rate limit imposed by Amazon on sensor triggers. I think it's 30 seconds in between.

I think you can still buy the network module by itself. It really would be odd not to considering not everyone uses the ISY Portal but still use network resources.

You can't call curl directly from python. curl is a linux/unix utility. I recommend using the 'requests' python module. Here's a page on how to use it with basic auth https://2.python-requests.org/en/master/user/authentication/

@Chris Jahnsame failure with leak sensors. Here's some data for you. <?xml version="1.0" encoding="UTF-8"?> <nodeInfo> <node flag="128" nodeDefId="BinaryAlarm_ADV"> <address>4E 29 71 1</address> <name>Kitchen Leak Sensor-Dry</name> <parent type="3">1964</parent> <type>16.8.68.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>4E 29 71 1</pnode> <ELK_ID>H02</ELK_ID> <property id="ST" value="" formatted=" " uom="0" /> </node> <properties> <property id="ST" value="" formatted=" " uom="0" /> </properties> </nodeInfo> <node flag="0" nodeDefId="BinaryAlarm_ADV"> <address>4E 29 71 2</address> <name>Kitchen Leak Sensor-Wet</name> <parent type="1">4E 29 71 1</parent> <type>16.8.68.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>4E 29 71 1</pnode> <ELK_ID>H03</ELK_ID> <property id="ST" value="" formatted=" " uom="0" /> </node> <node flag="0" nodeDefId="BinaryAlarm_ADV"> <address>4E 29 71 4</address> <name>Kitchen Leak Sensor-Heartbeat</name> <parent type="1">4E 29 71 1</parent> <type>16.8.68.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>4E 29 71 1</pnode> <ELK_ID>H04</ELK_ID> <property id="ST" value="" formatted=" " uom="0" /> </node>

No they aren't compatible. The way a Pico fits into the bracket won't work with the RemoteLinc2. I've tried as I have both. If trying to hack something the piece of plastic or cut down plate to go over the gang box is the best route.

I agree with @Bumbershootusing curl or if your script is python using python request is the easiest to push a variable to ISY. PyISY is very complete and full featured but may be overkill for a simple single variable. Also there's a couple (including my own) Ambient Weather nodeservers available that provide barometric pressure information from your own local sensors.

If it were thick enough plastic to not flex when pushed against then you're creating a flat/hard surface for the mount to rest against just like a wall. So it would work but it's a lot of work to compensate for a bad mount design from SmartHome I wonder... do they make dimensional gang box covers/fillers that would cover the box and not protrude past the drywall? I've used the blank plate covers before but that adds thickness and is unappealing having the switch mount attached to that and it's then not easy to put a decorative face plate on top of that. Hmm...

The mount bracket has not "back" to it and only holds the remote in by two touch points (top/bottom) and it uses the "wall" as the backing surface for pressure when pressing the switch. Without the wall behind the "mount" when you push the remote it wiggles about is horrible and if pressed too hard will pop through the mount into the gang box....

This is a complaint I have with the bracket. I wish SmartHome or someone would 3d print a nice electrical box mount for the RemoteLinc2. that would be great! This is something I really love about the Lutron Pico's and their mounting options.