markv58

I have been using Command Fusion for years to quickly set lights, check information and flip switches. Works well but a pain to update, so I came up with an actual app to do all those things even quicker, and updating is painless. I'm in the final stages, just cleaning up code and searching for bugs. This is not UD Mobile! I use that for the deep dives, to get to the nitty gritty, it's a great app for that and many other things as anyone paying attention knows. This is just to get in, do my thing, and get out. I'm curious as to the interest others may have in something like this so I thought I would share it with you. From start to finish in just a few minutes. Everything is custom in every tile and is simple to edit. Routines allow you to execute multiple command with just a tap, and a second tap just to make sure. Collections are some of your favorites gathered together in a way that best suites you and Information tiles are just that, information at a glance to see if something needs attention. I'm working on finding the URL scheme of all the apps I can, for instance, tapping on my Climate tile takes me to the EcoBee app. I'm curious about what you think, how you would improve it or any changes you would make. It's iOS right now but I'm willing to take the plunge and go Android if the interest is there. This should be ready for the Apple App Store in about a week for Flight Test.

Hard to find Insteon stuff sometimes, here's a link to the Siren : https://shop.insteon.com/products/insteon-siren I have 2 of the chime modules for notifications, really like them.

My UniFi APs updated at 3am, ISY is plugged into a Linksys router and has no portal connection either. I can connect to ISY through a Command Fusion app from the www and everything is working there. Seems like a portal problem.

Probably, got very busy with other projects. The "energy" part would be a separate ns because of the complexity. Planning to setup Brultech when time permits.

@gzahar @hart2hart The id is not linked to the variable, it was in the beginning but the nodeserver evolved. After much thought and feedback I decided to just have a number as the id rather than a proper name, which you can choose in the admin console and rename any time you want.

I'm thrilled about the way things are going, my home is as automated as I want it and it just works without any hands on intervention, invisible. There is the occasional low battery but that's about it. I've found time to work on an off-line voice assistant to replace the always sending data somewhere Alexa units, I call him Jarvis, he listens and does things but isn't connected to the internet.

The virtual switch is its own variable, on or off. You can link it to a variable with a program if you want but that seems redundant. A vs can be queried or used in a program same as a variable. I put them in scenes so I can query whether a scene is on or off and use them for a dozen other things as is.

Pushed an update, v1.0.15, should fix the problem on Polisy. Does not seem to effect RPi installs.

For myself, not having an irrigation system and only wanting to take care of the ornamentals, I chose to go the LinkTap direction. There is already a nodeserver for that.

Short answer, yes. Longer answer, you can use the Pi GPIO to trigger a relay. You could write a nodeserver to do that using the ISY programs. Exactly what would be needed as an intermediary so as not to burn up the Pi would need research. I did this to control a garage door. Here is the link to that GitHub: https://github.com/markv58/UDI-GarageDoorPi

Use a program to update the generic: If <something> is not <generic> Then <generic> is <something> Just to check, did you save changes after deleting the custom config param?

@DennisC The Generic is for any value 0 - 100 so it would be fine for humidity. When you delete a node from the nodeserver nodes page it should be removed from ISY too, make sure to delete the custom config page entry or it will reappear in ISY on a nodeserver re-start.

I had the same problem with one about that age, needed a new battery. I took it apart and replaced the battery with a Lithium battery, works again.

@tmorse305 Once you get that straightened out you should be ok. You probably need to update the ip of the nodeservers on the ISY side.

@tmorse305 Well that is odd. Do other ns work on the polyglot? Did the polyglot ip change?

Update the new ISY address on the Virtual custom config page, save then restart.

@JBanaszak That can happen on rare occasion. The nodeserver needs to be restarted but can be difficult to reset. Watching the log, hit the restart button and then immediately hit the stop button several times until the ns stops. Hit start and if the error is cleared you should have a normal log. If you get the connected then unexpected disconnect message repeatedly try again.

I use 2 programs: Entry Light On - [ID 0005][Parent 0046] If 'Devices / Sensors / Door / Front- Door Sensor' Status is On Then Set 'Rooms / Entry / Entry Ceiling Light' On Else Run Program 'Entry Light Off' (Then Path) Entry Light Off - [ID 0006][Parent 0046] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 minute Set 'Rooms / Entry / Entry Ceiling Light' Off Else - No Actions - (To add one, press 'Action')

@tmorse305 According to the hints.yaml the "type" is correct for both devices. Home(1), Controller(2), Toggle(12) and Home(1), Controller(2), Dimmer Switch(9). There is another setting 'Multilevel Switch that may be more appropriate.

@tmorse305 From the Nodes page delete the device then delete the entry from the custom configuration page and immediately hit the Save Changes button. That should get rid of it. I have done the coding for the Generic / Dimmer node and it works as it should, brighten and dim. I also have removed necessity to link to a specific variable, the current value of a switch or dimmer is saved like the temperature data is saved. I see no real need to have those devices linked to variables, should you want that link, a program can do that without limitations. What say you about that? I can add a Push to and Pull from option if you or anyone thinks that necessary.

The virtual device can't be a controller because it doesn't actually exist, you can set a program to make it control scenes. This is how I have one setup: Shop Lights - [ID 019C][Parent 0185] If 'Devices / Virtual / Shop / Switches / Shop Lights' Switch Status is Off Then Set 'Scenes / General / Shop' Off Else Set 'Scenes / General / Shop' On You would need to use a virtual generic node to have fade ability however there is no Brt or Dim capability right now. I have made some updates to Virtual but haven't completed all the work. I will add the Brt and Dim to the generic node which should solve the issue and push an update.

@gviliunas That looks normal, it's the driver that is reporting the minutes since last update.

I've thought about this quite a bit and think the best way is the Key being a unique number and of course the value being the node type. Going free form can cause a lot of problems down the road and then there is the node db cleanup. When a node is deleted, it's db remains and I need to add a routine that checks for orphaned files and deletes them, much easier to do with digits. You can always rename the node in ISY and easily change the name should you want to repurpose the node or just don't like the name. So, I would start at 1 and work my way up. The config page will sort in numerical order so you know what is available next.

The original purpose of having the node send data to a variable, especially the init, was to have a way to record the state of the switch incase of an Isy reboot or other event that wiped out the status. I now have the status saving to the nodes db and see no real need to have the variable linked any longer.

The number you assigned to the device, switch, is the ID number of the state variable that will be updated. I am nearly done with the next update that removes that link.