bpwwer

I just submitted version 1.0.8 of the plug-in to the store. Go to the Node Server Store and click the Refresh Store button. Select the Caseta node server Click "Install" for the trial (I'm assuming you're running the trial) You should then have the option to re-install to the same slot, click on that and the node server will install the new version and restart the node server. The button press events for the configurable Pico buttons should now work.

I've been able to reproduce the issue and I'm working on a fix.

I suspect that's because the fail/reconnect happens within a couple of seconds. You may have said earlier, but are you running PG3 or PG3x? What does the node server log show at those times for a couple of them?

You should get a node created for each button on the Pico which it looks like you do from what you posted. You have Study_Pico - A, Study_Pico - B, Study_Pico - C, and Study_Pico - D right? Each of those should have an option to set what the button does like below. By default I believe button A sends an ON command, button B sends a BRIGHT command, button C sends a DIM command and button D sends an OFF command. But you can configure each button independently. For example with A configured to send ON and B configured to send OFF you could put these in a scene with an Insteon lamplinc and button A would then turn the lamplinc on and button B would turn it off. What you can't do is use a single button as a toggle (well maybe you can with a set of programs). Speaking of programs, you should also be able to trigger programs on the button press. Like below. Pico buttons are somewhat limited in that the only thing the bridge sends to the node server is the button pressed (and button released) events. They don't have any status. But this should be enough to do what you want. To summarize you have two options with Pico buttons 1. Use them as a scene controller where they send a command to the responders in the scene. 2. Use the button press event as a program trigger. If it isn't working as I described above, set the node server log level to debug, do the operation you're trying to make work, download the log package for the node server and PM it to me.

@Sparks PG3x uses a service on the system called UDX to do the authentication. That service is rejecting PG3x's request. That is not something that should be happening. So please to submit a ticket. There can be issues when that service is updated as part of a upgrade where it won't work properly until the system is rebooted, but as you've already tried that, this seems unrelated.

All of them or only specific node servers? What node servers do you have installed? My Roku node server seemed to do this. What's happening is that the mqtt connection drops, the node server then re-tries and successfully reconnects. So you see a fail notification and a connect notification. I was seeing this on only one of about a dozen node servers installed. I don't know why that one specific node server was having issues with the mqtt connection.

Critical - not used. Error - something failed that isn't expected to normally fail. Warning - something that may need to be reviewed. Info - messages that track execution. debug - more verbose execution tracking. db operations - log all database operations.

Looks like PG3x is not running. If PG3x was running it would connect fairly quickly, but then take a while to migrate node servers. the "Upgrade" process doesn't always result in things starting backup properly so a full system reboot or even power cycle is needed to get everything properly restarted. So if you've been waiting for 15 or 30 minutes with no change, power cycle.

The package has been updated. I believe all you need to do is run the "Upgrade Packages" again.

The package is missing a file that prevents PG3 from starting. We're working to get it updated.

Have you restarted ST-Inventory? Or you may just be able to do a query on the node. I believe what happened is that when you installed Ring, you also had to enable remote access. When remote access was enabled it restarted the IoX. When IoX restarts, it doesn't remember any of the node server values. ST-Inventory will only send the counts to IoX when they change and most of those values rarely change. It doesn't know that the IoX was restarted and that it needs to send everything again.

Hello all, We are very happy to introduce PG3x v3.1.27 for eisy and Polisy. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure and enable features based on remote access. Polisy users may update their systems to use PG3x if they want access to the new features. PG3 will continue to get updates for the foreseeable future. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you should restart/reboot the eisy. Do this from the Admin Console, Configuration, Reboot. Once PG3x has restarted, reload /refresh the browser page. Changelog for 3.1.27 - Fix developer API queries. - Add install option to Purchases page and change "(Re)Install" to "Update". - Base call to PG3x cloudlink protocol on UI protocol. - Send notification to UD Mobile for NS connection status - Finish notification support - Add support for incoming POST request from IoX (to handle more complex notifications) - Add clientConnected message API for remote access via Portal. - Remove portal login button from sales report - Clean up login/logout of portal code in html templates. - rework purchase options to provide developers with more control over pricing. - Limit developer sales report to 18 months. - Sort developer sales entries by date - Handle free/trial in developer sales report if no paid options exist. - Update developer sales report to handle changes to API. - rework purchase options to provide developers with more control over pricing. - Log pip output when installing node server. - Add support for push notifications to UD Mobile

