KMan

Pull request created, you should have it now.

@kewashi Not sure if you are interested in contributions to HP ... if you are, I added functionality to display the ISY variable names rather than the ISY identifiers ("int_1") in the Existing Fields and Available Fields when linking ISY variables. I also removed the precision fields from the displayed option list, as I don't see any reason to link to them. The changes are fairly straightforward, and localized to just a few locations in 2 files. If you are interested, I can create a pull request, or you can view the changes directly at https://github.com/Tri2Spike/hpserver (hpserver.js and customize.js).

@kewashi Not sure if what I'm trying to do is supposed to be permitted or not ... but ... I am trying to change the text displayed on the "run" part of a program tile. Basically I just want one line of my custom text and the icon to show, nothing else. Maybe there's another way to do this but I'm trying to do this by putting custom text on the "run" field. This causes HP to treat the tile as a passive tile, and just pops up the tile values when I click on it. I added a hack in processClick() which seems to allow it to work. Not sure if it breaks anything else though. The hack is to exclude the ISY program commands ("run", "runThen", etc) from being processed as user commands. I added the '&& !progarr.includes(subid)' clause. // Exclude ISY program commands from being treated as user commands (if the user has // applied custom text to one of these fields. var progarr = ["run","runThen","runElse","stop","enable","disable"]; if ( usertile && usertile.length>0 && $(usertile).attr("command") && !progarr.includes(subid)) {

@kewashi Where do you announce new versions? If I "watch for releases" on github, will I be notified? Do you have a preferred central location for reporting issues? Here is an issue ... ISY has a function to "init" a variable, which sets the value that the variable will be set to on power up. This generates an event that does not include a val element, and housepanel ends up setting the value to NaN. Here is a log of the event (action 7 instead of the 6 used for set events): V2.328 on 9/12/2020 10:10:08 AM ISY event json result: { Event: { '$': { seqnum: '134', sid: 'uuid:68' }, control: [ '_1' ], action: [ '7' ], node: [ '' ], eventInfo: [ { var: [ { '$': { type: '1', id: '14' }, init: [ '1' ], prec: [ '0' ] } ] } ] } } V2.328 on 9/12/2020 10:10:08 AM Event info: { '$': { type: '1', id: '14' }, init: [ '1' ], prec: [ '0' ] } I hacked a fix by adding a check "if ( typeof varobj.val !== "undefined" ) {" before setting the variable. Probably better to validate the action is a set action before trying to set the variable. Keep up the good work. I'm really liking it so far.

@kewashi Thanks for your quick responses! Note that the custom tile display does not get updated if the ISY Variables tile isn't present. If I put the ISY variables tile on the page, everything works great ... but if I remove that tile, the custom tile linked to it does not get updated. Everything seems to work, the variable gets updated in the ISY, and housepanel receives the notification (verified by DEBUG9) ... but the custom tile display doesn't get updated.

Thanks ... I did realize after posting that linking was probably what I needed to do. Still having some glitches, but trying to work through them. I may have corrupted something, so may try starting over from scratch.

Started playing around with HP. Are people having success with ISY variables, or are they still in a proof of concept phase? I tried adding the variables tile ... and then painfully deleting all of the vars I didn't want on that tile. And then I created another variables tile, and it inherited all the changes I had made to the first one. Hope I'm doing something wrong!

Glad I found this ... pretty much just what I've been looking for. Played around with it for a little bit and am amazed at how configurable it is. Well done.

Is buying a cheap android tablet or phone and using it just for an alarm clock an option (no need for cell service)? Or even just seeing if anyone you know has an old one lying around unused? I've been using the tasker/autoalarm solution for a while, and it works really well. Additionally, I use an always on clock app, and it serves as a bedside clock as well.

Maybe I'm not understanding what you are saying, but IFTTT can run a program on the ISY, which then can do anything ISY can do.

Ah, you should be good to go with my instructions in post #3. One other thing ... you need to go in to the ISY portal and give the program a spoken name. There is a quirk in the ISY interface, in that when you first set it up, it queries the ISY for devices/scenes/programs and auto populates the spoken names. If you add devices/programs/scenes after setup, you need to go into the portal and add a spoken name. And then do discover devices again.

