gzahar

Download the FLIRC application software (depending on the OS you will use) from FLIRC (under downloads at end of page): https://flirc.tv/products/flirc-usb-receiver?variant=43513067569384 Plug FLIRC into computer (PC/Mac/Linux) and RESTORE the device using the downloaded application s/w above and the 'ISY my_flirc_config.fcfg' file from the forum. Then move FLIRC device to eISYIR node server platform (eisy/Polisy).

In the UD Mobile node, there is a selection box for content. It shows my first 16 defined custom notifications. Did you intentionally limit it to 16 (coincidentally) or it is stopping at the fist gap in ID numbering (after 16 my next ID is 21).

Not sure about the error, but make sure PG2 node server is stopped. The EVL interface can only have one (TPI) client interface logged in at a time.

Here is the code. Not sure what steps are involved in adding it to Polisy once you make changes. https://github.com/exking/udi-mqtt-pg3

I am running the IR node server on PG3. PG3x isn’t required. There are slightly different install instructions for PG3 vs PG3x.

I see the same thing. Once I go to the custom notification tab and back to programs they show correctly until I restart AC. UDI is looking into it.

Can you add an API to PG3(x) that allows triggering from a network resource? You can even include credentials in a NR.

I don’t think you have to have IoX in charge of deciding when a node server needs to restart. And by that, I mean hard coding the logic into IoX if that is what you are suggesting. Letting the user issue a restart command based on his own criteria/program is preferable (for me). Just because you can’t catch every failure for a node server doesn’t mean monitoring some aspects isn’t worthwhile. Using connection status and heart beats is a good start. On some node servers I am able to monitor the status of certain nodes and tell when it has stopped working also. Given there is a restart command that can be issued manually, I would think this is relatively simple to implement remotely from a development standpoint? I get this gives people plenty of rope to hurt themselves and in turn probably increases support tickets. Lastly, does restarting the node server remove the relevant logs needed for debug? If not, I don’t see why this has to be either/or. Restart automatically and then send logs to developer later.

I am totally in @MrBill ‘s camp. Especially when we have to manually deal with broken node servers when an unplanned reboot/restart forces it to update. [emoji41]

True, but a lot of times, the end user has little or no control over fixing the underlying problem. This would be a great second step to keep the user up and running until the problem is identified and resolved. I understand this is not ideal and know the reasons some would not want to do this. But in my OPINION, keeping the system working for the end user is more important.

You need the beta s/w. Look for the TestFlight link in the current release notes for UD Mobile.

I am seeing a similar issue with the notifications displaying in programs incorrectly. In my case, if I go to the Configuration tab for the custom notifications and back to programs, they display correctly.

Several upgrade / power cycles of Polisy seemed to do the trick. Now working.

Why don't you put them all in a scene and turn the scene off.

The Shelly relays have a switch input (that can be configured to be detached from the output relay, similar to an Insteon 2450 IOLinc). Any chance of adding the status of this input to the node server?

Thanks. And you are running V 2.0.0 of the node server?

If 11PM Then Turn off lights wait 5 seconds Turn off lights wait 5 seconds Turn off lights ....

PG3 (Polisy) Edit: I see now that you submitted the updates and not Bob. If you are talking about the changes 3 days ago, that is what broke it for me. Was working before using the desktop workaround.

I see you just made some changes to the authentication process of this node server. After updating to the new version, I am getting "Not authenticated or invalid authentication". The "Authenticate" button, takes me through Google approval process, but still get blue banner noted above after returning and restarting node server. Is this the expected authentication process or is the desktop workaround still needed (those detailed instructions are now gone).

I had a ZSE40 doing the same thing. Based on another post, I was going to try writing changes right after inserting the battery (apparently they are awake for around 10 seconds after power up), but before I put the battery back in I noticed the 1011 icons had cleared. I think opening the case/tamper alert woke it up.

The only extra processing it did, was create a log entry of the fact it didn’t need to do anything more (showing that it ran else). It will always have to see if the input conditions are true or not every time the lamp status changes. And the minor overhead of logging that it was false is very helpful for debugging.

You might try reposting in a different section of forum. Try Coffee Shop or IoX support / common ISY topics / how are you using your ISY.

The Flirc USB https://flirc.tv/products/flirc-usb-receiver?variant=43513067569384

It does work on Polisy, I am using on one now. The actual flirc device has to be programmed to recognize the IR. It only passes along mapped keys to the node server, so the node server never actually sees the IR information. I have uploaded a flirc config file in one of the other threads that has the 40 ISY IR codes mapped to keys (you can you that to skip the flirc learning process).

During the include process (before it adds the nodes) it should pop up with a security prompt asking for the device specific key/pin (if you select S2 security). Do you have 'use secure inclusion' checked in the Zwave menu? I tried adding a lock w/o using security and it wouldn't add any (useful) nodes. Anything in the event viewer?