glarsen

All works well here too using the downloaded package. Though it doesn't seem impact anything, the MAC for the ethernet interface I'm using shows as "00:0d:ffffffb9:52:ffffffbf:fffffff4". The correct MAC is 00:0d:b9:52:bf:f4, so for some reason something is loading a bunch of extraneous "f"s. I'm using DHCP and it configures correctly, so this appears to be something spurious. Edit: Change the timezone to Victoria (-8) required the same steps reported by gviliunas. Edit2: The gateway address shows 0.0.0.0 although route show does display the correct gateway.

Sure. Read this post . I set mine up as suggested here and it works flawlessly.

Same here today. No portal access, thus no Alexa. No nodeserver access (Polisy or nodelink). Could not connect with console, through portal or apps. Power cycle was required to restore access. It seemed anything internal to the ISY continued to run, but nothing requiring external access functioned. Log sent.

Ping doesn't work since the system call structure in Python is slightly different in FreeBSD than in debian/rpi linux. The developer needs to rework the code a bit to fix it. The same applies to the presence-poly NS.

4 19:59:56 raspberry systemd[1]: [/etc/systemd/system/nodelink.service:10] Unknown section 'UNIT'. Ignoring. I think "UNIT" should be "Unit". It's case sensitive in most *nixes

I just installed the ping nodeserver for fun. I looks like it has the same problem with the ping API call. It shouldn't be too hard to fix.

I had the same issue. After digging into more I discovered that there are two issues: 1. Bluetooth support is different in FreeBSD. The methods used in the ping server are not supported. 2. The Ping API call works differently in FreeBSD (thus the error you see in the log.) I edited the Python code directly on my Polisy and removed BT support completely since I don't use it. Also rewrote the Ping call. I haven't forked the original project on Github so the code isn't posted publicly but I can share it with you privately if you are able to manually replace Presence-Poly.py on your Polisy.

I too was experiencing this. I never did determine exactly which nodeserver was causing it. (I have Sonos, MyQ, AVRemote and Meteobridge). I restarted Polyglot several times and it just stopped displaying those errors, no idea why. Interestingly, whether related or not, during this time I could not get ISY to talk to the SONOS nodeserver (it worked the other way around - Polyglot to SONOS). Once this disconnect/reconnect thing stopped, SONOS began working properly, so maybe it was the SONOS nodeserver that was causing it.

I just ran the install script manually and updated to 0.10.2 cleanly.

Everything migrated just fine it seems. (MyQ, Sonos, Meteobridge). Just a Presence-poly fix needed to finish the job.

I received my Polisy today, with wifi board loose inside the case. Does it matter which of the PCIe slots it is plugged into?

It's a problem being experienced with other nodeservers as well. There's a thread about the new SonosController in Developers/Discussions where the same problem is occurring.

Worked pretty well. I converted the startup to use the systemd scripts instead of rc.local and all was good! Thanks for the update.

FYI Michel, I am again also experiencing this on my Note 8 and my wife's S9+

I'm trying to figure out how to use a routine (e.g. Alexa, Goodnight) to turn off a Group of Scenes. I have a number of scenes (3) which are exposed as devices and a device within a Group. Using the Group directly either manually or using the Alexa spoken works as expected, either turning the Group of scenes on or off as instructed. However, when using the routine none of the scenes within the Group are activated, only the single device. Is this expected behaviour? Thanks!

The background reporting appears to be working properly. Updates are occurring as expected.

Fernando, as soon as both devices, S7 and Note8, were updated, they reported "In" the geofence. I'll check the background reporting when we go out a little later to ensure all is working properly, but this is a good sign. Thanks again for the help!

I will, as soon as it is available!

Thanks for looking into this Fernando. Much appreciate the quick response.

Thanks, appreciate it!

Sorry, definitely set up as "Editor".

(Samsung Note 8 and Samsung S7) I'm not sure what you mean about settings. I've re-verified all of the permissions settings after the re-install of the app, as well as the power-saver settings. And of course, re-established the geo-fence location and size using the GPS locator pin (which does show in the correct location) after the re-installation this morning.

Sorry Michel, that doesn't help any. It doesn't explain why both worked just fine with the current settings until the latest UDI Mobile update was installed in the last couple of days. The phones are both at the latest version of firmware, one is my wife's and the other mine so they are rarely close enough to one another to be an issue, especially during the work day. Both have been re-booted, the app uninstalled and re-installed, permissions opened completely up and geo-fences removed and re-added. They both have the app set to "unmonitored" in the power saving settings so that they continue running in the background. They are both set to 10m and 1 minute inside a 250 m diameter fence. I've even tried changing the diameter to 400m and both still behave the same. The pin turns blue when i manually "Report Device Status", and then a minute later turns red again. The ISY status follows with in/true and out/false as expected. Both phones have also been deleted from and re-added to the portal so I'm at a loss. It kind of removes half the value of having the portal for me. It's disappointing because for months it all worked perfectly, and now suddenly, nothing. "

I'm experiencing an odd situation where both my Android devices (Samsung Note 8 and Samsung S7) are both reporting "Out" all of the time. This behaviour began right after updating the app to the latest version from Google Play on the 14th of August. Manually reporting device status will update correctly, but a few minutes later the status again reverts to "out". I've tried uninstalling and re-installing the app, removing and re-adding both devices to the portal and verifying app permissions are all set correctly, with no luck. Has anyone else experienced this?