glarsen

OK, I guess I'll dig some more.....

@JimboAutomates, I'm not sure whether this is an ELK or UD Mobile issue. Sometime in the past week after one upate or another (UD or ELK, I don't know which), I no longer see a drop-down for Armed Status. Is there now a different way to ARM/DISARM or am I missing something? I'm on IoP 5.4.3_1, PG3 3.0.59, ELK 3.2.7 and UD mobile 0.140. I've resynced UD Mobile, restarted the node server, restarte IoP, and in various orders and no change. Thanks!

Yes, because the status driver isn't used in the child node, it's used as one of the data drivers. The parent provides that status information. I'll change that in the next version so it doesn't show.

I'm not too sure, it seems Dyson doesn't like your credentials for some reason. Try the 'US' in lower case maybe. I've seen that Dyson seems to be case sensitive for some things, ie the serial number has to use all caps.

I think it's telling you that it wasn't succesful in connecting to your fan. Perhaps you can turn on DEBUG in logging, and then restart the node server again. You can PM the log to me instead if inserting in the public space. Double check your configuration - make sure there are no leading or trailing spaces in any of the elements. I know it's a bit tricky because of the Dyson API - acquiring that credential need to connect is a pain. I believe you can run two copies of a node server on PG3; they would just be installed in separate slots.

Too many variations for Holidays to make it worth the effort for me. Canada is different from the US. But there are a couple of new Holiday node servers on the PG3 store that are free. Take a look at those.

When the Area node is opened in UD Mobile. The zones are fine.

@Javi, @JimboAutomates, I think this update must have broken something with UD Mobile. I get "java.lang.error: Node Status Relation Cursor is empty. NodeId: 1551. Control:0.500. I have restarted the ISY and the reloaded the app with no change. Edit: The node status fields all display, but none of the CMD fields appear. All of the grouped nodes show.

There is also a restriction on which characters the ELK can display...for instance if a degree or percent symbol is embedded in the string, nothing will display. Ask me how I know this...?

Glad you got it sorted. That error typically means the hostname is missing in config. I'll have to trap that and provide a specific error message. Next update... Thanks.

Installed, no issues. Linux desktop - no issues with AC.

I have already updated Michel I have already updated Michel. The pre-requisite is documented in the Node server documentation. I don't believe there are any further firmware releases planned for the ISY994i, and it does not have UoM support for GPM, and a number of other new UoMs. I'm also not planning any further releases for the PG2 version of the Node server.

@bpwwer, the issue is that there is a UoM being used in the PG3 version that is only available on the IoP. See the linnk above.

@stevehoyt This is the reason. I had forgotten about this until now. The profile changes in this version break it for the ISY994. The PG2 version works but does not support flow rate

So far I have no idea what the issue is, the profiles and code are identical whether you're using an ISY or the IoP. I do see the same thing as you, here, but can't explain it yet. Michel has mentioned he would suggest migration to you.

@stevehoyt, I've discovered something, just don't have the answer yet. There is something different about the way the Node server loads into the ISY994 and the ISY on Polisy. The identical code and profile work as expected on IoP, yet zone status seems to be missing from the ISY installation. Other nodes statuses are fine, just zones seem to be different. Still trying to figure out why.

Steve, can you confirm which version of ISY you are running. I'm assuming you are still on the ISY994i, and not the ISY on Polisy, correct?

Thanks @Bumbershoot. I also experienced some of this when moving from PG 2 to PG3. The fix was also as suggested, to click on an element, then 'Update', then 'Save Changes'.

It would be helpful if you could provide some additional information to troubleshoot this, such as: 1. Version of Polyglot (i assume you're using PG3?) 2. Version of rainmachine installed. 3. Set the rainmachine log level to debug and restart the Node server. Then zip the log file and PM it to me. 4. Exactly what you are trying to do with the status variable. I haven't had any issues with this Node server working with either my ISY at 5.3.4, or IoP at 5.4.1, so I have no idea why your installation isn't working correctly. Thanks.

Looks like you have a dead copy still connected to MQTT, although I would have thought the restart would have fixed that. Are you able to ssh to your polisy to kill it? ps ax|grep rm-poly 84788 - I 96:50.60 python3 ./rm-poly.py (python3.8) sudo kill 84788 (this number will be different, specific to the your copy) After doing that, restart the rainmachine Node server. It should be showing 3.1.5. As far as I can tell, it looks like it installed ok, according to the PG3 log.

Yes, I know. That is an ISY on Polisy issue, and has nothing to do with what my Node server displays.

It should be fine after restarting, as mine (on Polisy) was good after the restart. I did find a bug where the sunset/sunrise times were not being updated properly. The code was only checking for DST at startup, not every longPoll and release 3.2.21 corrects this. Timedata calculates Sunrise/Sunset times itself, independently of the Polisy/ISY, so the Timedata times should be correct now.

I just looked at this. I did find something that is related to the change to/from DST, so will issue an update in a bit. Restarting the polisy would restart everything, PG2, PG3 and all node servers.

Try restarting the Node server. If I recall correctly, I think calculations happen at midnight and of course the time change is at 2am. I'll look into this tomorrow when I get back home.

Yes, mine upgraded successfully too, showing the same log entries. My Polisy is also one of the early ones (geek release ?)