MWareman

Modify /etc/dhclient.conf to persist the hostname, set the DNS domain, and change the DNS server order...

Interesting. My 2.2.4 does not have a GUI option to change the port. I have it in my config .env file though (because I prefer port 443). That being said - did you restore from another install? I wonder if the option could have been set via that process.

After installing npm, I had to fully remove the Tesla node (from the UI) and then delete it from the filesystem. On reinstalling it - it worked. No manually running install.sh needed.

Try installing npm (I posted the command above)

Looking in /var/polyglot/nodeservers/Tesla/package.json, I see the following dependencies needed: "async-lock": "^1.1.4", "markdown": "^0.5.0", "polyinterface": "^1.2.3", "pgc_interface": "^1.0.3", "request": "^2.88.0", "request-promise-native": "^1.0.7" I'm not as familiar with node services - or their dependencies. However - the npm binary is nowhere to be found. So - this likely needs installing first: [admin@polisy /]# sudo pkg install npm-6.11.3 Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. The following 4 package(s) will be affected (of 0 checked): New packages to be INSTALLED: npm: 6.11.3 node: 12.13.0 libuv: 1.33.1 gmake: 4.2.1_3 Number of packages to be installed: 4 Uninstall and re-install the Tesla poly then appeared to work... Now - if only someone would provide me a Tesla to test with... Edit: In all likelihood - this is going to be needed for most (all?) node based polys....

It’s why it’s called a geek batch!

Good to know. I wonder if the current process is relying on a local compiler (not present on PolISY for obvious reasons!) - and the installation process needs instead to call the native package manager to install a binary version.

Answered my own question: [admin@polisy ~]$ sudo pkg install py37-netifaces-0.10.9 Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: py37-netifaces: 0.10.9 Number of packages to be installed: 1 10 KiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching py37-netifaces-0.10.9.txz: 100% 10 KiB 10.4kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Installing py37-netifaces-0.10.9... [1/1] Extracting py37-netifaces-0.10.9: 100% Then the WirelessTag poly started just fine... You may need to have a method that dependencies can be resolved and installed automatically. Or - Poly authors should include dependency information in the Poly metadata and Polisy should install the dependencies when Poly's are installed from the store.

Well - installing Polys is working now that Polyglot 2.2.4 is installed. Weatherflow and the WirelessTag polys. Weatherflow appears to be working - but WirelessTag is reporting the following: 2019-10-28 19:52:47,967 [MainThread] [INFO ] UDI Polyglot v2 Interface 2.0.31 Starting... 2019-10-28 19:52:48,830 [MainThread] [ERROR] Traceback (most recent call last): 2019-10-28 19:52:48,831 [MainThread] [ERROR] File "./wirelesstags-poly.py", line 8, in <module> 2019-10-28 19:52:48,832 [MainThread] [ERROR] from wt_nodes import wtController 2019-10-28 19:52:48,832 [MainThread] [ERROR] File "/var/polyglot/nodeservers/WirelessTag/wt_nodes/__init__.py", line 7, in <module> 2019-10-28 19:52:48,833 [MainThread] [ERROR] from .wTagManager import wTagManager 2019-10-28 19:52:48,834 [MainThread] [ERROR] File "/var/polyglot/nodeservers/WirelessTag/wt_nodes/wTagManager.py", line 10, in <module> 2019-10-28 19:52:48,834 [MainThread] [ERROR] from wtServer import wtSession 2019-10-28 19:52:48,835 [MainThread] [ERROR] File "/var/polyglot/nodeservers/WirelessTag/wtServer.py", line 11, in <module> 2019-10-28 19:52:48,836 [MainThread] [ERROR] import netifaces as ni 2019-10-28 19:52:48,836 [MainThread] [ERROR] ModuleNotFoundError 2019-10-28 19:52:48,837 [MainThread] [ERROR] : 2019-10-28 19:52:48,837 [MainThread] [ERROR] No module named 'netifaces' So - the Python module 'netifaces' is not present... Figured I' give pip3 a go: [admin@polisy ~]$ sudo pip3 install netifaces Password: Collecting netifaces Downloading https://files.pythonhosted.org/packages/0d/18/fd6e9c71a35b67a73160ec80a49da63d1eed2d2055054cc2995714949132/netifaces-0.10.9.tar.gz Installing collected packages: netifaces Running setup.py install for netifaces ... error ERROR: Complete output from command /usr/local/bin/python3.7 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-z68xnvz6/netifaces/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-l5ncxh2k/install-record.txt --single-version-externally-managed --compile: ERROR: running install running build running build_ext checking for getifaddrs...not found. checking for getnameinfo...not found. checking for socket IOCTLs...not found. checking for optional header files...none found. checking whether struct sockaddr has a length field...no. checking which sockaddr_xxx structs are defined...none! checking for routing socket support...no. checking for sysctl(CTL_NET...) support...no. checking for netlink support...no. building 'netifaces' extension cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC -DNETIFACES_VERSION=0.10.9 -I/usr/local/include/python3.7m -c netifaces.c -o build/temp.freebsd-12.0-RELEASE-p10-amd64-3.7/netifaces.o unable to execute 'cc': No such file or directory error: command 'cc' failed with exit status 1 ---------------------------------------- ERROR: Command "/usr/local/bin/python3.7 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-z68xnvz6/netifaces/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-l5ncxh2k/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-z68xnvz6/netifaces/ Seems cc is not present... I guess I'd need to setup a cross-compilation environment. What should the process be to request dependent Python libraries?

