apostolakisl

Probably overkill doing both is zero or is not zero since the odds of it being exactly at 0.0 and staying at 0.0 are slim to none, but whatever.

I don't really know what all of the names of your stuff is, but if it is loading real time weather data into a variable, you would presume that the data would change at least a little with every update, especially if it is reading to the tenths place. You could use that as a retrigger for your monitoring program instead of a heartbeat. As an example, I have wireless tags monitoring a walk in freezer and fridge at my church. I have a program that retriggers every time the temp changes. If it fails to retrigger after 45min, I get an alert. For that program to fail, both the wait clause would have to fail and the wireless tag connection would need to fail essentially simultaneously. As a precaution, I could add a few "if" items such as if time is 6am, 12noon, 6pm, and 12mn to ensure I don't go more than 6 hours without an alert in the failure event I mentioned. Freezer Online - [ID 009F][Parent 009D][Run At Startup] If 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is not 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is not 0.0% Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is 0.0% Then Wait 45 minutes Repeat Every 1 hour Send Notification to 'Lou and Stuart' content 'Freezer Monitor Offline' Send Notification to 'Denis Phocas' content 'Freezer Monitor Offline' Else - No Actions - (To add one, press 'Action') To test your program you can right click on the program that is supposed to be running in a loop and hit "stop" and then see if your program alerts you.

It also occurred to me that you might be able to use the action of the program itself as the "heartbeat" depending on what that action is rather than having a variable that serves as the heartbeat. In other words, if the programming is expected to change the state of something, you can monitor that the state of that thing is changing rather than the state of the variable is changing. OH YEAH! The variable you use needs to be a state variable. I don't think I mentioned that. An integer variable will not work.

Some of the node servers have a heartbeat, one of the values just goes back and forth between 0 and 1 every 60 seconds. If (run at startup) status of node is 1 or status of node is 0 Then wait 5 minutes send notification The value changing every 60 seconds restarts the program so the 5 minutes never finishes unless the node goes offline. You could probably do something like that instead of what I wrote above If whatever you want Then repeat every 1 minutes whatever you want repeat 59 times set variable to 1 wait 1 minute set variable to 0 Now you would have a variable that is a heartbeat every 1 minute and you could just have a second program to send you a notification. But if you have a concern about it stopping at DST or whatever also add some hard start points for it If (run at startup) status of node is 1 or status of node is 0 or time is 8am or time is 8pm Then wait 5 minutes send notification

You could have your repeat set a variable to say 1. Then you could have another program that sets that variable to 0 on a schedule, like every morning at 8am, or you could have it run more often, but it needs to be a schedule, not a repeat. Finally, your last program would check periodically to see if that variable is one or zero. Depending on how often the program repeats and when your program resets the variable you would need to adjust the times for this stuff. For example: If whatever Then repeat every hour whatever you want set variable to 1 If time is 8am Then set varialbe to 0 If time is 9am and variable is 0 Then send me an email

The new rpi came. I stuck the sd card into it and it booted straight up. I moved it over to the same IP it had before and rebooted. The one and only node that didn't mysteriously get deleted populated as expected. All the others I needed to delete and re-add. I actually had 6 nodes on there, so 5 deleted. The one that didn't delete had nothing particularly different about it. It was neither my first nor last node that I created on PG2.

I'm not sure what the deal is, but I rebooted ISY and it blinked the two lights indicating no network. I changed the ethernet wire and the plug on the switch and rebooted again and it is fine. So, I guess that was a wire or switch issue. Hard to explain since it has been all the same for several years and no one was anywhere near any of this to bump into it or yank on anything. Also I made no changes to the network physically or setting wise in many months. For good measure I replaced the power supply and moved it to a UPS. I don't think any of this is related to the nodes disappearing. Upon further review, it appears 3 of the 4 nodes run by PG2 rpi got deleted from ISY. Then all the programs that had any mention of those nodes turned yellow and stopped running. My nodelink nodes are fine. New rpi came today, so we'll see what happens when it goes back online. Curiously, I also have Nodelink running on that rpi. I have CAI webcontrol, Sun Position, and ISY Data all running on nodelink. And some of the fields on those nodes populated even though nodelink is not there. Specifically, the hour and minute in ISY data are populating and the sun position is populating. I suppose those nodes are pulling some data from nodelink itself and some data from ISY. None of the fields for CAI webcontrol populated, which makes sense since ISY clearly has no internal knowledge of any of that, but ISY does have a clock and does track sun position.

Well now ISY went down. This is at my church so I'll have to stop and try to see why it is down. But I am able to access the network, so it is not a power outage or network outage. Anyway, I definitely did not accidentally delete the node doing any of those things. I am familiar with how to delete a node and promise you I didn't. But now that ISY has shut down for some reason I am wondering if ISY is having an issue.

This is a 994i and an rpi running PG2, but the PG3 forum is closest I guess. Anyway, my rpi died, I ordered a new one, but while waiting, ISY deleted half the nodes. I do not understand why it did this. This creates issues since any program that mentions those nodes becomes non-functional. If I fix those programs, then they will need to be fixed again when I get the new rpi installed. But why would ISY delete a node just because it isn't responding at the time? And why only some of the nodes? I would expect that ISY would just leave the nodes unpopulated, not delete them. I do not know for sure how long it took from the time the rpi went offline until the nodes were deleted. There have been several times that rpi went offline for a day or something in the past and this did not happen. This time it has been over a week and the new rpi is supposed to come tomorrow.