Advantage of the connected home: - Better accuracy - Simpler syntax (you are limited to on, off, set, dim, brighten and maybe a few other actions, but you don't have to say "Alexa, tell ISY to...") Advantage of the skill: - More flexible syntax Personally, I prefer the connected home. I've tried the skill, and didn't have good luck with Alexa understanding "tell ISY" or "ask ISY". For simplicity, I suggest working with the connected home first. Once you get that working, you could switch to the skill if you like the syntax better. You can have both enabled if you want. It is the syntax which determines which Alexa uses ("ask ISY" or "tell ISY" or "open ISY" keys the echo to use the skill). Anything else will go through the connected home. Have you installed the ISY portal? Have you connected the ISY through the connected home? Have you discovered devices?

Assuming you are using the ISY connected home (as opposed to the ISY skill): "Alexa, turn Pioneer On" will run the "then" part of the program. "Alexa, turn Pioneer Off" will run the "else" part of the program. For the program: Just put the required network resources in the "then" and "else" actions. No need to put any conditions in the "if", just disable the program. Unfortunately, to control volume, you cannot use terms like "volume", as echo interprets that to mean it's volume rather than another device's volume.

I had the same symptoms for a short time when I was first switching from the emulator to the connected home. I don't remember doing anything specifically that made it clear up (it lasted less than a day for me). I know that I cycled power to the echo, ISY and PLM ... but I don't really think that had anything to do with clearing it up.

Listen to him. You don't want to be running two DHCP servers, unless you know what you are doing. Post the make and model of the new router that you added. It can likely be set in a mode that it will act like a switch and not a router (including turning DHCP off). Unfortunately, it is not always obvious how to do this, since they try to make them plug and play for the normal use (which is one router on the network).

Sounds to me that both routers are acting as DHCP servers, and your ISY is ending up on a network that isn't reachable from the router that your PC is connected to. In addition, some other device is at the IP address that you think your ISY is at. You should be able to log into both routers and find out what IP your ISY is actually at (look for "attached devices" or something similar. While in there, you might try turning off the DHCP server on one of the routers if both have it turned on.

The other thing besides syntax that you need to be careful about is colliding with any of Echo's built in words. I'm trying to control my whole home audio via Echo, but words like "Music", "Radio", "Volume" or any radio station numbers/call sign collide with Echo's built in functionality and don't work.

Updating this in case someone finds this thread in the future. Thanks for the suggestions everyone. I've researched them and have settled on JRiver's Media Center, running on an always on PC (already in use for other reasons). Thanks to user hbsh01 who mentioned JRiver in this thread. JRiver is very easy to control via REST, and plays internet radio easily via vtuner. I've been able to easily integrate Echo -> IFTTT -> ISY -> JRiver to control my whole home audio via voice. Seems to be working very well. Next step is to remove IFTTT and use connected home directly. The iTunes integration isn't as seamless as I'd like (currently exporting then importing), but I have some ideas to make that easier.

Thanks for this post. I've been doing something similar with Subsonic (another media player), but the REST API is pretty limited. They expect the client to do most of the heavy lifting, so I've written some python scripts to translate simple network resource requests into complex Subsonic REST calls. I will have to check out Jriver.

Wouldn't that time be insignificant compared to the speech recognition and the cloud transactions (echo -> amazon -> portal -> ISY)?

Nice job. Is this a typo? Or does some pronunciation and use actually match that?

Would I need to activate the networking module to access the web services on the ISY?No/ The network module is not needed to access the REST api that the ISY provides. The network module provides the ability for the ISY to send network requests, and to upload your own web pages to the ISY.Are there any limitations to using the web services?Yes there are limitations. The REST API provides "read" and "update", but not "create" and "delete". In other words, you can't create/delete a variable or a program, nor can you edit existing programs. If all you want your UI to do is read/write variables and execute programs, you can do that. But if you want your UI to be able to write programs/variables (or edit them), you won't be able to do that.

Do you have multiple profiles set up on the echo (his and hers)? This sounds like the behavior I experienced when I had the echo set to a different profile than the profile that the ISY portal is linked to.

To be clear, doing it this way the secondary ISY would talk to the primary ISY, which would then talk to the BuzzLinc or 2867-2222. The secondary ISY doesn't communicate directly with the insteon devices in the primary residence. If you already have enabled internet access (or have the ISY portal) on the primay residence ISY, it is pretty straightforward. Steps: On the primary ISY, create a program that does whatever you need it to do (trigger buzzlink for example). Set this program to disabled. On the secondary ISY, create a Network resource that points to the primary ISY IP address. Use the rest api (documented here) to have the URL run the program created in #1 (use the program ID). Here is an example of a rest URL that uses the ISY portal to run the then clause of program ID 004D: https://<user>:<pass>@my.isy.io/isy/<portal key>/rest/programs/004D/runThen On the secondary ISY, create a program that detects the condition and triggers the network resource.

If you have the Network Module for your secondary residence, it can notify the ISY in the primary residence to do any notification you want.