mapeter

Will it be a consolidated desktop version that can perform the configuration functions of the admin console, PG3, and the portal? I am seeing more and more of these configuration options being added to UD Mobile, which is great. However, an unified desktop configuration UI would also be wonderful.

I think I am on a very old version of PG3. I do have :3000 in my URL. I have started the Update Packages again. Will give it time to run and see what happens. I appreciate everyone's help.

I am going to have to do some more research as my Polisy appears to be really messed up. From the AC I clicked on Upgrade Packages. There is no "Restart Polyglot 3" open in my version of the System menu in PG3. I have clicked on all the Reboot and and Restart menu options as well as clicked on the Reboot option in the AC. It does not appear to be restarting/rebooting. I attempted to SSH into the Polisy, but get the error kex_exchange_identification: Connection closed by remote host

I am finally setting up my first node server on PG3 (version 3.0.36). I "purchased" a trial WirelessTag license and when I attempt to install it into slot 2, the green "installing..." dialog appears. When it finishes up and I return to the dashboard, no node servers are showing up. Below is what I am seeing in the error log. Any thoughts on what is going wrong? 11/9/2022, 15:10:05 [pg3] debug: ########## {"docs":"https://github.com/UniversalDevicesInc-PG3/udi-wirelesstag-poly/blob/master/README.md","longPoll":"600","executable":"wirelesstags-poly.py","status":"active","oauth":"undefined","url":"http://pg3store.isy.io/v2/node servers/production/WirelessTag.zip","name":"WirelessTag","language":"python3","developer":"jimsearle@gmail.com","ip_added":"70.181.79.77","nsInfoPoll":"0","profile_version":"3.1.3","logLevel":"WARNING","ts_added":"1641350502","shortPoll":"60","author":"Jimbo.Automates","version":"3.1.7","discover":false,"prem":true,"nsdata":"{\n \"client_id\": \"REMOVED\",\n \"client_secret\": \"REMOVED\"\n}\n","desc":"CAO Gadgets Wireless Sensor Tags www.wirelesstag.net","authorize":false,"install":"install.sh","purchaseOptions":[{"isTrial":true,"recurringPeriod":"month","recurring":"1","price":0},{"price":20,"isPerpetual":true}],"branch":"","uuid":"REMOVED","ts_updated":"1664077839","price":20,"modified":"9/24/2022 22:50","profileNum":"2","nsid":"7ad25b20-1c13-45ca-9a94-85bd5063815d","expires":1670619543000} 11/9/2022, 15:10:05 [pg3] info: [00:0d:b9:53:dc:04_2] :: Creating Node server 'WirelessTag' 11/9/2022, 15:10:05 [pg3] warn: [00:0d:b9:53:dc:04-2] :: Node server folder exists, removing... /var/polyglot/pg3/ns/00:0d:b9:53:dc:04_2 11/9/2022, 15:10:08 [pg3] error: unhandledRejection REPORT THIS!: Error: Request failed with status code 404 at createError (/var/polyglot/node_modules/axios/lib/core/createError.js:16:15) at settle (/var/polyglot/node_modules/axios/lib/core/settle.js:17:12) at RedirectableRequest.handleResponse (/var/polyglot/node_modules/axios/lib/adapters/http.js:238:9) at RedirectableRequest.emit (node:events:390:28) at RedirectableRequest._processResponse (/var/polyglot/node_modules/follow-redirects/index.js:425:10) at ClientRequest.RedirectableRequest._onNativeResponse (/var/polyglot/node_modules/follow-redirects/index.js:57:10) at Object.onceWrapper (node:events:510:26) at ClientRequest.emit (node:events:390:28) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:623:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17) at TLSSocket.socketOnData (node:_http_client:487:22) at TLSSocket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at TLSSocket.Readable.push (node:internal/streams/readable:234:10) at TLSWrap.onStreamRead (node:internal/stream_base_commons:199:23)

Hi @matapan - I did a little testing on this. It appears that a 404 error indicates that the parameter value is not valid for the device. You were attempting to query parameter #2. Try to query it in the admin console. I suspect you will get an error. As an example: Parameter 151 is valid for the device I tested: http://x.x.x.x/rest/zwave/node/ZW018_1/config/query/151 returns: <config paramNum="151" size="2" value="50"/> However, parameter 1 is not valid for teh device I tested: http://x.x.x.x/rest/zwave/node/ZW018_1/config/query/1 returns: <RestResponse succeeded="false"> <status>404</status> </RestResponse>

Here is another article: https://arstechnica.com/gadgets/2022/04/shameful-insteon-looks-dead-just-like-its-users-smart-homes/

I purchased a Keene IR Anywhere a few years ago and wrote a proof of concept NodeJS program to fire REST commands to the ISY when it received certain IR commands. When I have some free time I think I am going to use the NodeJS Node Server template and see if I can come up with something that works.