Hello Everyone, This is the support thread for PG3x v3.1.27

Hello all, We are very happy to introduce PG3 v3.1.21 with bug fixes and new features, see changelog below. To upgrade PG3: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you will need to restart PG3. From PG3 select System-> Restart Polyglot 3. Once PG3 has restarted, reload /refresh the browser page. Note that in some cases you may be asked to reboot after the upgrade is complete. Changelog for 3.1.21 - Fix developer API queries. - Add install option to Purchases page and change "(Re)Install" to "Update". - Base call to PG3 cloudlink protocol on UI protocol. - Finish notification support - Add support for incoming POST request from IoX (to handle more complex notifications) - Remove log messages for access_token authentication not needed. - Remove debug output from sale report request. - Remove portal login button from sales report - Clean up login/logout of portal code in html templates. - Portal oauth2 re-write. UI should now only ask for portal credentials once. - Limit developer sales report to 18 months. - Sort developer sales entries by date - Handle free/trial in developer sales report if no paid options exist. - Update developer sales report to handle changes to API. - rework purchase options to provide developers with more control over pricing. - Decrease maximum log size and compress old log files. - Add support for push notifications to UD Mobile (for PG3 an Node Servers) - Fix bug in git clone when no branch is specified. - Change text on how to update node server. - Change ISY to IoX in UI

Hello Everyone, This is the support thread for PG3 v3.1.21

I took a look at the RoomieRemote. It doesn't seem all that much different to me. Mostly there is just a difference in focus. eisy/Polisy are more focused on home automation and less on remote control. RoomieRemote is more focused on media remote control. RoomieRemote treats the ISY as a lighting controller and that makes sense. The support things like ecoBee thermostats directly, why would they want to also support an ISY node server for ecoBee thermostats? Doesn't make sense to apply any resources to that. Yes, there are devices that UDI supports via node servers that RoomieRemote doesn't and there are devices that RoomieRemote supports that UDI doesn't. That has more to do with each team applying resources to the support devices that fit with their main focus.

@TRI0N It can be hard to figure out what someone did/didn't do from forum posts so a big thanks for posting the screen shots. With the next release of PG3(x) the purchases page button will display either "Update" or "Install". Update when the node server is installed and Install when it is not. I'm hoping that clears up some of the confusion the exising (re-install) button causes.

What would it take to make UD Mobile compare with Roomie Remote? I.e. can you enumerate specific features/capabilities that UD Mobile doesn't have that Roomie Remote does? Here on this forum, you have the ability to influence UD Mobile development but this forum is not the right place to get Roomie Remote to better support eisy/Polisy.

Node servers have been available for years (4, 5, more?). There were discussions with third party developers and as @Javi said, it is possible to support them. Most developers of third party integrations chose not to. My reasoning was something like this: A HomeSeer thermostat plug-in sells for about $29. There are 4 or 5 different node servers for different thermostats. How much would I have to change for an ISY plug-in that supported 5+ different thermostats to make it worth the effort to provide support for them all? Now try to scale that up to support the 100+ different node servers. I'd have to charge over $3000 for my plug-in and nobody's going to pay that.

If it's not on the dashboard then you haven't installed it. Go to the Node Server Store, select Ring and select Install.

I believe ST-Inventory always logs that error if you don't have any network resources defined. It's not fatal and would have nothing to do with the Ring node server.

Pretty much no third party product that integrates with UDI has ever supported node server nodes. I've written one such product (HomeSeer ISY plug-in) and I don't support node server nodes in that either. While it is possible to do so, it is a lot of work because node server nodes can't really be handled in a common, generic way like Insteon or Z-wave. Each node server creates unique nodes which means unique code on the third party side for each node server. There are over 100 node servers so the effort is high and the payback is currently low.

The authenticate button is on the node server details page.

If you selected re-install to the existing slot, it does not touch the custom parameters so any that were previously entered will remain.** If you delete the node server and then install, it will delete the custom parameters and you will have to re-enter them. ** This is somewhat dependent on the node server as it could clear them all at startup if that was part of it's startup process.

@Michaelv Yes, the latest ISY plugin for HomeSeer does work with the latest eisy and Polisy firmware.