Everything posted by simplextech
-
ISY not (fully) operating
Was the IP address the same or different from before the re-install? May have been asked already but is your ISY configured with a static IP address or DHCP?
-
ISY not (fully) operating
No DHCP reservation.... so the IP address of the ISY could have changed during your testing and rebooting and such. Have you cleared your java cache and downloaded and installed the ISY finder during any of this?
-
ISY Portal, ISY Dashboard, Home Automation Dashboard, my.isy.io, udajax
I've been giving this a lot of thought recently..... I looked into Home Assistant again and their native and hacs component for ISY. Neither are even loading or working if Nodeservers are present so this is a non starter. I looked into OpenHAB and their binding. It's deprecated and not maintained. Probably wouldn't work correctly so I didn't continue looking. If someone else runs OpenHAB with the ISY binding please let me know how well it works and particularly with Nodeservers. Currently none of the mobile apps (eKeyPadPro, Agave, Mobilinc X) support nodeservers. I've heard from all of them they are "looking into it". At what time frame is unknown and which developers they are working with to test/validate nodeservers? I think HAD or a variation of it is still viable and could be continued. However at what level of interest from people and at what cost? (development time).
-
ISY not (fully) operating
As mentioned earlier all of this is pointing towards some network issue. I went back in the thread and you said you don't have a "Port" reservation. But do you have a DHCP or Host Reservation within the Google Wifi router? I know nothing about the Google Wifi or how/what they may call it but it should not be "Port". Does the AC still work only sometimes? after a ISY reboot it works and then stops working?
-
ISY not (fully) operating
It sounds like there's a lot of issues and a lot of changes before, after, during this whole debacle. Have you contacted UDI support? Can they look at your system and try to get things working? From the Portal and AC side I think UDI should look to verify the portal registration is good.
-
3-Way Wiring - Use ISY , or Not?
Doing the linking from the ISY gives you the best of the technology. Without the ISY managing the switches you can't use them in a program. The devices are still inked and still work without the ISY being online just like they would with direct linking. So you lose nothing but gain the ability to use them with ISY programs.
-
ISY not (fully) operating
Polyglot running local has zero connection to the ISY Portal. In any kind of troubleshooting exercise only do one thing at a time and check results before continuing as when you do 3 things how do you decide what fixed things or caused the problem?
-
Pull Variable Value from ISY to Python Program on Pi
You're very welcome. I grabbed pieces from the ISY-Inventory polyglot and edited to work outside of the nodeserver. Here's the link to my public repositories. Might find some ideas or useful tidbits. https://github.com/simplextech?tab=repositories
-
Pull Variable Value from ISY to Python Program on Pi
Give this a try. I left comments inline and print statements for debug #!/usr/bin/env python3 import xml.etree.ElementTree as ET import requests from requests.auth import HTTPBasicAuth def get_request(url, user, password): try: r = requests.get(url, auth=HTTPBasicAuth(user, password)) if r.status_code == requests.codes.ok: return r.content else: print("get_request Error: " + r.content) return None except requests.exceptions.RequestException as e: print("Error: " + str(e)) my_switch = 0 isy_ip = "192.168.1.69" user = "admin" password = "admin" svars_url = "http://" + isy_ip + "/rest/vars/get/2/1" svars_resp = get_request(svars_url, user, password) # print(svars_resp) if svars_resp is not None: svars_root = ET.fromstring(svars_resp) # print(svars_root.tag, svars_root.attrib) for svar in svars_root.iter('var'): # print(svar.find('val').text) my_switch = svar.find('val').text print("My Switch Value is: " + my_switch) Change the (isy_ip, user, password) to match yours.
-
ISY not (fully) operating
If those are the only changes then remove them and see if the problems clear up. Then add one at a time to see if a problem returns.
-
Initial Feeback
I suppose that's one way to check. Normally one would check the process table and see if the process is found, if it's been running for a while or not. Does a "start" the script checks if it's running but doesn't provide much information. Do you have anything in your logs that may point to why it's not displaying in the UI?
-
Initial Feeback
Have you logged into the box to see if the udx process was still running? Did it crash for some reason? Look at the logs?
-
Pull Variable Value from ISY to Python Program on Pi
In your python r is the requests object. You can access the contents via literally the objects contents. change the print statement like this. print(r.content) That will print the content you receive from the requests.get which is contained in the 'r' variable (object).
-
Support Thread: 5.0.16C (ISY994)
Not sure about the slowness in programs but 5.0.16A did fix the slowness of a right-click on a z-wave device from the main screen. Hoping it's still fixed in this release.
-
When will PolISY be shipped?
For those that want a GUI and want it "their way" I recommend investing some time with The Home Remote or Command Fusion and learn it's not "easy" which means it takes a lot of time which equals a lot of money if you're hiring staff to do it.
-
When will PolISY be shipped?
I don't agree with the "app business". Here's why. I know of 2 major platforms that in the last year have shifted their "direction" to being mobile first. Both were automation platforms that had remote access and had a way of doing things. "New Users" all whined for a "mobile app" to be "easy" and because they wanted an "app"..... So one platform catered and developed a basic app for the users. The users do NOTHING BUT COMPLAIN because the app is basic and because it's not the core business it does not function well all of the time and is just not that good of an app. Because it's not the core business and they didn't have proper resources (staff) to build a good app now they have a crappy app that people still complain about and they have to shift resources around trying to "appease" these "basic users" and support the app they released. The second company went so far as to modify the core of their system interface and functionality to make an app that was super "pretty" and gave new users what they are wanting. The result is that is destroyed the local web UI for real users that want to have flexible administrative control and power to make their system do what it's supposed to do... AUTOMATION. But hey it looks "Pretty" right? So now there's a powerful system that's pretty and "easy" but to really do anything takes 100 mouse clicks a and dozens of popup windows and scrolling through hundreds of pages of devices to do anything.. but it's pretty!!!! Moral is... UDI and these other companies are NOT app developers and unless You and others that really want an app shell out the upfront capital to hire the staff necessary to properly developer a mobile app then I won't want UDI or any other company spending time/resources on a mobile app when there are 3rd party companies already out there doing this and doing it well. If you want the mobile app to be better... please complain to those companies. UDI is a automation system NOT a control system and it should stay that way. Now to play a little devil's advocate. I think the old HAD should be updated/upgraded as a framework to allow people to more easily build their own custom Web Dashboard for use in display and basic status/control Dashboards. That is a framework design and some basic template for direction/use of what's possible. Then other 3rd parties I'm sure would pick that up and develop dashboards that people could then use or buy. I know I would. In fact I've been looking at HAD thinking of what I could do with it or revise it. Sorry if this is too direct but I've seen 2 systems in the last year go down this route... one is now floundering and is unstable and a mess and the other is on it's way....it's a race to the bottom to attract "New Users" and gotta have a "Shiny App" seems to be the attraction... frankly from the quality/level/experience of these "New Users"... Umm I'll pass....
-
Actions with Insteon HUB not seen by ISY
Mobilinc, Agave, eKeypadPro are some of the options.
-
Actions with Insteon HUB not seen by ISY
The two do not work together like that. You should pick one system and work from that point.
-
MobiLinc X (iOS/Android) now supports ISY Portal!
I'm sure it would be and would be a lot less profitable. It takes a lot of time which equals money to develop software. Just because Apple/Google have a "family share" option that people like doesn't mean it's fair to the app developers. So the in-app purchase is the only way to circumvent the "family share" that Apple/Google built. I don't mind paying for each install (license) WHEN the app is a reasonable price. Currently @InsteonNutI think the direct + remote is silly borderline ridiculous that they are extra charges. Should be one. I don't have ELK yet and I'm not going to expose camera's via port forwarding so the ONVIF camera support is worthless to me for remote and like many (most) I use Blue Iris or Xeoma or Unifi Protect for cameras so ONVIF doesn't matter. Make the direct+remote (ISY Portal connection) a single app/purchase as they technically are the same connect method and make it a reasonable price for an app.
-
I am excited about the new Echo flex motion sensors.
You can't.
-
When will PolISY be shipped?
E-mail sent...
-
In Floor heating thermostat options for the ISY 994i
In Polyglot Cloud (web browser). Refresh. It's a browser/UI thing with the nodes not being listed in the Polyglot UI. If they are showing in the ISY Admin Console then all is well.
-
In Floor heating thermostat options for the ISY 994i
Did you go to the controller node and click the Discover button? See if the missing node appears or not. EDIT: I just did a re-install on my Prod system and I have the 3 day/week/year nodes for the energy log which is correct.
-
Log maximum?
That is odd/interesting that it didn't start overwriting the old... May want to ask support about that one.
-
In Floor heating thermostat options for the ISY 994i
There should be the 3 day/month/year. I'll go take a look but I didn't mess with that portion of the code but ya never know...I have seen where not all nodes get created every single time on installs. Do a Discover and see if it shows up.