Appreciate the responses and ideas.

I have an ISY994i/IR Pro as well as a Polisy Pro. I use the ISY IR support to trigger scenes and programs. When the time comes to migrate to ISY on Polisy, what are people planning to do for IR support? (I suspect it is a small population of users.)

Oops... Sorry. I was reading too fast and not paying total attention Thanks for sharing as it will be cool to try. Looks like Amazon is now providing Smarthome Status Announcements. Hopefully we will see this integrated into the ISY Portal sometime soon.

Instead of "Raw Text", try a mode of "C Escaped". That is what I had to use to POST requests to Pushover.

Currently running on 2.2.8 and have the option to upgrade to 2.2.11. It goes through all of the motions when I click on the upgrade button, but it never actually upgrades. End up on 2.2.8. Any thoughts on what is going wrong?

I have been using Insteon since the beginning and have a house full of it. Despite that, I have just added a couple more to clean up some communication issues. I don't know if I have switches that are starting to fail and not relaying the signal; or if the use of more LED lights is putting more noise on the line. Regardless of the reason, hiding the wall warts behind furniture and the like is keeping the "It is not working again!" comments away At least the new version of the devices are much smaller than the old ones.

I am using FIBARO RGBW controllers for my LED strips. Configures as a native z-wave device to the ISY, so a node server is not needed. I have a button programmed on my KeypadLinc to turn it on and off.

My first experience programming was on a Data General Nova 800 with a whopping 16K of core memory. Toggled in the bootstrap from the front panel and then loaded the paper tape.

I came across the following post regarding Semantic Extensions on Amazon's developer site. It is dated September 25. Of great interest is the following: Enable More Natural Control with Open, Close, Raise, and Lower Semantic Extensions We introduced toggle, range, and mode, each with their own general voice model, to give developers building blocks to easily model a wide range of device functionality. Now we are adding semantic extensions (coming soon) that give you the ability to map these building blocks to specific voice models that better fit your device’s functionality. The first semantic extensions (coming soon) enable you to support utterances that use “open”, “close,” “raise,” and “lower” commands such as “Alexa, open the window” and “Alexa, lower the movie screen”. These new semantic extensions (coming soon) can be used to deliver natural control of devices such as projector screens, windows, water valves, closets, drawers, garage doors, gates, curtains, shades, blinds, awnings, and more. Smart shades from Lutron, Schellenberg and IKEA will be Alexa-enabled, designed to use the open, close, raise and lower semantic extensions (coming soon). This enables them to support phrases such as “Alexa, open the shades”, and “Alexa, raise the shades halfway”. Garage door openers from Nexx and beam Home will be Alexa-enabled, designed using the mode controller, along with open and close semantic extensions (coming soon) to support phrases such as “Alexa, close the garage door”. @bmercier - Any thoughts about if/when we will get this support for our spokens?

@Michel Kohanim - Will there be an option to have Zigbee along with INSTEON, Z-Wave and Bluetooth in the Polisy Pro?

Thanks @jca001! I did not see that command in the dropdown at first.

Are there any plans to allow an ISY program to set a z-wave configuration parameter rather than having an ISY program call a network resource to fire a REST request back to the ISY to set the configuration parameter?

I haven't had a chance to test it yet, but it looks like echo-centric smarthome groups has arrived...

Does anyone have a clever way to simplify the if statement below? I would love it if a scene name containing the devices could be specified, then if any device in the scene is switched off, the program would be triggered. Listing out all of the devices like I have below means that I have to remember to modify the program whenever the associated scene is updated. Thanks! --Andy If Control 'Devices / Foyer / Front Lights FOY_KPL' is switched Off Or Control 'Devices / Master Bathroom / Front Light Slave MBA_KPL2' is switched Off Or Control 'Devices / Mud Room / Front Lts Slave MUD_KPL' is switched Off Or Control 'Devices / Garage / Front Outside Lights Slave' is switched Off Or Control 'Devices / Basement / Front Lights Slave BAS_KPL' is switched Off Then -- some action to take -- Else - No Actions - (To add one, press 'Action')

You can create a program in the ISY whose "Then" branch activates the scene that dims the lights and then activates the network resource that shoots the command to the shades. Use the ISY portal to associate a spoken to the new program. The wiki has more information.

Thanks Michel, that worked. Also, thanks for the heads up on the potential cross-domain issues with JavaScript.

Is there a way to access the web pages from the ISY's Network Module web server via the portal? Similar in the way that udajax.htm is available via the portal, I would like to get access to /USER/WEB/INDEX.HTM.

A little fun for the day... Be sure to enable the volume in the video. https://t.co/Wriy531ALr