half red = last run was false half green = last run was true solid red = currently running false solid green = currently running true When I did "upgrade packages", I also didn't believe anything happened as it did not appear to reboot. However, it showed _5 as the version number and the correct time for having updated.

I have suffered the same issue. First off, there are some revisions of the current firmware that supposedly fix this bug. Go to https://polisy.local:8443/WEB/sysconfig.txt and find your current firmware. You will see a section that looks like this: isy-5.7.0_5 Name : isy Version : 5.7.0_5 Installed on : Thu Oct 26 20:04:26 2023 CDT Origin : misc/isy Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : UNKNOWN Comment : ISY Port to X (IoX) The latest version is 7..5.0_5 My system was on the _4 version when it spontaneously disabled all my programs. Please do an "update packages" to get the _5 version which I pray fixes the issue. I am going to assume you have programs that are supposed to be disabled and that you have lots of programs and that figuring out which ones are supposed to be disabled would be a major PITA. In that case, hopefully you have a recent backup so you can restore the programs to proper enabled/disabled status. If it is easy for you to know which programs are supposed to be disabled, just go to the program summary page, block highlight all the programs, right click, and click enable. Unfortunately, my backup was 6 months old and my system had changed. First I made a current backup of the system. Then I restored my 6 mo old backup, took screen shots of all the programs showing enabled/disabled, then loaded the current backup back onto the system. I block highlighted all the programs and enabled them, then went back and disabled the 30 or so that needed to be disabled using my screenshots. Then I made a new backup just in case _5 version hasn't actually fixed the issue.

I don't know much about Brultech, just at a glance I didn't see any DC voltage meter on it. I use Emporia Energy for monitoring my home energy which has a PG3 node. Though Emporia doesn't report voltage, only energy consumption. But it works great for that and a PG3 node makes it very streamlined.

I'm on Polisy and Nodelink is working. I am running DSC, CAI webcontrol, and ISY data on it.

CAI Webcontrol 8 board has several analog inputs on it that measure 0-10vdc. You would need to fashion a voltage divider to bring the 12v battery in range. Might need to include a path to ground through a resistor as well to keep it accurate, I'm not really super savvy when it comes to that stuff. The CAI board has a node server made by IOGuy. It runs on a rpi or PC and can be downloaded from his website. There is a section here on the forum just for nodelink. For me this would be the easiest especially considering I already have nodelink running in my setup. Once you get that analog value showing up in a node on ISY you would write a program to convert the voltage divided value back to the undivided value. https://forum.universal-devices.com/forum/113-nodelink/

@Geddy Update Packages did nothing. I waited well over an hour and nothing. Now today, it spontaneously disabled all of my programs (except 2 for some reason) and they aren't correcting after multiple reboots. I am very unhappy. Nothing is working and I have a huge number of programs and figuring out which need to be disabled will be impossible. My most recent backup is 6 months old, but perhaps I can restore it, take screenshots of the program summary page and then restore the current backup and set the programs. I can ssh into polisy but don't the proper commands to issue an upgrade. EDIT: I guess it did update even though I never had to log back into the admin console because I did the command above and it shows _5 now. Mind you, I did not do an update at the time of the programs being disabled. It just happened for some random reason at some random time.

yes

I don't know what S21 is. I just powered up the Sensibo, pointed the Friedrich remote at it and pushed power button. Immediately on the Sensibo app on my phone it showed configured and ready to go.

yes. and it doesn't have to be set by the sensibo. If you use the remote that came with the unit, sensibo gets updated, at least with my Friedrich unit. I believe the unit itself transmits an IR signal whenever it changes state and the Sensibo receives that. This is why you need to mount the Sensibo somewhere that it can receive an IR transmission from the unit.

Sensibo as far as I can tell controls everything from the app (schedule, leuvers, temp, power, mode, fan, etc). Again, this is on a Friedrich system. From ISY there are fewer options (on/off, temp, fan level, mode). I assume it is that the creator of the node just didn't put it all in. The app is frankly a lot better layed out then the remote that came with the unit.

I don't know about integration being complete or not with your unit, but I used a Sensibo on a Fredrich unit and it works great. Regarding power. I cut off the end of a simple inexpensive extension cord, stripped the wires and then screwed it down inside the unit where the power connects. That gave me a plug to plug the USB power brick that sensibo uses. I zip tied the plug and brick down inside the unit where there was some space and ran the usb wire out of the unit using one of the pre-imprinted knock-outs the unit had and double face taped the sensibo to the wall next to the unit.

Problem I have is my old isy99i I am using as an IR receiver. It receives IR commands and then uses network resource to trigger polisy. But in the last year, I am no longer able to login to 99i because java won't let me. Says the certificate is expired. So can you tell me how to get around that so I can configure my 99i again?

_4 is my version

@Javi I too would like to know if I can change the port number. Looking over ISY the port number is greyed out and I can't find anywhere in PG2 or PG3 to change the port.

I'm on 5.7.0 Don't know anything about the _5. I upgraded to 5.7.0 a couple weeks ago. I didn't do anything since then. This wasn't associated with an upgrade. It was working when I left for work yesterday and when I got home all the programs were disabled.

Things weren't working today. I went into ISY Admin Console and discovered every single program was disabled. Fortunately, a reboot of ISY seems to have fixed the issue. My wife says there was a power flicker earlier today, but the Polisy is on a UPS, so I don't know how that would be the cause. This is most disconcerting, if I were out of town, things would have failed.