io_guy

Nodeserver. NodeLink does it, not sure if polyglot has a node for it.

Correct, phone and EVL can exist together.

Anyone figured out how to make backlight consistent? I have 10 years of various switches and dimmers. Depending on the unit I see: 0-100% is perfectly linear with 0% being "almost" off (oldest units) 0% being the sun and 1-100& being somewhat increasing in brightness 0% being somewhat bright and then gradually gets lower till around 10% and then gradually gets brighter from 10-100% I used to be able to just set them all to 50% but it seems like I know need to go and tweak each one separately while standing in front with a laptop. Is this just an Insteon hardware/firmware "feature"?

Works fine here.

Restarting was the fix. Deleting the dir wouldn't make a difference unless your previous config had NodeLink on some strange port that was used by another resource. In that case you would edit the config.xml to change the port.

Reboot the Pi, you have two instances running (hence the "Already in use").

You're manually starting mono without the proper arguements to resolve the 5.16.0.179 bug. Look at the rc.local.

Nope, the part running was just a standard apt-get install. Maybe it ran out of memory. I see you're running X and VNC.

Rerun the install script now. I added an option to the mono run command to fix a bug in mono 5.16.0.179. (mono -O=-aot NodeLink.exe)

NodeLink installation on a Raspberry Pi is now a lot simpler. On a running Pi you type: sudo curl -sSL http://reverbautomation.com/Files/install.sh | bash That's it. It updates the Pi, installs dotnet, downloads NodeLink and sets up the startup script.

Nope. 4 or 5.

Anywhere to buy these in Canada yet?

Nothing, only lyric.

NodeLink is a console application (runs on a networked computer) which allows communication between various devices and an ISY-994i with firmware >=V5. NodeLink is a Node Server which creates nodes (virtual devices) within the ISY. NodeLink runs on a networked computer (Windows, linux, OSX, etc.) running 24-7 w/ NodeLink installed and requires .NET 5.0 runtime or greater be installed. Brief NodeLink guide can be found here Help for installing NodeLink on a Raspberry Pi can be found here 0.11.3 (2022-02-09) - Fixed an auto-update issue introduced in v0.11.1 - Changed nodedef ISY call to all lowercase (to support polisy) - GEM: Added support for all binary formats - GEM: Added ability to relay binary to Home Assistant 0.11.2 (2022-02-05) - Added the ability to disable the ISY connection (useless to anyone but me) - Caller ID: Added Android TV - Changed nodedef ISY call to lowercase (to support polisy) - Allow for NET major upgrade 0.11.1 (2021-02-06) - Weather: Fixed saving of API key - Weather: Fixed web config page error - Venstar: Fixed C/F temperature display - Genmon: Fixed getting Utility Voltage 0.11.0 (2021-01-04) - Moved to .NET 5 - New device added, Weatherbit (currently very limited) - WeatherFlow: Fixed pressure report on Air for US - Tweaks to the restart code - Removed VB and Linq libraries - Ecobee: Changed to single node definition for all units - Ecobee: Adjusted pin refresh - Ecobee: Updated JSON libraries - Ecobee: Changed remote sensors to identify by ID - TCC: Changed to single node definition for all units - Venstar: Changed to single node definition for all units - Added relay command to reboot ISY - CID: Added delay before sending init command on connection - GEM: Added support for format 3 - GEM: Fixed Wh calc on formats that don't supply it - GEM: Separated runtime data into a separate data.xml file - GEM: Added ability to limit the frequency of runtime data saves to disk - GenMon: Updated JSON libraries - Removed "nodeType" parameter from definition files (wasn't used) - Added the ability to set a custom log directory - Fixed issue (reliability) updating NodeDef files For previous version release notes see the change log built into NodeLink. v0.2.0 (2015-11-06) - Initial public release

To rainmachine. I'll run NodeLink from here.

Wouldn't be the parse or I'd get a JSON error. Any chance you could open the port up so I can connect from here? There must be something silly/different in the request post.

Yet another stupid bug. It's cause it's still using http when you set from the config until you restart. The address saved is fine though, so rebooting NodeLink should get it up and running (it loads the address properly with https). Will fix in next version.

0.9.5 is out and should fix this.

Oops that's my bad. I added regex checks to the IP address fields in NodeLink but forgot to take into account the possible addition of ports. I'll clean that up in a new release shortly.

If you do choose Z-wave, use the Homeseer HD100+ instead of the Leviton as it does not support the proper command classes for instant status.

Without knowing your ISY version it's difficult to answer the scene/z-wave portion. In any case, you can use a program to trigger a scene. Just get Alexa to run a Good Night program.

Hail was a valid method to get around a stupid patent that shouldn't have existed. The problem with the DZ6HD-1BZ is it's a new Zwave Plus device that still uses it. Its firmware should be updated to remove hail and add the central scene class instead.

Once a websocket has successfully subscribed, the user is immediately sent the status of all ISY nodes. Any chance a future firmware version can include the status of programs as well (then/else)? Their changes are sent over the socket fine but on startup I have to poll the rest interface for the dataset and initial values.

Each device (almost all) in NodeLink setup a heartbeat which toggles a bit in the ISY based on whether it's communicating with the end device. So it will tell you that the device, the Pi, and NodeLink are operational. If you want to do it with NodeLink without a device, install the ISY Data module and watch for the Minutes This Year to increment.

You don't need the python. If you're using NodeLink with the Honeywell the node already has a heartbeat that it sends to the ISY. You just need to add the ISY program to react to it.