MWareman

What should we put as the variable number when we are not linking it to a variable? Will there be a future possibility to name the node (rather than just a number?) Thank you! Sent from my ONEPLUS A5000 using Tapatalk

Thank you all - good to know! Edit: Would this all be the same for virtual devices NOT tied to an ISY Variable? Basically - the Poly would hold it's own state for the variable (maybe using sqlite or the mongo that's part of Polyglot). This way - these devices are not subject to polling - and when the state is updated on ISY the Poly will see the change immediately?

I suspect you could establish a websocket subscription to ISY and this would eliminate polling. This is what I thought the Polyglot library does on behalf of running polys.

I’ve got to ask - why polling ISY at all? Doesn’t ISY send the status real time for the Poly to see? I understand polling is used generally when the poly has to pull data from third party APIs... My temperature probes temperature can change fairly quickly (I have sensors in my HVAC system) so I’d rather get changes pushed real time when they change than have to have the poly poll them.

Thank you! Sent from my ONEPLUS A5000 using Tapatalk

I must be confused. If the nodeserver is sending the value to a variable to store the value sent to it, but I trigger a program on the same variable changing and sending it’s value to the nodeserver - wouldn’t that create an infinite loop?

Agreed. There really shouldn't be a need to tie a virtual device to a variable in ISY. It could be persisted in Polyglot within the Mongodb. For me - this would mean no reliance on multiple variables (one for the poly to store it's value in - and a separate one for Brultech to send it's value to) - and two programs to send the data (one to divide the incoming value by 10 and store it in a temp variable - then to send it to the poly). Adding more UOM options would likely be more viable at that point. I'm interested in options to send UOMs of 1,21,22,23,30,33,36,71,72 and 73 - though others may be useful to others in this regard. General just does not look as good as using the correct UOM to represent a value. Thank you!

The external device is a Brultech Dashbox - I cannot change it's URL. It sets the variable via the ISY REST API. Why is it setting the variable by a program sends it's value to the poly - but setting the value via REST API does not?

So, I need two variables? The external device sets a state variable - and I then have to have a program to respond to that and set a second variable to populate the poly? I’ll probably run out of variable space doing that. Is it not possible to have it directly monitor the current value since that’s functionality provided in the Polyglot library?

If I have an external device setting a variable via the REST API - how can I set this poly up to interpret the variable as a temperature and display it? In my case - variables 141 and 142 are set via the ISY API - and constantly updated. I have set this up: I see the nodes - but the value seems to stay at zero: State variables 141 and 142 are as follows: 72.5 degrees and 60.5 degrees. Am I missing the intent of the poly?

On the mac, it downloaded a directory called Insteon_5 Yep - MACs will automatically expand .zip files when you download them. You need to use the .zip file without it being extracted! There is a setting somewhere to stop macs from doing this I think....

Fantastic! Thank you for this. Have not (yet) got this going but in my case I have my Brultech GEM sending temp data to an ISY state variable from some one wire probes. I suspect this will work fine with the temperature node. Can I ask that we add other node types? With the GEM sending data I’d like to see power related nodes (watts, amps, voltage). Is this possible? Thank you!

Thanks to this post, I checked my PGC account and saw the same thing. My Ring poly needed reauthorizing even though it’s been working for weeks. I wonder what happened.

Just know that only on or off is supported. Direct Dim commands are not supported by Insteon scenes (and therefore cannot be called via Google Home or Alexa for that matter)

I have a dpdt relay connected to my Doorbell with a 24vac coil powered by the doorbell transformer. One pole connects to the chime, the other to my Elk (on a non-alarm input). This could easily be an iolinc. This triggers an ISY program that calls a network resource. The URL is on a Rpi and it runs a .php script. That PHP scrips grabs an image from a Foscam I have looking out of my sidelight - and calls the Pushover API to send my phone the image. It works fairly well overall.

If the ‘Room’ assigned to a device in the ISY Portal matches a ‘Room’ available in Google Home - then you won’t have to do this. It will happen automagically for each device. If the room name does not have a match, it will be unassigned in Google Home and you will have to manually assign it. At least it did the last few times I relinked.

FYI - Mobilinc Connect requires a license fee as well. Both it and UDIs Portal are subscription based. Like UDI - it’s to offset the cost of running the cloud resources necessary for the integration to Google Home and Alexa work. You can avoid fees by using free services (like ifttt) but I know that can be significant processing delays thru services like that. It’s also much more effort to setup. In my opinion, the cost of admission is well worth it.

I haven’t. Mobile, I use Agave which uses a websocket subscription - and this can be proxied. Otherwise, I use ISY Portal - and when remote I connect the Admin Console via that. Michael.

All tests matched your steps - so if this confirms 1.1.3 then I'm good. Hopefully the PGC version display bug can be fixed soon. Michael.

Just to be clear, the images are taken from the git repository. How can I check the actual version installed as it reports in the UI as 1.1.0? Michael.

Interesting - package.json lists version 1.1.3: https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/package.json server.json (https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/server.json) contains version 1.,1.3 and profile_version 1.1.0: Is this just a display bug in PGC? Michael.

On start: logBucket: 'pgc-prod-logbucket-[REDACTED_DATA]', url: 'https://github.com/UniversalDevicesInc/ring-nodeserver.git', isyPassword: '[REDACTED_DATA]', development: false, language: 'node', userId: '[REDACTED_DATA]', 'https://[REDACTED_DATA].execute-api.us-east-1.amazonaws.com/prod/api/sys/nsgetioturl?params=[REDACTED_DATA]', timeAdded: 1561760405240, oauth: '<oAuth config>', isyVersion: '5.0.15', longPoll: 120, name: 'Ring', pgUrl: shortPoll: 60, timeStarted: 0, version: '1.1.0', id: '00:21:b9:00:f0:9c', netInfo: nodes: '<nodes>', publicIp: '3.89.244.35' }, { publicPort: 30492, { oauth: customData: httpsIngress: 'https://pgc-ns-ingress.isy.io/ns/[REDACTED_DATA]/', '[REDACTED_DATA]', created_at: 1579398192, { access_token: token_type: 'Bearer', '[REDACTED_DATA]', refresh_token: This was after receiving the code from Git. Clearly - it's identifying as version 1.1.0. And: After restarting it and it came back up - still 1.1.0: Michael.

You are still applying the spoken to a scene - and scenes still cannot be set to anything other than ‘On’ or ‘Off’. Remove the spoken from the scene and apply it to the light itself. Then write a program to trigger of the status of the light and turn the kpl button on if the light is >0 or off otherwise.

I'm seeing the same thing. The usual stop/start does not bring in the new version. @bmercier ?

@Michel Kohanim has found and fixed the issue I was having with udx - and my beeping has stopped and I can now access Polisy's settings screen. In my case - I had a purchased SSL certificate - it's private key is 4096 bits. The udx binary was not expecting that - causing it to throw an error on start. 4096 bit keys are now being properly accommodated. This is resolved in udx version v1.0.26_8. Thank you! Michael.