Bingo... My outbound proxy was being a bit overzealous - the SSL cert is using a wildcard SAN name. My proxy was blocking that.. [admin@polisy ~]$ true | openssl s_client -connect pkg.isy.io:443 | openssl x509 -noout -text | grep DNS: depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify return:1 depth=0 CN = *.isy.io verify return:1 DONE DNS:*.isy.io I've bypassed the proxy for the PolISY for the time being (until I can figure out a better option). The update then worked just fine. Thank you! Michael.

Good point. I do have a proxy on my LAN - but the WPAD only targets my Daughters devices. Let me check...

I know this would add a few $ to the cost - but a small oled display driven by an OS driver could report the IP address (if DHCP assigned one) or the MAC of the interface with link (if not)... No stickers needed... Something like this (if the board has an I2C port): https://www.aliexpress.com/item/4000008299769.html It would just need a suitable driver.... but the display could be used in the future for all kinds of user feedback (far more informative than lights to blink out fault codes).

Michel, This is what the update / upgrade attempt results in: [admin@polisy ~]$ sudo pkg update && sudo pkg upgrade Password: Updating udi repository catalogue... SSL certificate subject doesn't match host pkg.isy.io SSL certificate subject doesn't match host pkg.isy.io SSL certificate subject doesn't match host pkg.isy.io pkg: https://pkg.isy.io/udx12/meta.txz: Authentication error repository udi has no meta file, using default settings SSL certificate subject doesn't match host pkg.isy.io SSL certificate subject doesn't match host pkg.isy.io SSL certificate subject doesn't match host pkg.isy.io pkg: https://pkg.isy.io/udx12/packagesite.txz: Authentication error Unable to update repository udi Error updating repositories! [admin@polisy ~]$ https://pkg.isy.io seems to issue a redirect to your main website currently.. (though this may be normal as this is a browser request to / - Polisy may be making a POST or other request to something other than the default document)... GET / HTTP/1.1 Host: pkg.isy.io Connection: keep-alive Pragma: no-cache Cache-Control: no-cache DNT: 1 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36 Sec-Fetch-Mode: navigate Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3 Sec-Fetch-Site: none Accept-Encoding: gzip, deflate, br Accept-Language: en-US,en;q=0.9 HTTP/1.1 302 Moved Temporarily Server: nginx/1.16.1 Date: Mon, 28 Oct 2019 23:55:51 GMT Content-Type: text/html Content-Length: 145 Connection: keep-alive Location: https://www.universal-devices.com Strict-Transport-Security: max-age=31536000; includeSubDomains; preload Michael.

