Bumbershoot

Now, if you can get your hands on a Polisy, you should be able to keep your Insteon investment alive. Don't expect it to be simple, but this can actually be a vast improvement over your experience with the Insteon hub. Expect a learning curve, sometimes a steep one.

Mine are working as normal, but I've never had an Insteon hub involved in my setup in any way whatsoever.

I have three different types that I've been testing, and while all good, the best for me in general lighting applications has been the Zooz Zen7x series. The ergonomics of this switch are good, and they respond very quickly, especially with a series 700 controller. Other switches I've used successfully are the GE/Jasco Embrighten (which are Z-Wave+, not series 700) switches/dimmers/motion sensors/fan switches (the switches/dimmers with the built-in motion sensors solve several problems for me), and Homeseer switches (to be fair I haven't installed their HS WX-300 yet, but the previous version is very good, and the status RGB LEDs can be useful in some situations). I'm still relying on Insteon for most of my lighting, so I haven't done anything fancy with the Z-Wave switches -- I just control them with ISY programs, but they've all been reliable, and I could (and do) live with any of them.

This may not be related to your issue or the Node server, but if you have a mesh WiFi network, then some Sonos installations can have problems staying continuously connected to WiFi. Two solutions have worked to solve this issue in the couple of networks that I've had to deal with: 1) connect one Sonos speaker to the network with an ethernet cable instead of WiFi, or 2) add a Sonos Boost to the network. If the problem continues and you have a mesh WiFi setup, this may solve your issue.

It won't hurt me, as production is on PG2, and will be for a while yet. I like the sounds of what this update will provide, however. I'll probably install the notification Node server as well due to the Short Custom Content functionality.

Thanks, that works...

Thanks. I set the log level to "Info" and it's chugging along just fine now.

This appears to be happening with other node servers as well, but with the latest PG3 3.0.54 update, I'm getting these errors in the log: 2022-03-29 07:06:09,912 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-03-29 07:06:10,081 Command udi_interface ERROR udi_interface:write: Exception in thread 2022-03-29 07:06:10,082 Command udi_interface ERROR udi_interface:write: Command 2022-03-29 07:06:10,082 Command udi_interface ERROR udi_interface:write: : 2022-03-29 07:06:10,083 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-29 07:06:10,084 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-03-29 07:06:10,088 Command udi_interface ERROR udi_interface:write: self.run() 2022-03-29 07:06:10,089 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-03-29 07:06:10,093 Command udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-03-29 07:06:10,094 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 678, in _parseInput 2022-03-29 07:06:10,098 Command udi_interface ERROR udi_interface:write: self._handleInput(key, input[key], None) 2022-03-29 07:06:10,099 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 684, in _handleInput 2022-03-29 07:06:10,103 Command udi_interface ERROR udi_interface:write: self._inConfig(item) 2022-03-29 07:06:10,104 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 598, in _inConfig 2022-03-29 07:06:10,108 Command udi_interface ERROR udi_interface:write: LOGGER.setLevel(self.currentLogLevel) 2022-03-29 07:06:10,108 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 1421, in setLevel 2022-03-29 07:06:10,114 Command udi_interface ERROR udi_interface:write: self.level = _checkLevel(level) 2022-03-29 07:06:10,115 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 198, in _checkLevel 2022-03-29 07:06:10,118 Command udi_interface ERROR udi_interface:write: raise ValueError("Unknown level: %r" % level) 2022-03-29 07:06:10,119 Command udi_interface ERROR udi_interface:write: ValueError 2022-03-29 07:06:10,119 Command udi_interface ERROR udi_interface:write: : 2022-03-29 07:06:10,120 Command udi_interface ERROR udi_interface:write: Unknown level: 'NULL'

Running PG3 3.0.54, and version 3.1.4 of this Node server, and I'm getting these errors in the log: 2022-03-29 07:01:21,446 MQTT udi_interface.interface INFO interface:_message: Successfully set wtcontroller :: ST to 1 UOM 25 2022-03-29 07:01:24,135 MainThread udi_interface.interface INFO interface:addNode: Adding node WirelessTagsController(wtcontroller) [None] 2022-03-29 07:01:24,137 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. 2022-03-29 07:01:24,338 Command udi_interface ERROR udi_interface:write: Exception in thread 2022-03-29 07:01:24,339 Command udi_interface ERROR udi_interface:write: Command 2022-03-29 07:01:24,340 Command udi_interface ERROR udi_interface:write: : 2022-03-29 07:01:24,341 Command udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-29 07:01:24,342 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-03-29 07:01:24,347 Command udi_interface ERROR udi_interface:write: self.run() 2022-03-29 07:01:24,348 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-03-29 07:01:24,351 Command udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-03-29 07:01:24,352 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 678, in _parseInput 2022-03-29 07:01:24,356 Command udi_interface ERROR udi_interface:write: self._handleInput(key, input[key], None) 2022-03-29 07:01:24,357 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 684, in _handleInput 2022-03-29 07:01:24,361 Command udi_interface ERROR udi_interface:write: self._inConfig(item) 2022-03-29 07:01:24,362 Command udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.8/site-packages/udi_interface/interface.py", line 598, in _inConfig 2022-03-29 07:01:24,365 Command udi_interface ERROR udi_interface:write: LOGGER.setLevel(self.currentLogLevel) 2022-03-29 07:01:24,366 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 1421, in setLevel 2022-03-29 07:01:24,373 Command udi_interface ERROR udi_interface:write: self.level = _checkLevel(level) 2022-03-29 07:01:24,374 Command udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/logging/__init__.py", line 198, in _checkLevel 2022-03-29 07:01:24,376 Command udi_interface ERROR udi_interface:write: raise ValueError("Unknown level: %r" % level) 2022-03-29 07:01:24,377 Command udi_interface ERROR udi_interface:write: ValueError 2022-03-29 07:01:24,378 Command udi_interface ERROR udi_interface:write: : 2022-03-29 07:01:24,379 Command udi_interface ERROR udi_interface:write: Unknown level: 'NULL'

The error -110022 might be the cause. From the error codes listed in the wiki: -110022 OPEN FILE FAILED

I'll bet 3.0.46 deamon was still running, even though the newer version was installed. sudo service pg3 restart would have likely given the same results as the system shutdown/restart (it did in my case).

I don't know about the roomieremote, but it appears to be an IP based control system, so it should work just the same with a Polisy. Otherwise, if you're all Insteon/X10, you should purchase a Polisy and consider a migration plan. I doubt there'll be much development other than bug fixes for the ISY994i ZW Pro, as Polisy is the UDI platform going forward, and it's a much more capable device than the ISY994i. You could simply restore of a backup of your ISY994 on the Polisy and you'd be up and running. Z-Wave could come in time when you're ready to add devices (some Z-Wave dongles currently in the market are requiring upgrades to get past some issues, so it might be a good idea to wait a bit on that if you don't have an immediate need for it). If you're going to use the same serial PLM that your ISY994i uses, then I believe there's an issue with the cable that the ISY994i uses (you'll need to use the cable that came in the packaging). If you have a USB PLM, then no issues at all. Just keep in mind that IoP is under heavy development at the moment.

I haven't turned on the system yet, still too many freezes overnight, and I'm still running on my ISY994 and PG2, not IoP and PG3. The Node server is running normally...

Well, I simply checked for status of this single detector (the status on this detector changed when any of my other hardwired detectors saw smoke), and this always worked as intended. I replaced these detectors with wireless Elk detectors quite a while ago, so this solution is no longer in use, but it worked: Smoke Bridge - [ID 004D][Parent 0013][Not Enabled] If 'Devices / dirMasterBedroom / Smoke Bridge-Smoke' Status is On Then Set 'Devices / dirLivingRoom / ZW 007 Siren' On Wait 2 seconds Set 'Scenes / scnAllInteriorLights' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / flcFan-Light' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / sldGuestVanityLight' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / sldGuestShowerLight' Fast On Wait 2 seconds Send Notification to '3' content 'Smoke Detector Alert' Wait 5 seconds Set 'Devices / dirLivingRoom / ZW 007 Siren' Off Else - No Actions - (To add one, press 'Action')

@xlurkr, if you need a hard wired detector, it looks like Amazon still has these: https://www.amazon.com/gp/product/B000EVO9D4/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1 I put one of these in, connected it to the Smoke Bridge, and it worked as expected.

@stevehoyt, for the programs that are yellowed and say "Out of Memory" in the status page, the first thing to try is to simply re-save these programs. They may or may not need an edit (I would inspect them), but clicking on the "Save Changes" button might restore the functionality of the programs. This is a problem that was encountered often when folks upgraded from the v4.x.x firmware to 5.x.x firmware in the ISY994. It's a simple thing to try, at least...

My ISY994 has the correct time for sunrise/sunset (v 5.3.4), and my IoP has sunrise/sunset an hour later (v 5.4.1_2). The 'date' command on my Polisy indicates that the time on the machine is correct.

It appears that the Aeotec Multisensor 6 motion sensor does indeed work as a controller in a Z-Wave scene. The motion sensors in my Jasco switches/dimmers to not. I'm not sure what the difference is, as the Multisensors seem to have mostly the same set of commands that the Jasco switches/dimmers have. Lots to learn here... Aeotec Multisensor 6 node details: Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ---------------------------------------------- Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW 008 Motion Sensor 1 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW008_155 uid=8 security=None type=4.33.1 mid=134 tid=258 pid=100 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] Association Group ID 1 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW008_1 - Primary Isy Node Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x20 V1 BASIC Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x86 V2 VERSION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x85 V2 ASSOCIATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x73 V1 POWERLEVEL Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x71 V3 NOTIFICATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x84 V2 WAKE_UP Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x80 V1 BATTERY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x30 V1 SENSOR_BINARY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x31 V5 SENSOR_MULTILEVEL Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - xEF V0 MARK Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - Secure Sun 03/13/2022 06:29:02 : [ZW-SHOW ] Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ---------------------------------------------- Jasco motion sensor node details: Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ---------------------------------------------- Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW 025 Motion Sensor 1 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW025_155 uid=25 security=None type=4.16.1 mid=99 tid=18765 pid=12338 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] Association Group ID 1 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW025_1 - Primary Isy Node Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x20 V1 BASIC Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x73 V1 POWERLEVEL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x27 V1 SWITCH_ALL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x2B V1 SCENE_ACTIVATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x2C V1 SCENE_ACTUATOR_CONF Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x86 V2 VERSION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x71 V4 NOTIFICATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x60 V4 MULTI_CHANNEL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x8E V3 MULTI_CHANNEL_ASSOCIATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x85 V2 ASSOCIATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x56 V1 CRC_16_ENCAP Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - Secure Sun 03/13/2022 06:30:44 : [ZW-SHOW ] Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ----------------------------------------------

Is see now. Maybe there's still a bit of fixin' to do on the files?

Maybe I misunderstand, but I'd think that tab separated values in the file might be deliberate as well. https://en.wikipedia.org/wiki/Tab-separated_values

CR + LF is known as DOS format for text files, whereas a single LF is known as UNIX format. DOS format makes the files compatible with Windows text editors. I assume UDI did this deliberately, likely due to the error log formatting complaints that were addressed with ISY version 5.40, though I haven't followed the issue. In many *nix distributions there are included utilities to convert files: 'unix2dos' and 'dos2unix', neither of which are included in the POLISY FreeBSD distribution. https://www.freebsd.org/cgi/man.cgi?query=dos2unix&manpath=CentOS+7.1

I like the sounds of what you're doing. I live in a desert environment with an ongoing and persistent drought and porous, volcanic soil. Proper and effective irrigation requires precision here. Thanks to you, @JimboAutomates and @glarsen for helping me accomplish water savings with these tools (and thanks to @io_guy for starting me down this path). This is the single area where home automation actually pays... Also, @simplextech provided the EcoWitt nodeserver, and the EcoWitt moisture sensors are really useful.

Enhancements : - Added Gallon per hour I'm curious if this was added in support of this nodeserver? I'm considering buying a FlumeWater device to work in conjunction with my Rainmachine, much as @stevehoyt is apparently doing. I see some discussion in the github repository that suggests something like this.

This may be something entirely different that what you're asking for, but I was able to add an additional SKY unit to the hub that also connects to my TEMPEST unit, and the PG3 nodeserver shows data from both the SKY and the TEMPEST. Only one copy of the nodeserver running. Very handy. The SKY unit is measuring indoor data. Thanks for adding this functionality, @bpwwer!

It looks like @xKing has done the most recent commits in github, and somewhere I got the impression that he was working with UDI with Polisy (I could be completely wrong about that). I see he was active on github last month, so my guess is that it's not moribund yet!