This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
here are my specs:
What are yours @WouterNLD ?
Edit: i read the question wrong, no the attached devices only have normal characters and "-" "_" in there names
Edit 2: @gruijter_dev i found a space in an network name (of a device with i cant edit) could that be the troublemaker?
Yeah, that isnt an easy one, its tucked away behind the dishwasher... so i cant (easily).
ive made an new wireless and connected Homey and my computer and now it works. so its defenetly an device name in my network, i going to continue my search
And thanks again for a cool app !
Anyways, exactly the same screen as @matrover posted above.
The log states:
2017-11-27T19:09:44.522Z updateRouterDeviceState error: Error: Error: Invalid character in entity name Line: 158 Column: 21 Char: at parseString (/netgear.js:385:15) at Parser. (/node_modules/xml2js/lib/parser.js:307:18) at emitOne (events.js:116:13) at Parser.emit (events.js:211:7) at SAXParser.onerror (/node_modules/xml2js/lib/parser.js:122:26) at emit (/node_modules/sax/lib/sax.js:624:35) at error (/node_modules/sax/lib/sax.js:653:5) at strictFail (/node_modules/sax/lib/sax.js:677:7) at SAXParser.write (/node_modules/sax/lib/sax.js:1491:13) at Parser.exports.Parser.Parser.parseString (/node_modules/xml2js/lib/parser.js:322:31)
2017-11-27T19:10:44.523Z updateRouterDeviceState error: Error: Error: Invalid character in entity name Line: 158 Column: 21 Char: at parseString (/netgear.js:385:15) at Parser. (/node_modules/xml2js/lib/parser.js:307:18) at emitOne (events.js:116:13) at Parser.emit (events.js:211:7) at SAXParser.onerror (/node_modules/xml2js/lib/parser.js:122:26) at emit (/node_modules/sax/lib/sax.js:624:35) at error (/node_modules/sax/lib/sax.js:653:5) at strictFail (/node_modules/sax/lib/sax.js:677:7) at SAXParser.write (/node_modules/sax/lib/sax.js:1491:13) at Parser.exports.Parser.Parser.parseString (/node_modules/xml2js/lib/parser.js:322:31)
etc.
The problem was / are my heos speakers. There names arent weird but the manufacturer is “D & M Holdings” and i think the “&” gives the error.
@WouterNLD could you verify this / do you have any weird characters in the names or manufacturers your network?
By the way, you both reported a slightly different string for the devicename. Could you post the exact string you get (copy paste)?
So this means the root cause of the problem is that Netgear is producing xml that is not compliant to the xml standard.
I'm working to find a workaround, with some help from the xml parser developer.
2017-11-28T16:27:19.010Z {"Firmware":"V2.0.0.74NA","RegionTag":"RBR50_NA","Region":"us","Model":"RBR50","InternetConnectionStatus":"Up","ParentalControlSupported":"1","SOAPVersion":"3.14","ReadyShareSupportedLevel":"4","XCloudSupported":"1","isBlankState":"0","LoginMethod":"1.0"}
2017-11-28T16:27:21.674Z {"ModelName":"RBR50","Description":"Netgear Smart Wizard 3.0, specification 1.6 version","SerialNumber":"************","SignalStrength":"-4","Firmwareversion":"V2.0.0.74","SmartAgentversion":"3.0","FirewallVersion":"net-wall 2.0","VPNVersion":"","OthersoftwareVersion":"N/A","Hardwareversion":"N/A","Otherhardwareversion":"N/A","FirstUseDate":"Sunday, 30 Sep 2007 01:10:03","DeviceName":"Orbi-RBR50","FirmwareDLmethod":"HTTPS","FirmwareLastUpdate":"2017_9.30_2:21:33","FirmwareLastChecked":"2017_11.26_21:27:57","DeviceMode":"0"}
2017-11-28T16:27:23.246Z retrieving knownDevices from persistent storage
2017-11-28T16:27:23.258Z router added as device
2017-11-28T16:28:23.432Z login succsesfull @ driver
2017-11-28T16:28:29.103Z updateRouterDeviceState error: Error: Error: Invalid character in entity name Line: 227 Column: 21 Char: at parseString (/netgear.js:390:15) at Parser. (/node_modules/xml2js/lib/parser.js:307:18) at emitOne (events.js:116:13) at Parser.emit (events.js:211:7) at SAXParser.onerror (/node_modules/xml2js/lib/parser.js:122:26) at emit (/node_modules/sax/lib/sax.js:624:35) at error (/node_modules/sax/lib/sax.js:653:5) at strictFail (/node_modules/sax/lib/sax.js:677:7) at SAXParser.write (/node_modules/sax/lib/sax.js:1491:13) at Parser.exports.Parser.Parser.parseString (/node_modules/xml2js/lib/parser.js:322:31)
2017-11-28T16:29:29.019Z updateRouterDeviceState error: Error: Error: Invalid character in entity name Line: 227 Column: 21 Char: at parseString (/netgear.js:390:15) at Parser. (/node_modules/xml2js/lib/parser.js:307:18) at emitOne (events.js:116:13) at Parser.emit (events.js:211:7) at SAXParser.onerror (/node_modules/xml2js/lib/parser.js:122:26) at emit (/node_modules/sax/lib/sax.js:624:35) at error (/node_modules/sax/lib/sax.js:653:5) at strictFail (/node_modules/sax/lib/sax.js:677:7) at SAXParser.write (/node_modules/sax/lib/sax.js:1491:13) at Parser.exports.Parser.Parser.parseString (/node_modules/xml2js/lib/parser.js:322:31)
App version 1.2.0 Stable was just submitted to the app store pending approval from Athom.
This version has the following enhancements / fixes:
* Fixed several bugs, including a bug in up/down speed
* Fixed app-crash caused by invalid device names that include the &-sign
* Greatly expanded the supported router types. It has now been confirmed to work with:
- WNR2000v5 (80)
- WNDR4500v2 (5000)
- R6250 (5000)
- R7000 (5000)
- R7800 (80)
- R8000
- R9000
- RBR50 Orbi (80)
I also expect other types to work.
For this version I have not received any reports on Netgear routers that do not work.
But in both cases: Please confirm in this forum if you have a supported router that is not in the above list. And please also inform me if you have a router that does not work (correctly)
Confirmed working on an Orbi RBR50
with Heos speakers in the network
Thanks for all the hard work @gruijter_dev !
My speed is also 0.03 en 0.01 en it should be more than 300 en 30 on my R7000
I dint test it when i was at home and looking YouTube or Netflix i will test that this evening.
I am at work now so the insight is when no one is at home.
So is it wright that te speed you see in Homey is nog the speed i see when i do a speedtest.?
Changes:
* Fix option to empty the known devices list.
* Added automatic soap port detection during pairing.
* Several minor tweaks.
This version is running very stable on my R7800. I hope you can enjoy it as well
just an idea for a new feature:
Making som kind of "whitelist" feature or "group" feature in settings that can then be referred to in a flow card - kind of the way the "Devices" flow card works with any, some, none in a zone.
Like in the flow below:
The goal is to turn off power to the printer if none of the two PCs are online, which can be done by
IF a device goes offline AND [[it's PC-1 AND PC-1 is offline AND PC-2 is offline] OR [it's PC-2 AND PC-1 if offline AND PC-2 is offline]] THEN switch off the printer.
The initial check whether it is PC-1 or PC-2 is to avoid triggering the flow in it's full every time a unit goes offline.
Have the reciprocal flow, switching on the printer if one of the PCs are online as well.
In this case, when only two devices are involved, it's pretty straightforward, three devices will be possible, but four or more is not possible with only three "or" spaces available in the flow.
If it was possible to make a list (one or more) it would be possible to make a flow like:
IF a device goes offline AND the device is on "this list" AND no devices "on this list" are online THEN...
Hope I've described my idea in a way that it's understandable - but please ask, if something is unclear.
Regards,
Chr.
Thx for the input. Always nice to see how people are using the app. I think I do understand what you would like to have. But I do not see grouping of devices as something the netgear app should handle. It would deviate too much from the core functionality that I intend to support. It is more something that should be part of flow functionality. You can always make multiple flows to achieve what you want with more then 3 devices. Also you might want to check some other apps like better logic, virtual devices, and device groups, to see if that works for you.
You're completely right, it can be done by making several flows - and as far as I can figure out, neither Better Logic, Virtual Devices, or Device Groups can provide shortcuts on that - I just like keeping the number of flows as low as possible :-)hopefully, you'll sit some day having nothing to do and realise, that this was one of the best ways to improve the app jump right into making it ;-)
Still, it's a great app <span></span>
Chr.