vbPhil

I see the problem. The list of Locations shown when selecting the AC Change Location button is wrong for Albuquerque. It shows the Albuquerque Daylight Saving Rule is America/Phoenix, it should be America/Denver. Phoenix does not change to Daylight Saving. I wonder when that rule was changed. I've never had this problem before. Update 3-14-2023, UDI contacted and will resolve in the next update.

Nothing relevant in the log files. Did another Reboot but it's still showing Standard Time. I guess I need to read up on how Unix reconciles time zones.

I changed the Location to Denver and it adjusted the clock display correctly to Daylight Saving. Changed it back to Albuquerque and it adjusted the clock back to Standard time.

I verified Polisy date via SSH and it agrees with the AC, but it is indicating Mountain Standard Time (MST). So, it's doing everything right except it doesn't know about Daylight Time. I notice in the AC that the Daylight Standard checkbox is checked but greyed out. Why would it be greyed out? [admin@polisy ~]$ date Sun Mar 12 07:13:11 MST 2023

Location is correct, Albuquerque, NM.

Did a Reboot and it's got the day correct but the time is one hour off, still at Standard instead of Daylight Saving.

My Polisy did not adjust to Daylight Saving last night. In fact, the Admin Console time is showing Saturday at 11:39pm. It's actually, Sunday at 7:39am. No where in the World is it still Saturday right now. I wonder what screwed up. IoX version 5.5.9.

I always have 5+1 beeps but my commenting goes unanswered. Also, the update instructions for Polisy no longer say to unplug Polisy but rather issue a reboot. However, it still states to Power Up Polisy. I wonder who writes/reads this stuff anyway?

Any error messages? Polisy or Eisy?

Upgraded from 3.1.17 without any issues. Thanks

Great, thanks! I never noticed that control command before in the AC.

can someone explain what the "hail" is?

I get 48 as well with Polisy on 5.5.7. Checked this on the Time & Date website and they say this. https://www.timeanddate.com/date/durationresult.html?m1=1&d1=1&y1=2023&m2=2&d2=18&y2=2023 So I agree. Today is the 49th day of the year from and inclucing 1/1/2023.

5.5.7 upgrade went as expected which is becoming a trend. The one thing I notice is after upgrading the status of my Z-Wave devices is not known until I query each one. However, the battery devices don't seem to query.

I quite often get a Request Failed or some sort of TCP error when selecting the Query button in the Admin Console for a battery-operated Z-Wave device. It's my understanding that a battery device is asleep and wouldn't hear a command from the controller. Which possess the question on what exactly does that query button do in this case? Can someone explain this for me?

Yes thanks. The ZSE40 is a battery device so I had to put it in wakeup mode first. But, all is well.

@Chris Jahn 5.5.6 didn't fix the Celsius temperature readings on the ZSE40 ZooZ 4-in-1 Sensor and Aeotec ZW078 Heavy Duty Switch. Do I have to do anything extra after upgrading to 5.5.6 to make them switch to Fahrenheit?

@bpwwer @Geddy PG3 is working again. Here's what I did. I decided to put in a Support Ticket. Went to UDI Support page and logged in using my ISY Portal Login. After logging in I decided to try PG3 one more time and this time it worked. I wonder if logging in to the ISY Portal had any effect? Anyway, PG3 is accessible again and IoX is showing data from the node servers. Go figure.

That didn't work. Polisy. I'm not getting the PG3 login page. I'm trying to launch PG3 from the AC menu link and I get a browser page that says 192.168.1.158 refused to connect.

Upgraded from 5.5.5 to 5.5.6. IoX seems normal but PG3 isn't responding with the login page and the Node Servers aren't populating AC with data. What's my next move?

UDI is aware of this issue with some devices and has promised to fix it. UDI is aware that some devices won't finish the interview but I'm not sure what they're going to do about it. Sometimes if you exclude it and try again it may work. Or try an 'update with interview' from the z-wave popup menu choice on the device.

I might have 3 ZSE44s that I'll sell cheap, along with some other z-wave devices. I'm not happy with z-wave devices right now with how they include/exclude and show up in Home Assistant and the InFluxDB add-on. Too many nodes show up that don't have any use in "my network" and it's a pain to manage when there's many of them. As example, here's what I get for the ZSE44, 12 nodes when all I want is 2, temperature and humidity. The ZSE44, however, added smoothly to my Polisy Zmatter Z-Wave migration. I'm also using Wireless Tags but I think they're on the way out for me as well. I'm trying YoLink devices later in the week. Hopefully they might be my new alternative.

Me too. One ghost device with Interview not done.

Mine is working fine, no re-install required after upgrade. Polisy 5.5.5.

@Chris Jahn 5.5.5 didn't bring with it the fix for temperature readings in Celsius instead of Fahrenheit. Is that still on your bug list to fix? My affected devices are; ZSE40 ZooZ 4-in-1 Sensor and Aeotec ZW078 Heavy Duty Switch.