Without seeing your Tasker profiles it’s difficult to decode what you are meaning. I’ve never sent email to Tasker - so I don’t really know what profile elements you are using to have Tasker react to email. Are you able to post some examples so I can see what is meant? Behind the scenes - network rules will be faster than email - because network rules are a tcp socket made real time - and email is store and forward. Sometimes, the difference may be negligible. Other times, noticeable. It depends on many things outside of the scope of this forum.

Most modern routers will list the name received in the DHCP request. This makes the Polisy easy to spot in the list (it’s name is “Polisy”). I do agree though - I know MAC addresses are not user friendly - but it does allow a DHCP reservation to be created in advance and/or a reservation to be easily found. Ideally, this would be provided on a sticker adhered to the Polisy. This has become pretty common practice. It’s not surprising that the geek batch came without though.. . That’s kind of the point so that changes can be made prior to shipping to non-geek users.

Pushover posted a write up on the issue... https://blog.pushover.net/posts/2019/10/october-24-25-ddos-attack

Personally, I prefer notifications. They are ephemeral and don’t clutter up an email inbox. Notifications are generally faster to arrive as well and don’t rely on the email client having to poll a mailbox.

That's interesting. Thanks for pointing that out. I think something may have changed in the ISY (since that wiki was written back in 2014). GET is correct for sending to AutoRemote. I'll update the Wiki page accordingly to match current reality. Edit: Wiki edited. Thanks for the report. I added additional clarification about variable substitution and interaction with 'Encode URL' as well since when that page was originally written that was not possible.

Michel, I just logged onto Polisy again - and the SolarEdge Poly is gone... I wonder if it was a default there from the image used. Michael.

I guess I should have paid attention to where this post was already! On 1 - That's what I figured out. I assume the post-geek batches will have a limited shell by default (much like the ISY today). 2) Awesome! 3) I cannot see this in the UI. I can see where you set the 'hostname' of the MQTT broker (localhost by default). I'm pretty sure that's not it. 4) Thank you! That's what I thought - the git clone error usually occurs when it cannot write to the storage (permissions or space). 5) I can see a UI branch in your near future! I guess I should also ask about the 'Use Beta Firmware' checkbox.

Email sent! I'll move all other discussion to the correct place.. Thanks!

By Pushover URL - I mean the NR pointing to Pushovers API: https://pushover.net/api#messages Pushover has a library of sounds baked in. https://pushover.net/api#sounds As long as one of the sounds fits - then Pushover will be better. If you want full control over the sounds played - then you will need to use Tasker/Autoremote.

If using the Pushover URL - then Pushover is playing the message and popping up the notification. No Tasker or autoremote needed. If using the Tasker / Autoremote method - the you need to write a Tasker profile that triggers on the incoming AR message and runs a task that plays your notification (and pops up your message).

If you want to try having Pushover natively notify you (instead of needing Tasker to intercept) - the try setting the priority to >0, and the sound to something. token={token}&user={user}&priority=1&sound=falling&message={message} 1 causes Pushover to make a high priority notification, and 2 causes the message to repeat the notification until it's acknowledged. This can only be done from a NR AFAIK. Tasker intercepting incoming will require a different triggering profile that what you used for email. I've never configured Tasker to trigger from incoming Pushover pushes (it just seems redundant). For using NRs to send data to Tasker - this is the wiki I refer to: https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification:Tasker

I use Autoremote (a Tasker plugin) and use NRs to send messages to it. Tasker then acts on incoming messages to Autoremote without issue. I put this recipe on the wiki as well. Is that what you are doing? A better alternative may be to send the Pushover message with a parameter to play a sound. That way it’s not dependent on Tasker.